Loading...
Loading...
Found 2,894 Skills
Creates a change proposal with clear intent, defined scope, and technical approach. Trigger: /sdd-propose <change-name>, create proposal, define change scope, sdd proposal.
Regenerate docs/INDEX.md using docs/prompts/PROMPT-INDEX.md with a preflight plan, direct execution, validation, and post-action review (explicit-only).
Conversationally guides the user to a CLAUDE.md file. Starts by inferring what it can from the repo, asks ~8 core questions, then offers optional depth across business, voice, and working-style topics. Use when the user wants a CLAUDE.md but would rather have a conversation than fill out a form.
Authoritative reference for Anthropic products. Use when users ask about product capabilities, access, installation, pricing, limits, or features. Provides source-backed answers to prevent hallucinations about Claude.ai, Claude Code, and Claude API.
Follow this sub-process when fixing bugs—turn the verbal description of "discovered a problem" into a closed loop of verification and repair, leaving three documents in the middle: issue report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code", avoiding several common pitfalls: the problem description in your mind disappears after modification, fixing only the surface without analyzing the root cause, uncontrollable expansion of repair scope that cannot be traced, and not knowing if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing outputs. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only keeping the fix-note.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.
Perform a thorough quality review of a pull request or feature branch before merging. Use this skill whenever the user asks to review a PR, check if code is production-ready, assess quality, verify docs are updated, or asks "is this ready to merge?", "review this PR", "check quality", "is this production ready?", or similar. Also use when reviewing your own work before submitting.
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.
Organize reusable programming patterns / library usages / technical skills that answer "To do this kind of thing, the correct approach is this" into a prescriptive reference library, which can be retrieved and reused as needed during feature-design and issue-analyze phases. Three types: pattern (design patterns, programming idioms), library (usage and pitfalls of a certain library/framework), technique (specific operation skills / command recipes). Trigger scenarios: When the user says "record a trick", "this usage is worth recording", "tricks", "record library usage", or when a skill worth archiving is discovered during feature-design / issue-analyze phases and actively pushed. Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / decisions / explore.
Draft a structured decision memo for Ane. Use when the user asks for a "decision memo", "decision doc", "options paper", "recommendation brief", or equivalent. Produces a scannable document with context, options, recommendation, risks, and reversibility. Applies Ane's CLAUDE.md writing style automatically.
ALWAYS invoke this command when creating, editing, or improving any CLAUDE.md file
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.