Claude Skills by duc01226

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

[Category] Use when defining the standard skill description pattern.

[Architecture] Use when designing solution architecture — backend, frontend, data & consistency, integration & APIs, deployment, monitoring, testing, code quality.

[Architecture] Use when auditing the ENTIRE project architecture and production readiness in one pass; bundles architecture-review + scalability + production-readiness into one health report.

[Code Quality] Use when reviewing architecture compliance — layers, messaging, service boundaries, CQRS, repos, entity events, data/consistency/tenancy boundaries.

[Architecture] Use when grading architecture and scalability — build/CI scale, distributed-monolith risk, module isolation, coupling, horizontal scaling, clean architecture, observability.

[Code Quality] Use when reviewing artifact quality before handoff. Flag: --type={pbi|story|spec-tests|design}.

[Utilities] Use when answering a technical or architectural question.

[Content] Use when brainstorming as a PO/BA — ideation for problem-solving, new products, feature enhancement, or outcome-roadmap framing. Flag: --mode={roadmap|scope}.

[Git] Use when comparing branches, analyzing git diffs, or reviewing what changed between two refs.

[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.

[Content] Use when evaluating business idea viability — Business Model Canvas, financial projections, risk matrix, go-to-market, execution plan.

[Documentation] Use when generating or updating changelog entries.

[Code Quality] Use when looping /changes-review + /fix recursively over a fixed diff scope until one full pass clears the severity bar.

[Code Quality] Use when reviewing current changes, staged or unstaged diffs, or branch-to-branch diffs.

[Utilities] Use when saving analysis context to a checkpoint file for recovery.

[Utilities] Use when asking for the claudeKit usage guide.

[Utilities] Use when setting up, configuring, or troubleshooting the Claude Code CLI and its features.

[Documentation] Use when initializing, updating, or refactoring CLAUDE.md from project-config and codebase scans.

[Code Quality] Use when evaluating review feedback, requesting a targeted code-quality review, or verifying completion claims.

[Code Quality] Use when simplifying code for clarity, consistency, and maintainability while preserving behavior.

[Utilities] Use when setting the coding experience level that tailors explanations.

[Git] Use when asked to commit, stage and commit, or save changes. Flag: --push also pushes to remote.

[Utilities] Use when compressing context to reduce token usage.

[Utilities] Use when managing context window usage, compressing long sessions, or optimizing tokens.

[Utilities] Use when loading project context for the current session.

[Content] Use when writing high-converting copy for marketing, social, landing pages, email, or product descriptions.

[Content] Use when building course material — Bloom objectives, modules, lessons, exercises, assessments.

[AI & Tools] Use when creating, verifying, or enhancing Claude Code custom agent files.

[Utilities] Use when invoking, listing, saving, updating, or deleting a PROJECT-SPECIFIC saved prompt (playbook / recipe / runbook). Subcommands: list | <free-text> | save | update | delete.

[DevOps] Use when running or creating database migrations.

[Fix & Debug] Use when finding a bug''s root cause — reproduce, trace end-to-start, test hypotheses, pinpoint the defect before any fix.

[Research] Use when deeply researching the top sources surfaced by web-research.