Loading...
Loading...
Found 2,038 Skills
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Expert guidance for R package development following best practices for devtools, testthat, roxygen2, and R ecosystem tools
REQUIRED skill for planning and designing coding tasks before implementation. Use this skill when: (1) User asks to "plan", "design", "create a plan", or "think before coding" (2) Complex tasks requiring multiple files or steps (3) Tasks involving both backend and frontend changes (4) Breaking down ambiguous requirements into concrete tasks This skill ensures plans are properly documented, saved as markdown, reviewed by subagent, and registered as todos before any code is written. Do NOT skip this skill for non-trivial tasks.
Scans all skill directories in the repository to generate a comprehensive global map of agent capabilities, inputs, and outputs. Use when you need to understand the full potential of your agent library or when a master agent needs to decide which sub-agent skill to invoke for a complex task.
Maintain durable project context in `tasks/context.md` (state, decisions, milestones, gotchas, optional context links), inline during other workflows or standalone for cleanup/backfill. Triggers: update context.md, decision log, record project context, capture high-value reference links that improve context handoff.
Keep README.md in sync with code changes (APIs, features).
Maintain project brain with architectural decisions in memory file.
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bug", or describes a bug they encountered. Asks probing questions about reproduction steps, environment, patterns, impact, and context that help isolate the root cause. Continues until the bug is well-understood, then writes a detailed investigation/fix plan.
Epic orchestration - PM + Tech Lead for planning and formatted execution.
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
Keep the 0 Finance CLI aligned with product capabilities.
1. Requirement Gathering