REST API design patterns for the Verendar project — resource naming, status codes, pagination, filtering, error responses. Includes mandatory Verendar conventions (ApiResponse<T>, PaginationRequest, internal endpoints, soft delete). Use this skill whenever designing or reviewing API endpoints in Verendar. Activate proactively when the user is adding a new endpoint, designing a route group, or asking about API structure.

Code review specialist for quality, security, and best practices

Git workflow guidance for commits, branches, and pull requests

Transform Claude into an expert code reviewer following industry best practices.

Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.

Self-improvement loop triggered after any user correction. Captures mistakes as prevention rules in tasks/lessons.md so the same error is never repeated.

Review animation.c for C issues — memory safety, terminal handling, signal safety, and game logic

Audit a restaurant's web presence — check what AI models see when deciding whether to recommend it. Covers website, Google Business Profile, review platforms, and structured data.

Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.

Review authentication and authorization design including OAuth, JWT, token expiration, RBAC/ABAC, and privilege escalation risks.

Confidence-based model tier escalation for agent tasks. Defines when to escalate from Haiku to Sonnet to Opus, escalation signals, and the never-skip-tiers rule. Use when an agent fails or underperforms.

Writes React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.

Post-draft diagnostic for sermon and book writing. Scans for machine tells, assesses authenticity risk, checks voice continuity against the author's sermon corpus. Fires after writing is complete or when reviewing existing drafts. For during-writing standards, see like-a-human.

Triage and review Linear issues - list, filter, prioritize, and update issue status. Use when asked to check tickets, review backlog, or see what needs doing.

PANaCEa design system reference — typography tokens, visual hierarchy tiers, shared component helpers, and inline style conventions. Use this skill whenever modifying, creating, or reviewing UI components in the PANaCEa clinical library, reference views, toolkit, or any component using inline styles. Also trigger when the user mentions typography, fonts, styling, visual hierarchy, design tokens, color system, dark mode, or consistent look-and-feel across PANaCEa components.

startproject

Run a weekly retrospective across Threads and note outputs, then propose next-step improvements. Use for recurring optimization.

Product management: PRDs, RICE prioritization, metrics

**모두**&#x200B;이(가) true인 경우에만 적용:

Reviews changes for security, scalability, performance, code reuse, and maintainability using a structured checklist. Use when the user asks for a code review, wants feedback on a PR, or wants to harden code quality.

Review React/Next.js components, server actions, and data-fetching logic in the ClipRace repo to prevent performance regressions by checking RSC vs client boundaries, bundle size, waterfalls, CLS, and large list rendering. Use when the user asks for a performance review of specific routes, components, or flows.

Ruby Style Guide (rubystyle.guide) conventions. Use when writing, formatting, or reviewing Ruby code for layout, naming, flow of control, methods, classes, and idioms. Complements RuboCop.

Create a six-frame storyboard that shows a user's journey from problem to solution. Use when you need a fast narrative for alignment, concept reviews, or demos.

Use when resolving random JIRA issues. Fixes bugs, refactors code, performs code and security reviews, ensures 100% test coverage, runs CI checks, and creates pull requests. Links PRs to JIRA issues and updates issue status.

Reviews a pull request from a PR URL by directly fetching the URL content (no `gh` dependency) and verifies compliance with CONTRIBUTING.md. Use when the user asks for a PR review, to review changes before merge, or to check contribution guidelines.

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

Defines usecase-layer guidance for this repository in DDD x Clean Architecture, including usecase responsibilities, orchestration, transaction boundaries, DTOs, repository and external service ports, `internal/usecase` splitting, and `docs/domain/usecase` maintenance. Expected outputs include concise usecase-layer recommendations with reasons, placement guidance, transaction and side-effect handling notes, or small Go-oriented usecase templates with assumptions. Use when designing, implementing, reviewing, or documenting the usecase layer in this repository.

Audit email2telegram release artifacts for secret leaks and insecure defaults on GitHub, Docker Hub, and VPS. Use when preparing a release, reviewing .env/Dockerfile/compose/deploy scripts, changing scripts/release.sh, or when the user mentions security, secrets, leak, audit, hardening.

Performs a structured security review with a comprehensive checklist (secrets, input validation, injection, authz/authn, XSS, CSRF, rate limiting, sensitive data exposure, dependency hygiene). Use when adding authentication, handling user input/uploads, creating API endpoints, working with secrets/credentials, integrating third-party APIs, or implementing payment/sensitive features.

>-

Запускает трёх суб-агентов: **task-decomposer → task-worker(s) → work-reviewer**. Каждый шаг выполняется **в отдельном агенте** (отдельном контексте), а не в одном общем.

Use when reviewing Inbox One AI features for prompt-injection, unsafe automation, data leakage, and model-boundary issues. Trigger when changing ai-service logic, /api/ai/* routes, AI draft/reply/summary flows, composer prompt handling, future model integrations, or when the user asks for prompt-injection review, LLM safety review, AI guardrail review, or data-leakage review in this repo.

Run parallel reviews on draft/spec/ticket inputs and emit Council artifacts

[BETA] Offload plan phase to Claude Code's ultraplan cloud — drafts remotely while terminal stays free, review in browser with inline comments, import back via $gsd-import. Claude Code only.

Orchestrator-first workflow for building and shipping changes via KB Orchestrator (orchestrator/): setup target repo/workdir, run validation jobs with artifacts + safety, then run structured code review and apply fixes (requesting-code-review/receiving-code-review), and verify web UI behavior via Playwright MCP. Use when the user asks “через оркестратор”, wants repeatable stages + audit trail (commands/prompt), or needs phone/VPN-accessible web demo checks.

Run a literature review using paper search and primary-source synthesis. Use when the user asks for a lit review, paper survey, state of the art, or academic landscape summary on a research topic.

Use when refreshing RemDo dependencies. Run the workspace dependency refresh script, fix only straightforward fallout, then review CI warnings, tooling freshness, and notable release notes for simplification opportunities.

Structured code review checklist for torch_sipu changes. Use when reviewing code, a PR, a diff, or auditing operator implementation.

Manage GitHub Project v2 issue states, workpad comments, and related follow-up actions.

When a problem is found outside the current task scope, classify and act. Enforces strict triage rules: only direct regressions stay in the branch; everything else becomes a filed issue with full context, proper size split, and milestone set to match the current PR.

[OMX] Run a comprehensive security review on code

Review source files changed during a phase for bugs, security issues, and code quality problems

Review Donna experiences for older-adult usability, caregiver clarity, and reassuring low-friction interaction. Use when evaluating onboarding, dashboards, reminders, authentication, settings, copy, navigation, or any user-visible flow in `apps/consumer/`, `apps/mobile/`, `apps/admin-v2/`, or voice prompts intended for seniors and caregivers.

Adversarial verification agent for investigative articles

Audit repository documentation against the real codebase and reorganize docs into three buckets: implemented, planned, and mismatch. Use this whenever the user asks to review docs for correctness, compare docs with code or git diff, reconcile stale design docs, rewrite project documentation structure, or maintain `project-index.yaml` as the source of truth for doc-to-code mapping.

Walks the merchant through Stripe onboarding, captures their API keys, and writes them to Vercel env vars. Handles the common case where KYC takes days by supporting a preview-mode deploy path.

Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill \u2014 run after /story-readiness, before /code-review and /story-done.