ask-questions-if-underspecified
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
ui-refactor-extract
Refactor UI code without behavior change (extract/rename/reorganize) while preserving public APIs and adding evidence via tests or inspection.
client-generation
Generate or update typed API clients from canonical contracts.
compatibility-check
Validate API compatibility across versions or consumers.
contract-update
Update request/response API contracts and client wiring without business logic.
email-best-practices
Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.
authz-policy
Define and enforce authorization rules for protected actions, with tests and audit considerations.
backend-test-additions
Add or extend backend tests to prove behavior, invariants, and regressions for services/endpoints/jobs.
domain-logic-module
Add or refactor domain rules into a testable module boundary with explicit invariants.
endpoint-scaffold
Create a validated, authorized backend endpoint with error mapping and tests.
integration-adapter
Build an external API adapter with timeouts, retries, idempotency, and error mapping.
job-worker-orchestration
Add background jobs and orchestration with idempotency, retries, and observability aligned to repo conventions.
observability-audit
Ensure logging/metrics/tracing and auditability match the quality bar for changed behavior.
persistence-layer-change
Implement schema/migration changes and update data access patterns safely.
a11y-semantics-pass
Improve semantics and accessibility coverage for UI changes (roles, labels, focus, keyboard, ARIA correctness).
component-scaffold
Create a new UI component consistent with repo conventions (structure, typing, styling, exports).
data-fetching-integration
Wire UI to a data source with typed inputs/outputs, loading/error/empty states, and caching rules.
form-validation
Add input validation rules and UX patterns for forms (client-side validation, errors, submit gating) consistent with repo conventions.
frontend-test-additions
Add or extend frontend tests to cover intended behavior and critical UI states.
performance-pass-ui
Identify and reduce avoidable UI performance regressions (render churn, heavy computations, oversized bundles) without behavior change.
state-modeling
Define client state shape and transitions for non-trivial UI flows (multi-step, branching, async, derived state).
kalshi-markets
Access Kalshi prediction market data including market prices, orderbooks, trades, events, and series information. Use when the user asks about prediction markets, Kalshi markets, betting odds, market prices, or needs to search or analyze prediction market data.
bootstrap-repo
Bootstrap or refresh a repo scaffold (governance docs, .codex folder, Tree.txt). Use only when explicitly invoked.
create-plan
Create a concise, executable plan for a coding task. Use when the user explicitly asks for a plan or when work is clearly multi-step.
decision-capture
Capture non-trivial decisions as a proposed entry for a repo's decision log (e.g., DECISIONS.md). Use when work involves meaningful tradeoffs.
governance-sync
End-of-work audit that identifies which governance artifacts should be updated based on actual changes. Use when wrapping a milestone/checkpoint or after multi-file/structural work.
intake-interview
Interview to extract intent, constraints, assumptions, and success criteria for a new system or major feature. Produces an Intake Brief (not a plan, not code).
personalize-repo
Tailor a bootstrapped repo into a project-specific operating system by capturing intent, constraints, and preferences, then updating docs and generating a repo-local REPO_PROFILE.json. Use only when explicitly invoked.
prediction-arbitrage-scout
Scout price discrepancies between Polymarket and Kalshi for discovery and comparison. Read-only; no execution.
cartographer
Generate a deterministic project map (Tree.txt + docs/PROJECT_MAP.md) for a repo. Use only when explicitly invoked.
send-email
Use when sending transactional emails (welcome messages, order confirmations, password resets, receipts), notifications, or bulk emails via Resend API.
shadcn
This skill should be used when the user asks to "add a component", "use shadcn", "install Button", "create Dialog", "add Form", "use DataTable", "implement dark mode toggle", "use cn utility", or discusses UI components, component libraries, or accessible components. Always use the latest shadcn/ui version and modern patterns.
stripe
>-
supabase-expert
>-
tailwindcss
This skill should be used when the user asks to "style with Tailwind", "add CSS", "configure theme", "use @theme", "add custom colors", "implement dark mode", "use container queries", "add responsive design", "use OKLCH colors", or discusses styling, theming, or visual design. Always use the latest Tailwind CSS version and modern patterns.
react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
hooks-builder
>-
mermaid-diagramming
>-
adhd
Parallel divergent ideation for coding agents. Spawns N isolated branches under different cognitive frames (regulator, biology, speedrunner, 10-year-old, $0 budget), scores, clusters, prunes traps, and deepens top survivors. Use on /adhd, "ADHD mode", brainstorm/ideate intents, or open-ended design, architecture, naming, API/SDK surface, and fuzzy-debugging decisions. Skip for syntax, lookups, bugs with known root cause, or closed phrasing ("quick", "standard", "canonical", "textbook").
ast-grep
Structural code work on ast-grep — outline maps before reading source, AST search through the MCP tools with inline rules, durable rule folders enforcing project quality, and syntax-tree rewrites. Use when reading, editing, or searching any code/source file, when authoring or organizing a project's ast-grep rules, and when applying structural rewrites.
code-review
>-
coding-applescript
>-
coding-bash
>-
coding-pg
>-
custodian
Infrastructure custody pass — dispatches infra-custodian over a scope (TEND) or the working diff (REVIEW, the bare default); returns its typed receipt. Use after landing edits to constitutions, RULINGS, routers, laws, standards, or .claude/ definitions, and on "check the infra", "did we miss a ruling".
delegate-agy
>-
delegate-codex
>-
docgen
>-
hostinger
>-
Page 449 of 1657 · 82821 results