Use when a session starts, when the user asks to "continúa", "kickoff", "arranca la siguiente rama", or when you need a fast snapshot of repo state before doing branch work.
Analyze and improve test coverage. Use when reviewing coverage gaps, writing missing tests, setting up coverage tooling, or improving branch/line/statement coverage for any…
\"Review API calls, responses, and network traffic. 審API調用響應網絡流量. Use when: inspect API calls, review network requests, check API responses, analyze request payload, debug API…
Show detailed view of a story or task. Auto-detects type by ID format: S001 = story, S001-001 = task.
Update a plan document with the latest implementation status, test results, and completed steps. Use when the user asks to update, sync, mark progress on, or refresh a plan.
프로젝트 DesignSystem 모듈의 컴포넌트, Foundation 토큰, Extensions를 탐색하고 API를 분석합니다
White-box security audit. Blue-teamer and lead red-teamer run in parallel isolation for an independent first pass — neither sees the other's output during reconnaissance.
Performance review. Detects project type and dispatches compute and/or web performance reviewers. Advisory only — no changes made.
Create Playwright E2E tests for user flows. Use when testing complete user journeys, protected routes, form submissions, or cross-page navigation.
Figma URL을 분석하여 디자인 구조, 토큰, 컴포넌트를 추출하고 DesignSystem 매핑을 수행합니다
Use when backfilling tests on existing code. Analyzes code through public interfaces, detects the project's test framework, and writes behavior-focused regression tests.
Automatically extract technical requirements from design references when user mentions Figma, uploads images, or says "implement this design".
Expert knowledge for working with Backlog.md task management. Use when managing tasks, organizing epics, handling dependencies, or tracking project progress.
CareMatch용 Next.js API 라우트 생성. 인증, 입력 검증, 에러 처리가 포함된 API 엔드포인트를 생성합니다. 사용법 - "API 만들어줘", "지원 API 생성
Issue 番号に基づいて feature ブランチを自動作成する。「ブランチ作成」「ブランチを作って」「新しいブランチ」「feature ブランチ」「Issue からブランチ」「作業ブランチを作成」「ブランチ切って」などで起動。feature/[issue番号] 形式でブランチを作成。
Forked-context QA reviewer — preloads verdict schema + testing-pyramid lens + assertion/edge-case/TDD checklist.
Branch naming conventions, Git Flow vs trunk-based development, feature branch lifecycle, and release strategies.
Чеклист и формат code review: severity levels (CRITICAL/MAJOR/MINOR/NIT), формат вердикта (APPROVED/CHANGES_REQUESTED/BLOCKED), Django anti-patterns, N+1 detection, dbt checks,…
PR 체인 브랜치들을 순서대로 리베이스하고 force push
노션 백로그에 작업 내용을 맥락 중심으로 정리. "백로그 정리", "노션 정리", "작업 내용 정리" 등 백로그 문서화 요청 시 사용.
변경사항을 자동으로 분석하고 커밋 룰에 따라 커밋 생성