Loading...
Loading...
Found 1,237 Skills
Use when user asks to "deep review the code", "thorough code review", "multi-pass review", or when orchestrating the Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage), signal detection patterns, and iteration algorithms.
Orchestrate complete Root Cause and Corrective Action (RCCA) investigations using the 8D methodology. Guides team formation (D1) with domain-specific recommendations, problem definition (D2), containment (D3), root cause analysis (D4) with integrated tool selection (5 Whys, Fishbone, Pareto, Kepner-Tregoe, FTA), corrective action (D5-D6), prevention (D7), and closure (D8). Use when conducting RCCA, 8D, root cause analysis, corrective action, failure investigation, nonconformance analysis, quality problems, or customer complaints.
Provides spec writing guidelines with 6 core areas and boundary system. Use when writing SPEC.md, defining requirements, creating project specifications, 요구사항 정의, or 스펙 작성.
Architecture Decision Records and living architecture documentation. Activate when making technology choices, defining system boundaries, recording architectural decisions, or creating/updating ARCHITECTURE.md. Covers ADR format, decision governance, design facilitation, and architectural review.
Intelligent Retrieval Assistant for Cangjie Language Documentation. Supports 4 search modes (Direct Search, PageIndex Intelligent Retrieval, Hybrid Mode, Exploratory Learning). It is used when users need to: (1) Query Cangjie syntax (variable declaration, function definition, generics, etc.), (2) Look up standard library APIs (String, Array, HashMap, etc.), (3) Learn about Cangjie features or get started with the language, (4) Conduct any documentation queries related to Cangjie/cangjie/cj. It uses four MCP tools: cangjie_docs_overview, cangjie_list_docs, cangjie_search, and cangjie_get_doc for intelligent retrieval.
Build production database layers with SQLAlchemy ORM and PostgreSQL. This skill should be used when teaching students to define data models, manage sessions, perform CRUD operations, and connect to PostgreSQL/Neon databases.
Implements reliability patterns including circuit breakers, retries, fallbacks, bulkheads, and SLO definitions. Provides failure mode analysis and incident response plans. Use for "SRE", "reliability", "resilience", or "failure handling".
Creates 03-ui-ux-spec.md (IA, Expo Router route map, screen list, design tokens, component inventory, accessibility) for a new app idea. Use after docfactory-prd to define the visual and interactive layer. Essential for ensuring a consistent, goal-oriented mobile UI and preventing "design drift" during development.
Test coverage verification for refactoring. Apply when verifying existing test coverage, identifying gaps, recommending pre-refactoring tests, and defining verification checkpoints.
Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.
Edit prose to sound more natural, direct, and engaging. Works top-down through four levels (Document → Paragraph → Sentence → Word) with human checkpoints at each stage. Fixes LLM patterns, writerly bad habits, and style deficits. Works for academic papers, reports, memos, essays, blog posts, proposals, and other nonfiction. Use when prose sounds robotic, dull, or inaccessible.
Label taxonomy and triage workflow for GitHub issues. Defines type labels (bug/feature/enhancement/docs/chore), priority levels (critical/high/medium/low), status labels, and triage decision workflow. Use when categorizing and prioritizing issues.