Loading...
Loading...
Found 1,003 Skills
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report. Use when user says "review code", "quality check", "is it ready to ship", "final review", or after /deploy completes. Do NOT use for planning (use /plan) or building (use /build).
Comprehensive quality assurance skill for validating and verifying project deliverables and educational content. This skill should be used when establishing quality standards, performing verification and validation activities, conducting reviews and audits, implementing continuous improvement processes, or ensuring deliverables meet requirements and stakeholder expectations. Provides systematic approaches to prevent defects and ensure excellence.
Reviews finished and in-progress digital products to assess adherence to design specifications and discover potential issues. Use when user says "design review", "design QA", "QA review", "check implementation", "visual bugs", "compare to design", "match the specs", "review the build", "before launch", "pre-launch review", "implementation review", "verify design", "design validation", "spacing issues", "visual discrepancies", "accessibility review", "WCAG compliance", or "responsive testing". Validates implementation against design intent, identifies visual and interaction discrepancies, and provides actionable feedback. Do NOT use when still designing concepts (use design-concepts), need to understand users (use design-research), or nothing has been built yet.
Post-implementation reality check. Run after tests pass, before declaring done. Use when completing a feature, bug fix, refactor, or integration — or when asked to verify, sanity check, or confirm something actually works.
Autonomous development agent that picks tasks from a project board (Jira, ClickUp, GitHub Issues), explores the codebase, implements the solution, opens a PR, and notifies the team. Configurable per-project via project files in ~/.config/delivering-tickets/projects/. Use this skill when the user asks to "work on a ticket", "pick up a task", "implement issue X", "work autonomously on the board", "take the next task", or any variation of autonomous task execution from a project board. Also triggers when the user mentions delivering-tickets, project configuration, or wants to set up autonomous development workflows for their team. Available commands: /delivering-tickets (start), /delivering-tickets:check (check replies), /delivering-tickets:status (workflow status), /delivering-tickets:setup (verify environment), /delivering-tickets:project (manage projects). Do NOT use for general coding without a ticket, standalone code reviews, project setup without a board configured, or questions unrelated to task execution from a project board.
Forces exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology. MUST trigger when: (1) any task has failed 2+ times or you're stuck in a loop tweaking the same approach; (2) you're about to say 'I cannot', suggest the user do something manually, or blame the environment without verifying; (3) you catch yourself being passive — not searching, not reading source, not verifying, just waiting for instructions; (4) user expresses frustration in ANY form: 'try harder', 'stop giving up', 'figure it out', 'why isn't this working', 'again???', or any similar sentiment even if phrased differently. Also trigger when facing complex multi-step debugging, environment issues, config problems, or deployment failures where giving up early is tempting. Applies to ALL task types: code, config, research, writing, deployment, infrastructure, API integration. Do NOT trigger on first-attempt failures or when a known fix is already executing successfully.
React useEffect anti-pattern detection and correction guide. Use this skill whenever writing, reviewing, or modifying any React component that contains useEffect, or when about to add a useEffect hook. Also trigger when you see patterns like "setState inside useEffect", "effect chains", "derived state in effect", or "notify parent in effect". Covers 12 specific scenarios where Effects are unnecessary or misused, with correct alternatives. Even if the useEffect looks reasonable at first glance, consult this skill to verify it's truly needed.
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production".
This skill applies when OpenStoryline has been installed, and the user needs to start local MCP/Web services, create or continue a session, send editing instructions, perform multi-round re-editing, verify rendered video outputs, or make Chinese requests such as "启动 OpenStoryline", "把 OpenStoryline 跑起来", "用 OpenStoryline 剪视频".
Use after planning completes and before any implementation begins. Verifies that the current phase contract, story map, and bead graph are structurally sound, execution-ready, and aligned with locked decisions. Use for prompts like "validate the plan", "is this ready to build?", "check the bead graph", "verify execution readiness", or whenever there is doubt about whether the current phase is safe to execute.
Systematically review biblical content through a 10-point quality checklist. Works with bible-buddy reference files, any file path, URLs, or text pasted directly in the conversation. Use when asked to review, audit, check, or verify biblical content. Trigger on: "檢查冷知識", "fact check", "檢查經文", "review bible", "幫我檢查這段", "bible-fact-check", or any request to find errors, duplicates, or issues in biblical reference content.
Query and aggregation-pipeline optimization rules for Azure DocumentDB — using `explain("executionStats")` to verify index usage and avoid `COLLSCAN`. Use when reviewing a specific query, diagnosing a slow query, or validating that an index is actually being used. For full index-design workflow, see the `documentdb-query-optimizer` skill.