আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
This skill creates pull requests using the GitHub CLI with AI-generated descriptions. It analyzes the current branch, detects available target branches, and generates concise PR descriptions based on the commit history and changes. Use this when asked to create a pull request, file a PR, or when the user uses the `/pr` or `/gpr` command. It automates the PR creation process while ensuring quality descriptions.
Preserves session context when context window fills. Triggers at configurable thresholds (50%/75%). Captures objective, progress, technical details, decisions, blockers, and next steps.
Creates a streamlined pull request from v2 (staging) to main (production) with change summary, affected apps detection, and deployment checklist. This skill should be used when ready to deploy staging changes to production, creating a production PR, or promoting v2 branch to main.
Specialized agent for creating, maintaining, and organizing comprehensive documentation for the BarqNet project. Records all changes, creates technical specifications, API documentation, user guides, deployment guides, and maintains documentation consistency across the entire codebase. Use when documenting features, creating guides, or organizing project knowledge.
Guide development following Kent Beck's Test-Driven Development (TDD) using Red → Green → Refactor cycle. Use when writing tests first, implementing features with TDD, need to write failing tests, make tests pass, refactoring after tests pass, following red-green-refactor, fixing defects with tests, or practicing test-driven development methodology.
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be <5% of main task time, <30 seconds per fix, and reversible. Use after key points, not after every small change.
Red-team thinking for robustness testing and edge case discovery. Use when you need to stress-test solutions, find vulnerabilities, anticipate failures, or challenge assumptions. Ideal for security review, system design validation, decision stress-testing, and pre-mortem analysis. Example: "We've designed an auth system" → Attack it from 10 angles before shipping.
Archive completed implementation plans after PR merge. Use when a plan's implementation has been merged to main, or after plan-execute completes on main branch.
UI/UX design intelligence with searchable database: 50 styles, 21 color palettes, 50 font pairings, 20 chart types, 8 framework stacks. Trigger phrases (use this skill when user says): - "build a landing page", "create a dashboard", "design a website" - "Reactでコンポーネント作って", "Next.jsでページ作って", "Vueでアプリ作って" - "make it look modern", "use glassmorphism", "add dark mode" - "UIを改善して", "デザインを良くして", "もっとモダンにして" - "choose a color palette", "recommend fonts", "what chart should I use" - "fix accessibility", "improve UX", "optimize for mobile" - "style with Tailwind", "add hover effects", "create responsive layout" Supported: React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, HTML+Tailwind. Elements: button, modal, navbar, sidebar, card, table, form, chart, hero, footer. Styles: glassmorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, flat design.
This skill should be used for reviewing current project against mature project patterns, tool capabilities, and org standards. Triggers include "review this project", "what am I missing", "align with standards", "check tool usage", "compare to arbor/koto", or proactively at session start in unfamiliar projects. Surfaces gaps in patterns, underutilized tools, and org standard deviations.
Guidance for responding through Slack MCP: immediate acknowledgements, progress cadence, thread discipline, message templates, and failure handling. Use whenever Codex must reply to Slack mentions or share progress/results.
Generate structured release notes tailored to the specified audience and highlighting value, rollout, and risks.
HAIOS Close Work Cycle for structured work item closure. Use when closing work items. Guides VALIDATE->ARCHIVE->MEMORY workflow with DoD enforcement.
Turn Innovation project updates into clear, audience-specific status communications for Slack, email, and executive summaries.
Railway deployment management for {{PROJECT_NAME}}: CLI, env vars, health checks, troubleshooting, rollback.
Verify and close stories after frontend/backend tasks are completed. Check ALL related task files, update story acceptance criteria checkboxes. UNIQUE VALUE: Ensures BOTH frontend AND backend tasks are verified before closing story. Prevents premature story closure. Use this skill when: - Frontend or backend notifies "task completed, please verify" - User asks to "verify story", "accept story", "close story", "mark story done" - Need to check if a story can be marked as complete - User asks "is story X done?", "can we close story X?" CRITICAL: Must check BOTH frontend tasks (docs/reference/frontend/tasks/) AND backend tasks (docs/reference/backend/tasks/) before closing. Output: Update story file checkboxes from `- [ ]` to `- [x]`
Systematic web development workflow from PRD to implementation plan. Generates database schemas, detailed use cases with sequence diagrams, page requirements with state management design (Context + useReducer), and modular implementation plans. Use when building web applications following spec-driven development methodology with PostgreSQL and React.
Audit Claude Code skills against quality criteria including structure, descriptions, content clarity, testing, and best practices compliance. Use when reviewing skills before release or during PR reviews.
DO NOT USE THE APPLICATION NOTE SERVICE. Maintain and organize daily notes for the current project. Create, update, and manage these notes in a structured manner upon user request. Use this skill when the user requests "please make|create|write|add a note...".
