Loading...
Loading...
Found 2,136 Skills
Comprehensive thoroughness framework. Auto-invoked when planning features, implementing code, fixing bugs, writing tests, analyzing existing code, auditing features, reviewing architecture, or investigating issues. Forces systematic consideration of all edge cases, failure modes, error scenarios, security implications, state transitions, and hidden assumptions so nothing gets missed. Do NOT invoke for trivial changes like typos, renames, single-line fixes, adding imports, or updating config values.
Deprecated alias for tdd skill
Collaborate on document creation and refinement. Merges contributions, manages versions, and produces unified documents from multiple sources.
Expert guide for writing Effect-TS code, including project setup, core principles, data modeling with Schema, error handling, and the Context.Tag service pattern. Use when writing, refactoring, or analyzing TypeScript code using the Effect library.
QADeputy integration. Manage data, records, and automate workflows. Use when the user wants to interact with QADeputy data.
Execute one scoped change: understand the task, make the smallest complete implementation, test it, verify it, and report.
Core code quality principles for writing maintainable code. Use when reviewing code for design violations, assessing code quality, or applying architectural patterns like composition, immutability, and fail-fast.
Эксперт по интеграционным спецификациям. Используй для документирования интеграций, webhooks, event schemas и data flows.
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.
Build a production-quality CLI tool for any module or application. Auto-detects language, recommends CLI libraries, and follows a 5-step approval-gated workflow: Analyze, Design, Plan, Execute, Summarize. Don't use for building GUI/TUI apps, web APIs, or authoring one-off shell scripts.
Analyze repository and suggest improvements
End-to-end ***plain spec authoring workflow: runs a structured QA interview (product, tech stack, behavior) then produces complete .plain specification files with automated review. Use when the user wants to build something new from scratch or asks to start a new project.