Claude Skills by duc01226

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

[Workflow] Use when generating, updating, or maintaining E2E/Playwright tests. Flag: --source={changes|recording|update-ui}.

[Process] Use when ending the active workflow and clearing its state.

[Workflow] Use when creating or updating 8-section tech-free business feature documentation.

[Workflow] Use when implementing a well-defined feature, adding a component, or building a capability — including TDD and spec-driven test-first work.

[Workflow] Use when starting a new project from scratch — full waterfall inception from idea through implementation and integration testing.

[Workflow] Use when turning an idea or product vision into prioritized PBIs and stories (single-PBI deep mode or multi-opportunity discovery).

[Workflow] Use when turning a raw idea, vision, or problem into ONE canonical Feature Spec. Stops at the reviewed spec; chain workflow-spec-to-pbi for a backlog.

[Workflow] Use when driving an integration-test suite to fully green — adjudicate every failure before editing, fix at the owning layer, re-verify, then sync specs and docs.

[Workflow] Use when restructuring, reorganizing, or cleaning up code without changing behavior.

[Workflow] Use when researching a topic from web sources then synthesizing. Flag: --output={synthesis|business-eval|marketing|course}.

[Workflow] Use when running /workflow-review-changes repeatedly until a complete pass applies zero fixes.

[Workflow] Use when reviewing uncommitted, staged, or unstaged changes before committing — review, fix, and re-review until the severity bar clears.

[Workflow] Use when seeding test data or implementing idempotent QC happy-path seeders.

[Workflow] Use when updating test specs and feature docs after code changes, bug fixes, or PR reviews.

[Workflow] Use when converting canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.

[Workflow] Use when creating Excalidraw diagrams from codebase investigation or web research.

[Workflow] Use when writing integration tests spec-first, converting test specs into test code, or adding coverage to untested code.

[Git] Use when creating an isolated git worktree for parallel development.