Loading...
Loading...
Found 2,894 Skills
[Tooling & Meta] ClaudeKit usage guide - just type naturally
Use when creating Storybook stories, naming story exports, organizing story files, or reviewing story naming conventions. Ensures story names describe user scenarios and component states rather than implementation details.
Brief description of what this skill does and when to use it. Be specific about capabilities and use cases to help agents decide when to load this skill.
Utiliza esta habilidad cuando el usuario quiera crear, modificar o analizar una nueva "Skill" (habilidad) para Antigravity. Proporciona instrucciones sobre estructura de carpetas, YAML y Markdown.
Turn vague ideas into a validated design/spec through structured brainstorming. Use before any creative work (new features, UI/components, behavior changes, refactors) and whenever a user asks to brainstorm, define requirements, propose approaches, or write a design doc.
Scaffolds the project and sets up the Conductor environment for Context-Driven Development. Use when starting a new project or initializing the Conductor workflow in an existing (brownfield) project. This skill guides the user through project discovery, product definition, tech stack configuration, and initial track planning.
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
Framework for documenting compliant patient journeys with touchpoints, consent, and escalation paths.
Extracts valuable learnings, patterns, and workflows from conversations and persists them as reusable skill files. This skill should be used when a complex problem was solved, a valuable workflow was discovered, or the user explicitly requests to capture knowledge as a skill.
Transform conversations and ideas into structured technical specifications. Outputs: User stories, acceptance criteria, technical requirements, edge cases. Use when user wants to document requirements before coding. Triggers: write spec, create user stories, document requirements, /spec
Requirements Analysis Assistant that converts vague requirements into structured documents. Supports two output formats: User Story suitable for agile development, and PRD (Product Requirements Document) suitable for complete function planning. Clarifies ambiguities through targeted questions.
Create a plan for review: idea branch, plan file, and draft PR. Part of the Plot workflow. Use on /plot-idea.