Claude Skills by duc01226

[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.

[Documentation] Use when (re)generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. A generator — never authors business content. Modes: generate|audit|sync.

[Architecture] Use when researching and comparing tech stack options as a solution architect.

[Testing] Use when running a full-site QA audit (accessibility, performance, security, SEO) with visual reports.

[Testing] Use when running tests locally and analyzing the summary report.

[General] Use when building 3D web apps with ThreeJS, WebGL, or WebGPU.

[Code Quality] Use when reviewing UI/frontend changes for content overflow, responsive layout, flex-vs-fixed sizing, z-index discipline, SCSS/BEM quality, and async loading/error/empty states.

[Frontend] Use when designing aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.

[Process] Use when a developer needs to understand code, plans, decisions, bugs, or concepts — behavior, rationale, trade-offs, testing.

[Utilities] Use when reviewing recent changes and wrapping up the work.

[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.

[Research] Use when starting web research — discover, gather, and triage candidate sources to feed deeper investigation.

[Testing] Use when testing an individual page or component with Python Playwright scripts.

[Code Quality] Use when looping /why-review + /fix recursively over a target until a fresh full review clears the severity bar.

[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, or reports.

[Workflow] Use when auditing the whole project''s architecture, running an architecture health check, or checking production readiness — read-only, one consolidated health report.

[Workflow] Use when implementing a large, ambiguous, or research-driven feature.

[Workflow] Use when fixing a bug, error, or crash — root-cause investigation, fix, verification.

[Workflow] Use when authoring or maintaining the canonical Feature Spec FROM existing code, keeping spec, implementation, and tests in sync. For idea-to-spec use workflow-idea-to-spec.