Loading...
Loading...
Found 1,486 Skills
Documentation architecture for this repository. Use when creating, updating, or reviewing README.md, CONTRIBUTING.md, or docs/ files. Covers separation of concerns, vendor documentation standards, cross-references, and validation.
Strict Home Assistant Integration Code Review. Used for comprehensive checks before submitting PRs, including Quality Scale rule validation, code style, Config Flow, test coverage, and documentation. Triggered when users say "Review my HA integration", "Check if my code complies with HA specifications", or "Help me review the code ready for submission".
Effective communication strategies for AI-assisted development. Learn context-first prompting, phased interactions, iterative refinement, and validation techniques to get better results from Claude and other AI coding assistants.
Build forms in Inertia Rails applications with proper validation, file uploads, and error handling. Use when implementing forms, handling validation errors, or working with file uploads in Inertia.js with Rails.
Expert blueprint for hierarchical finite state machines (HSM) and pushdown automata for complex AI/character behaviors. Covers state stacks, sub-states, transition validation, and state context passing. Use when basic FSMs are insufficient OR implementing layered AI. Keywords state machine, HSM, hierarchical, pushdown automata, state stack, FSM, AI behavior.
Analyze HM Desktop PRD documents, extract requirement information, verify completeness, check chapter order (Requirement Source → Requirement Background → Requirement Value Analysis → Competitor Analysis → Requirement Description), inspect KEP definitions, detect requirement conflicts, and generate structured analysis reports. Applicable to user requests: (1) Analyze or review PRD documents, (2) Extract KEP lists from requirements, (3) Check PRD completeness or consistency, (4) Map requirements to module architecture, (5) Verify PRD format compliance, (6) Verify completeness of competitor analysis chapters. Keywords: PRD analysis, requirement extraction, KEP verification, completeness check, chapter order validation, competitor analysis check, analyze PRD, requirement extraction, completeness check, chapter order validation
Conduct rigorous 5 Whys root cause analysis with guided questioning, quality scoring, and professional report generation. Use when performing root cause analysis, investigating problems, conducting 5 Whys sessions, troubleshooting recurring issues, or when user mentions "5 whys", "root cause", "why did this happen", "find the cause", or needs to identify underlying causes of defects, failures, or process problems. Includes validation tests, scoring rubric, and countermeasure development.
Full-stack form handling for Inertia Rails: create, edit, delete, multi-step wizard, and file upload forms with validation errors and progress tracking. React examples inline; Vue and Svelte equivalents in references. Use when building any form, handling file uploads, multi-step forms, client-side validation, or wiring form submission to Rails controllers. NEVER react-hook-form. Use `<Form>` for simple forms, useForm for dynamic/programmatic control.
Add new LLM model pricing entries to Langfuse's default-model-prices.json. Use when adding model prices, updating model pricing, creating model entries, adding Claude/OpenAI/Anthropic/Google/Gemini/AWS Bedrock/Azure/Vertex AI model pricing, working with matchPattern regex, pricingTiers, or model cost configuration. Covers model price JSON structure, regex patterns for multi-provider matching, tiered pricing with conditions, cache pricing, and validation rules.
Review Server Actions for security, validation, and best practices in React 19. Use when reviewing forms, mutations, or server-side logic.
Sequential subagent execution with two-stage review gates for implementation plans. Use when executing multi-task plans in current session, when tasks need fresh subagent context to avoid pollution, when formal review cycles (spec compliance then code quality) are required between tasks, or when you need diff-based validation of each task before proceeding.
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.