Claude Skills by duc01226

[Documentation] Use when generating a demo guide, demo script, or sprint-demo walkthrough covering user stories and their test cases.

[Project Management] Use when mapping or visualizing feature dependencies between modules, services, and work items.

[Project Management] Use when creating UI/UX design specs from requirements, PBIs, or stories. Flag: --mode=wireframe converts sketches into structured specs.

[Design] Use when creating or describing a UI design. Flags: --mode={fast|good|describe|screenshot|video} (default fast), --lane={product|marketing} (default product).

[DevOps] Use when deploying to Cloudflare (Workers, R2, D1, KV, Pages), Docker, or GCP (Compute Engine, GKE, Cloud Run).

[Documentation] Use when initializing project reference docs via hook + scan skills.

[Documentation] Use when finding technical documentation for a library, framework, repository, or implementation topic.

[Documentation] Use when updating impacted documentation after code, spec, or test changes.

[Code Quality] Use when enhancing documentation, adding code comments, creating API docs, or updating READMEs.

[Document Processing] Use when converting Word DOCX files to Markdown with GFM support.

[Architecture] Use when analyzing the business domain — bounded contexts, aggregates, entities, ERD, domain events, cross-context integration.

[DDD Quality] Use when reviewing domain entities and value objects for DDD design quality.

[Code Quality] Use when validating a PBI against Definition of Ready before grooming.

[User-Invoked] Use ONLY when the user explicitly types /dual-ai — fans one prompt or workflow out to parallel Claude Code + Codex CLI sessions. NEVER auto-activate.

[Testing] Use when generating, updating, or maintaining E2E tests from recordings, specs, or code changes.

[Planning] Use when calibrating estimates against actual code, diff, PR scope, and developer time.

[Utilities] Use when visualizing workflows, architectures, or concepts as Excalidraw diagram JSON.

[Testing] Use when reviewing a running user experience or observable output (UI, API, CLI, service) — run it locally, drive it end to end like a user, gate on runtime/console logs and captured screens, set a baseline, or adjudicate a regression. Flag: --rounds=N (default 3; 0 = report-only).

[Implementation] Use when implementing a feature step by step.

[Documentation] Use when synthesizing specs, PBIs, ideas, and mockups into one standalone HTML slide deck for stakeholders.

[Frontend] Use when extracting design context from Figma URLs via MCP, REST API, or screenshot fallback.

[Implementation] Use when analyzing and fixing issues. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix.

[Git] Use when resolving git merge, cherry-pick, or rebase conflicts with backup and analysis.

[Git] Use when generating developer KPI, contribution, story-point, man-day, or code-quality reports from git history.

[Git] Use when merging code from one branch to another.

[Code Intelligence] Use when analyzing the blast radius of current code changes via the knowledge graph.

[Code Intelligence] Use when building, updating, or syncing the code knowledge graph. Flag: --scope={full|update|sync} (default auto-detect).

[Code Intelligence] Use when detecting frontend-to-backend API connections via the knowledge graph.

[Code Intelligence] Use when exporting the code knowledge graph. Flag: --format={json|mermaid} (default json).

[Code Intelligence] Use when querying code relationships and connections via the knowledge graph.

[Code Intelligence] Use when tracing what happens as code executes, blast radius, or frontend-to-backend flows.

[Planning] Use when starting a new project from scratch — idea, research, domain modeling, tech stack, implementation plan.

[Quality] Use when setting up an agent quality harness with feedforward guides and feedback sensors.

[Project Management] Use when capturing new ideas, feature requests, or concepts for later refinement.

[Code Quality] Use when reviewing integration tests for assertion quality, bug protection, and repeatability, and verifying changed code has spec-traceable coverage.

[Testing] Use when driving an integration-test suite to fully green — verify, adjudicate each failure, fix at the owning layer, re-verify, until 2 consecutive green runs.

[Testing] Use when verifying integration tests pass after writing and reviewing them.

[Testing] Use when generating or reviewing integration tests.

[Fix & Debug] Use when investigating and explaining how existing features or logic work. Flag: --mode=explain gives a developer-narrative walkthrough.

[Utilities] Use when recording an engineering journal entry — decisions, blockers, lessons, progress notes.

[Research] Use when reviewing knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.

[Research] Use when synthesizing research findings into a structured report.

[Utilities] Use when teaching Claude a lesson that persists across sessions.

[Code Quality] Use when running linters and fixing issues on backend or frontend.

[Quality] Use when configuring code quality tooling for a tech stack — linters, formatters, static analysis, pre-commit hooks, CI gates.

[Decision Support] Use when pressure-testing an irreversible, high-stakes decision with adversarial AI advisors.

[Content] Use when serving markdown files in a calm, book-like reading view over local HTTP.

[Document Processing] Use when converting Markdown to Word DOCX with GFM and math rendering.

[Document Processing] Use when converting Markdown to PDF with syntax highlighting and custom CSS.

[Research] Use when analyzing the market landscape — competitors, TAM/SAM/SOM sizing, trends, SWOT, customer segments.