Loading...
Loading...
Found 3,210 Skills
Use when a Beat change is implemented and ready to archive — not for verifying implementation
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.
Guidance for Next.js using the official docs at nextjs.org/docs. Use when the user needs Next.js concepts, configuration, routing, data fetching, or API reference details.
Think like a product manager before changing React Doctor's public surface — CLI commands/flags, the 0–100 score, config (doctor.config.*), the JSON report schema, package APIs (inspect()/diagnose()), the GitHub Action, the website, and the canonical prompts. A step-by-step runbook for a user-facing change — locate the surface, search for a reuse candidate, wire one telemetry metric, add the compatibility artifacts (changeset / schemaVersion / action tag), update docs, and record a kill metric. Not for lint rules, which have their own pipeline. Also runs when the user types `/product-thinking`.
Help users write high-quality Product Requirements Documents (PRD) from scratch, or evaluate/improve existing requirement documents. It is suitable for non-product manager users in vibe coding scenarios who have product ideas but don't know how to structure them. This skill must be used when users mention keywords such as "requirement document", "PRD", "product requirement", "functional document", "I want to make a product/function/App", "help me organize requirements", "is there any problem with the AI-written requirement document", "help me supplement requirements", "I want to make a tool", etc. Even if the description is very brief, this skill must be triggered, and do not skip directly to outputting the document.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
Systematically collect, document, and validate requirements from stakeholders. Ensure clarity, completeness, and agreement before development begins to reduce scope creep and rework.
Run the Codex Readiness unit test report. Use when you need deterministic checks plus in-session LLM evals for AGENTS.md/PLANS.md.
Create AGENTS.md files for project-specific inline rules. Use when adding small, project-specific instructions that should be committed in repos.
Manage project knowledge base. Use "init" to setup, or provide a topic to research.