duc01226
- 157 skills
- 0 followers
- 1 week ago last updated
- ▌ Demo Guide · duc01226 bundle[Documentation] Use when you need to generate a step-by-step demo guide (demo script / walkthrough) covering all main user stories and their test cases — scope from a named feature, else the current working context, else confirm with the user — explaining for each case how the domain data is stored/changed and how the domain solves the feature. Triggers: demo guide, generate demo guide, demo script, demo walkthrough, how to demo, prepare demo, sprint demo, user story demo.
- ▌ Dependency · duc01226[Project Management] Use when you need to map and visualize feature dependencies between modules, services, and work items.
- ▌ Greenfield · duc01226[Planning] Use when you need to start a new project from scratch with full waterfall inception — idea, research, domain modeling, tech stack, and implementation plan.
- ▌ Pbi Mockup · duc01226 bundle[Project Management] Use when you need to generate an HTML mockup report from PBI and story artifacts.
- ▌ Prioritize · duc01226[Project Management] Use when you need to prioritize backlog items using RICE, MoSCoW, or Value-Effort frameworks.
- ▌ Spec Index · duc01226[General] Use when you need to (re)generate a DERIVED navigation index, cross-capability ERD, or reimplementation guide assembled FROM the canonical Feature Specs under docs/specs/**. Never extracts a separate A-E engineering tree.
- ▌ Sync Codex · duc01226 bundle[Codex] Use when you need to run the full Codex mirror sync + verify pipeline (migrate → hooks → context → verify) standalone, no npm/package JSON needed.
- ▌ Claude Code · duc01226 bundle[Utilities] Use when you need Claude Code CLI setup, configuration, troubleshooting, and feature guidance.
- ▌ Copywriting · duc01226[Content] Use when you need to create high-converting copy for marketing materials, social media, landing pages, email campaigns, and product descriptions.
- ▌ Design Spec · duc01226[Project Management] Use when you need to create UI/UX design specifications from requirements, PBIs, or user stories. Use --mode=wireframe to convert hand-drawn/digital wireframes or UI sketches into structured specs.
- ▌ Docs Seeker · duc01226 bundle[Documentation] Use when finding technical documentation for libraries, frameworks, repositories, or implementation topics.
- ▌ Graph Build · duc01226[Code Intelligence] Use when you need to build, update, or sync the code review knowledge graph. Flag: --scope={full|update|sync} (default auto-detect); --scope=full forces a full rebuild, --scope=update re-parses uncommitted working-tree changes, --scope=sync syncs committed git changes then updates the working tree.
- ▌ Graph Query · duc01226[Code Intelligence] Use when you need to query code relationships and connections using the structural knowledge graph.
- ▌ Graph Trace · duc01226[Code Intelligence] Use when investigating what happens when code executes, understanding blast radius, or tracing frontend-to-backend flows.
- ▌ Investigate · duc01226[Fix & Debug] Use when you need to investigate and explain how existing features or logic work. Flag: --mode=explain produces a one-way developer-narrative explanation (Purpose → How → Why → Impact) tuned by coding level; use /understand for the standalone prompt-driven explainer.
- ▌ LLM Council · duc01226[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.
- ▌ Refactoring · duc01226[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.
- ▌ Release Doc · duc01226[Documentation] Use when you need to generate a detailed, AI-analyzed release document from git history over a time range or custom prompt.
- ▌ Docs Update · duc01226 bundle[Documentation] Use when updating impacted documentation after code, spec, or test changes.
- ▌ Coding Level · duc01226[Utilities] Use when you need to set coding experience level for tailored explanations.
- ▌ Custom Agent · duc01226[AI & Tools] Use when you need create, verify, or enhance Claude Code custom agents (Claude Code custom agent files).
- ▌ Figma Design · duc01226 bundle[Frontend] Use when you need to extract design context from Figma URLs via MCP, REST API, or screenshot fallback.
- ▌ Graph Export · duc01226[Code Intelligence] Use when you need to export the code review knowledge graph. Flag: --format={json|mermaid} (default json); --format=json dumps the full graph to a JSON file, --format=mermaid renders a single file as a Mermaid flowchart diagram.
- ▌ Linter Setup · duc01226[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.
- ▌ Plan Execute · duc01226[Implementation] Use when you need to start coding & testing an existing plan. Flags: --approval=off (auto/trust mode, no approval gate), --tests=off (skip the test step), --parallel={auto|on|off} (default off — sequential; --parallel/=on opts in to parallel sub-agent waves; =auto fans out only when the plan declares PAR/SEQ tags and write sets).
- ▌ Project Init · duc01226 bundle[Utilities] Use when initializing or re-evaluating portable project context: project-config, project-reference docs, CLAUDE.md, AGENTS.md, universal agent rules, hookless setup. Triggers on: project init, init project, missing project-config, missing project docs, missing CLAUDE.md, missing AGENTS.md.
- ▌
- ▌ Spec Clarify · duc01226 bundle[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.
- ▌ Web Research · duc01226[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.
- ▌ Workflow E2e · duc01226[Workflow] Use when activating the E2E testing workflow to generate, update, or maintain Playwright/E2E tests. Pick mode with --source={changes|recording|update-ui}.
- ▌
- ▌ Custom Prompt · duc01226 bundle[Utilities] Use when the user invokes, lists, saves, updates, or deletes a PROJECT-SPECIFIC saved prompt — a named, reusable procedure stored with the project rather than in the portable framework. `/custom-prompt list` prints every defined prompt with its description; `/custom-prompt <free-text request>` matches the request to the closest saved prompt and executes it only after a confirmation gate; `/custom-prompt save|update|delete ...` maintains the registry — save never stores raw wording, it drafts the best version of the prompt and confirms the name, description, inferred goal, and steps with the user first. Triggers: custom prompt, custom prompts, list custom prompts, save this prompt, save this prompt task, update this prompt, my saved prompt, project prompt, playbook, recipe, runbook.
- ▌
- ▌ Documentation · duc01226[Code Quality] Use when the user asks to enhance documentation, add code comments, create API docs, improve technical documentation, document code, or update README files.
- ▌ Harness Setup · duc01226[Quality] Use when setting up an agent quality harness with feedforward guides and feedback sensors.
- ▌ Pbi Challenge · duc01226[Code Quality] Use when you need an AI-assisted Dev BA PIC review of PBI drafts.
- ▌ Plan Analysis · duc01226[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.
- ▌ Plan Validate · duc01226[Planning] Use when you need to validate a plan with critical questions interview.
- ▌ Product Owner · duc01226[Project Management] Use when you need to capture ideas, manage product backlogs, apply prioritization frameworks (RICE, MoSCoW), and facilitate stakeholder communication.
- ▌
- ▌ Skill Creator · duc01226 bundle[Skill Management] Use when creating a new Claude Code skill, adding reference files or scripts to an existing skill, scanning/fixing invalid skill headers, or optimizing/packaging skills. Triggers on: create skill, new skill, add skill reference, add skill script, fix skill, validate skill, package skill.
- ▌
- ▌
- ▌ Fix · duc01226[Implementation] Use when you need to analyze and fix issues [INTELLIGENT ROUTING]. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix; --target=types resolves TypeScript errors inline.
- ▌ Idea · duc01226[Project Management] Use when capturing new ideas, feature requests, or concepts for future refinement.
- ▌ Lint · duc01226[Code Quality] Use when you need to run linters and fix issues for backend or frontend.
- ▌ Scan · duc01226 bundle[Documentation] Use when scanning the codebase to (re)generate ONE project-reference doc. Parameterized by `--target=<key>`: 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. Shared 4-phase scan engine; per-target detail lives in references/targets.md. `ui-system` is an orchestrator meta-target (`kind: orchestrator`) that runs the 3 UI child scans in parallel instead of the 4-phase engine.
- ▌ Spec · duc01226 bundle[Documentation] Use to author, audit, amend, or test-spec a business Feature Spec. The single spec skill — modes draft|init|update|audit|amend create/maintain the tech-free 8-section Feature Spec; draft authors a provisional spec from an idea/requirement (no code yet, Evidence: TBD); tests generates Section 8 TC-{FEATURE}-{NNN} test specifications; sync reconciles §8 TCs ↔ executing test code. Per-mode procedure lives in references/{author,tests,sync}.md.
- ▌
- ▌ Plan · duc01226 bundle[Planning] Use when you need intelligent plan creation with prompt enhancement. Flag: --mode={ci|cro} (default none — standard planning); --mode=ci plans a fix from a GitHub Actions CI run/log, --mode=cro plans conversion-rate optimization (25-item CRO framework).
- ▌ Learn · duc01226[Utilities] Use when you need to teach Claude lessons that persist across sessions.
- ▌ Scout · duc01226[Investigation] Use when quickly locating relevant files and affected areas across a large codebase.
- ▌ Story · duc01226[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
- ▌ Commit · duc01226[Git] Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Flag: --push (a.k.a. "commit and push") stages + commits + pushes to remote in one shot.
- ▌ Design · duc01226 bundle[Design] Create or describe a UI design — quick (fast), immersive (good), or recreated/described from a screenshot or video, in a product-UI or marketing/creative lane. Dispatch via --mode={fast|good|describe|screenshot|video} (default fast) and --lane={product|marketing} (default product).
- ▌ Devops · duc01226 bundle[DevOps] Use when deploying to Cloudflare (Workers, R2, D1, KV, Pages), Docker, or GCP (Compute Engine, GKE, Cloud Run).
- ▌ Refine · duc01226[Project Management] Use when converting ideas to PBIs, validating problem hypotheses, adding acceptance criteria, or refining requirements.