Loading...
Loading...
Found 91 Skills
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says "archive this". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.
Update documentation based on lessons learned. Use after completing work to capture learnings and prevent future issues.
Product design, feature planning, and technical architecture for new projects. Explores the problem space through deep requirements gathering, suggests creative features, makes architecture decisions, and produces a structured MVP plan with scope boundaries, a future roadmap, and a deliverable tracker. Uses plan mode for deliberate thinking before writing any artifacts. Use when the user says "mvp", "plan a product", "design features", "what should I build", "feature planning", "scope an MVP", or describes a product they want to plan.
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.
Builds new project-specific skills or audits existing ones against the seven principles. Use when user says 'build a skill', 'create a skill', 'review this skill', 'audit our skills', 'is this skill good', 'what skills should we have', or 'clean up our skills directory'. Do NOT use for CLAUDE.md files (use create-or-audit-claude-md), subagents (use create-or-audit-agent), or hooks (use create-or-audit-hook).
Use this skill to ingest external materials into the current project-scoped Obsidian KB as source notes under Sources/Papers, Sources/Web, Sources/Docs, Sources/Data, Sources/Interviews, or Sources/Notes.
Convert the current conversation into a spec and publish it to the project issue tracker — no interviews, only synthesize the already discussed content.
Validate project space structure, boilerplate docs, and consistency with ideas/
A general research briefing template for quickly organizing research questions, distilling facts and uncertainties, and providing suggestions for subsequent experiments/interviews/data extraction.
Generate various types of documents based on the current project/code, supporting four types: thesis chapters, project sorting, key issues, and resume project descriptions. Use this when the user mentions generating thesis chapters, project sorting, technical difficulties, or resume project descriptions.
Initialize .chalk folder — analyze a repo and capture its architecture, coding style, tech stack, design assets, and project identity into chalk.json and structured docs