Claude Skills by duc01226

[Utilities] Use when saving or recovering task progress across sessions via file checkpoints, especially before compaction.

[Code Quality] Use when analyzing package upgrades, outdated dependencies, npm/NuGet update plans, or breaking changes.

[Code Quality] Use when running an AI-assisted Dev BA PIC review of PBI drafts.

[Project Management] Use when generating an HTML mockup report from PBI and story artifacts.

[Document Processing] Use when converting PDFs to Markdown, including scanned documents via OCR.

[Debugging] Use when analyzing or optimizing performance — slow queries, N+1, indexing, API latency, memory/GC, concurrency, algorithmic complexity, caching, frontend rendering and Core Web Vitals.

[Planning] Use when the user supplies a plan file and asks to analyze it, assess impact, or verify planned changes.

[Implementation] Use when coding and testing an existing plan. Flags: --approval=off, --tests=off, --parallel={auto|on|off} (default off).

[Planning] Use when auto-reviewing a plan for validity, correctness, and best practices — recursive until the severity exit bar clears.

[Planning] Use when validating a plan through a critical-questions interview.

[Planning] Use when creating an implementation plan. Flag: --mode={ci|cro} (default standard); ci plans a fix from a CI run, cro plans conversion-rate optimization.

[Git] Use when creating a pull request in the standard format.

[Project Management] Use when prioritizing backlog items with RICE, MoSCoW, or Value-Effort.

[Utilities] Use when applying structured problem-solving frameworks to complex, blocked, recurring, or uncertain decisions.

[Project Management] Use when capturing ideas, managing backlogs, applying prioritization frameworks, or facilitating stakeholder communication.

[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update, or milestone selection — outcome milestones, MVP scope, non-goals, risks, evidence gates.

[Code Quality] Use when reviewing service-layer and API changes for production readiness.

[Utilities] Use when scanning the workspace to update docs/project-config.json to match current structure.

[Utilities] Use when initializing or re-evaluating portable project context — project-config, reference docs, CLAUDE.md, AGENTS.md, static-context setup.

[Project Management] Use when generating project status reports, tracking dependencies, managing risk registers, or facilitating team syncs.

[Utilities] Use when a project adds, changes, lists, or removes its OWN protocol rules layered over a framework skill. Overlays are ADDITIVE ONLY. Subcommands: list | add | update | delete.

[Skill Management] Use when enhancing, compressing, or expanding prompts, docs, or skills. Flag: --op={compress|expand|enhance} (default enhance).

[Code Quality] Use when proving a fix is correct via adversarial proof traces — a skeptic tries to DISPROVE it first, with confidence scoring and evidence chains.

[Project Management] Use when enforcing quality gates, verifying standards compliance, tracking metrics, or generating audit trails.

[Code Quality] Use when running the quality gate checklist.

[Utilities] Use when restoring workflow context from a checkpoint after session loss.

[Code Quality] Use when restructuring code without changing behavior — extract method/class, rename, move, inline.

[Project Management] Use when converting ideas to PBIs, validating problem hypotheses, or adding acceptance criteria.

[Documentation] DEPRECATED — use /release-notes instead for any release document or release notes, at any scope.

[Git] Use when creating release notes or a release document from git history at any scope (tag-to-tag, branch-to-branch, time range), producing markdown plus a standalone HTML presentation.

[User-Invoked] Use when creating, updating, or previewing Remotion videos.

[Planning] Use when researching and planning technical solutions that are scalable, secure, and maintainable.

[Architecture] Use when scaffolding reusable OOP/SOLID project foundations before feature implementation.

[Documentation] Use when orchestrating all reference doc scans in parallel.

[Documentation] Use when detecting codebase health issues — unused exports, doc count-drift, orphan files, stale config references.

[Documentation] Use when (re)generating ONE project-reference doc. Flag: --target={project-structure|backend-patterns|frontend-patterns|scss-styling|design-system|code-review-rules|domain-entities|feature-spec|docs-index|e2e-tests|integration-tests|seed-test-data|ui-system}.

[Planning] Use when enumerating adversarial scenarios, failure modes, data-integrity risks, state boundaries, access risks, or pre-plan edge cases.

[Code Quality] Use when performing a security review or audit — OWASP Top 10, secrets exposure, dependency/supply-chain malware, infrastructure, CI/CD, AI-agent risks, host compromise.

[Dev Data] Use when implementing or enhancing test-data seeders that simulate QC happy paths via application-layer commands. Flag: --mode=review audits a seeder read-only.

[AI & Tools] Use when applying structured, reflective problem-solving to complex multi-step analysis needing revision and hypothesis verification.

[Skill Management] Use when creating a skill, adding skill references or scripts, fixing invalid skill headers, or packaging skills.

[Code Quality] Use when validating a spec artifact''s decisions with the user — a fresh Feature Spec, a canonical spec before PBI decomposition, or a refined idea plus §8 test specs. Blocking clarification gate.

[Investigation] Use when about to author a new Feature Spec — surface related, overlapping, or affected specs, missing test cases, and the invariant landscape first.

[General] Use when (re)generating a DERIVED navigation index, cross-capability ERD, or reimplementation guide FROM canonical Feature Specs.

[Documentation] Use when authoring, auditing, amending, or test-speccing a business Feature Spec. Modes: draft|init|update|audit|amend build the tech-free 8-section spec; tests generates §8 TCs; sync reconciles TCs with test code.

[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.

[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.

[Content] Use when building a marketing strategy — positioning, channels, messaging, campaigns, budget, KPIs.

[Codex] Use when running the full Codex mirror sync and verify pipeline (migrate, hooks, context, verify).

[Skill Management] Use when shared protocol checklists change and need propagating across skills.