duc01226
- 680 skills
- 0 followers
- 12 repo stars
- yesterday last updated
- ▌ Fix 3 · duc01226 bundle[Implementation] Use when a workflow step or the user asks for root-cause fixes with regression coverage. --target={ci|issue|logs|review|test|types|ui} scopes the issue.
- ▌ Fix 4 · duc01226 bundle[Implementation] Use when a workflow step or the user asks for root-cause fixes with regression coverage. --target={ci|issue|logs|review|test|types|ui} scopes the issue.
- ▌ Product Roadmap 2 · duc01226 bundle[Planning] Use ONLY when the user explicitly requests a product roadmap, roadmap update, or milestone selection — outcome milestones, MVP scope, non-goals, risks, evidence gates.
- ▌ Scenario 2 · duc01226 bundle[Planning] Use when enumerating adversarial scenarios, failure modes, data-integrity risks, state boundaries, access risks, or pre-plan edge cases.
- ▌ Experience Review 2 · duc01226[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).
- ▌ Integration Test Verify 3 · duc01226[Testing] Use when you need to verify integration tests pass after writing and reviewing them.
- ▌ Workflow Seed Test Data 3 · duc01226[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.
- ▌ Architecture Review Full 2 · duc01226 bundle[Architecture] Use when auditing the ENTIRE project architecture and production readiness in one pass — bundles architecture-review + architecture-scalability-review + production-readiness-review at project or diff scope, then synthesizes one consolidated Architecture Health Report.
- ▌ Workflow Greenfield Init 3 · duc01226[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.
- ▌ Git Developer Performance 3 · duc01226 bundle[Git] Use when generating developer KPI, performance, contribution value, story point, man-day, or code-quality reports from local git commit history.
- ▌ Workflow Architecture Audit 3 · duc01226[Workflow] Use when activating the Architecture Audit workflow to review the whole project's architecture, run an architecture health check, or check production readiness/scalability in one pass — read-only, produces one consolidated Architecture Health Report.
- ▌ Integration Test Verify Loop 2 · duc01226 bundle[Testing] Use when you need to drive an integration-test suite to fully green — each round runs /integration-test-verify (whole system by default, or the target named in the prompt), and on ANY failure combines /debug-investigate + /integration-test-review (report-only) to adjudicate the fault (test wrong · test not optimal · source wrong), then /fix to resolve it at the owning layer, then /changes-review on that round's fix diff, then re-runs a FRESH full verify — looping until the whole suite passes its 2-consecutive-green-runs gate with zero failures.
- ▌ Sync Skills Shared Protocols 3 · duc01226[Skill Management] Use when shared protocol checklists change and need propagation across skills.
- ▌ Workflow Review Changes Loop 3 · duc01226[Workflow] Use when you need to run /workflow-review-changes repeatedly in an outer convergence loop until a complete whole-workflow run applies zero fixes — recursive re-review of a fixed scope (branch-diff + current changes) until a clean no-op pass.
- ▌ Architecture Scalability Review 3 · duc01226 bundle[Architecture] Use when grading project architecture and scalability quality for greenfield init or brownfield audit: build/CI scalability, distributed-monolith risk, module isolation, dependency discipline, loose coupling, horizontal scaling, DRY, abstraction, clean architecture, observability, and delivery.
- ▌ Workflow Integration Test Green 3 · duc01226[Workflow] Use when activating the Integration Test Green workflow — drive an integration-test suite to fully green with a bounded convergence loop: verify the whole system (or the named target), adjudicate every failure with /debug-investigate + /integration-test-review before any edit, fix at the owning layer, /changes-review each round's fix diff, re-verify from scratch, then sync spec TCs, the integration-test reference doc, and feature docs.
- ▌ Workflow Write Integration Test 3 · duc01226[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
- ▌ Feature Presentation 3 · duc01226 bundle[Documentation] Use when you need to synthesize all generated specs, PBIs, ideas and mockups into one standalone HTML slide presentation for stakeholders (PO/BA/Dev/QC).
- ▌ Git Conflict Resolve 3 · duc01226[Git] Use when you need to resolve git merge/cherry-pick/rebase conflicts with backup, analysis, and reporting.
- ▌ Scan Codebase Health 3 · duc01226[Documentation] Use when you need to detect codebase health issues: unused exports, doc count-drift, orphan files, stale config references.
- ▌ Workflow Big Feature 3 · duc01226[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.
- ▌ Workflow Idea To Pbi 3 · duc01226[Workflow] Use when activating the Idea to PBI workflow for turning an idea — or a raw product vision/problem — into prioritized PBIs and stories (single-PBI deep mode, or multi-opportunity discovery mode).
- ▌ Workflow Spec To Pbi 3 · duc01226[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.
- ▌ Markdown Novel Viewer 3 · duc01226 bundle[Content] Use when you need background HTTP server rendering markdown files with calm, book-like reading experience.
- ▌ Web Design Guidelines 3 · duc01226 bundle[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.
- ▌ Workflow Code To Spec 3 · duc01226[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.
- ▌ Workflow Feature Spec 3 · duc01226[Workflow] Use when activating the Business Feature Documentation workflow for 8-section tech-free feature docs.
- ▌ Workflow Idea To Spec 3 · duc01226[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.
- ▌ Project Skill Protocol 3 · duc01226 bundle[Utilities] Use when a project needs to add, change, list, or remove its OWN protocol rules layered on top of a framework skill — a named overlay of extra project rules that applies whenever the targeted skill runs, stored with the project rather than in the portable framework. `/project-skill-protocol list` prints every overlay with its target and description; `add` drafts a new overlay and confirms it before writing; `update` applies a surgical change; `delete` removes it. Overlays are ADDITIVE ONLY — they never replace, override, or waive anything the skill already does. Triggers: skill protocol, project protocol, custom protocol for skill, extend a skill, overlay rules, add rules to a skill, project rules for skills, skill protocol overlay.
- ▌ Workflow Review Changes 2 · duc01226 bundle[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.
- ▌ UI UX Pro Max 3 · duc01226 bundle[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
- ▌ Claude Md Init 3 · duc01226 bundle[Documentation] Use when you need initialize, update, or refactor CLAUDE markdown from project-config JSON and codebase scan results.
- ▌ Course Builder 3 · duc01226[Content] Use when you need to build structured learning/teaching course material with Bloom taxonomy objectives, modules, lessons, exercises, and assessments.
- ▌ Project Config 3 · duc01226[Utilities] Use when you need to scan workspace and update docs/project-config JSON to match current project structure.
- ▌ Prompt Enhance 3 · duc01226[Skill Management] Use when enhancing, compressing, or expanding prompts, docs, or skills with attention anchoring [INTELLIGENT ROUTING]. Flag: --op={compress|expand|enhance} (default enhance); --op=compress strips token bloat, --op=expand reconstructs compressed text.
- ▌ Seed Test Data 3 · duc01226[Dev Data] Use when you need to implement or enhance test data seeders that simulate QC happy-path scenarios via application-layer commands. Flag: --mode=review reviews a target seeder (or the current changes / current work-context result) against every universal seed-data rule AND the project-specific seeder conventions — read-only, evidence-backed PASS/FAIL.
- ▌ Workflow Refactor 3 · duc01226[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.
- ▌ Workflow Research 3 · duc01226[Workflow] Use when activating the Research & Synthesis workflow — research a topic via web sources, then synthesize per --output={synthesis|business-eval|marketing|course} (knowledge report, business evaluation, marketing strategy, or course material).
- ▌ Excalidraw Diagram 3 · duc01226 bundle[Utilities] Use when the user wants to visualize workflows, architectures, or concepts as Excalidraw diagram JSON files.
- ▌ Graph Blast Radius 3 · duc01226[Code Intelligence] Use when you need to analyze the blast radius of current code changes using the structural knowledge graph.
- ▌ Workflow Spec Sync 3 · duc01226[Workflow] Use when activating the Test Spec Update (Post-Change) workflow for update test specs and feature docs after code changes, bug fixes, or pr reviews.
- ▌ Workflow Visualize 3 · duc01226[Workflow] Use when activating the Visual Diagram workflow for create visual excalidraw diagrams from codebase investigation or web research.
- ▌ Business Evaluation 3 · duc01226[Content] Use when you need to evaluate business idea viability: Business Model Canvas, financial projections, risk matrix, go-to-market, execution plan.
- ▌ Changes Review Loop 3 · duc01226[Code Quality] Use when you need to combine /changes-review + /fix in a recursive loop — each round runs /changes-review (report-only) to surface validated findings over a fixed diff scope, then /fix to resolve them, then loops again with a FRESH full /changes-review over the CHANGED diff until one complete pass produces zero validated findings (nothing left to fix).
- ▌ Knowledge Synthesis 3 · duc01226[Research] Use when you need to synthesize research findings into structured report using template.
- ▌ Quality Gate Review 3 · duc01226[Project Management] Use when you need to enforce quality gates, verify compliance with standards, track quality metrics, and generate audit trails.
- ▌ Sequential Thinking 3 · duc01226 bundle[AI & Tools] Use when you need to apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification.
- ▌ Tech Stack Research 3 · duc01226[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.
- ▌ Context Optimization 3 · duc01226[Utilities] Use when managing context window usage, compressing long sessions, or optimizing token usage.
- ▌ Spec Clarify 2 · 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 3 · duc01226[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.
- ▌ Workflow E2e 3 · 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 3 · 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 3 · 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 3 · duc01226[Quality] Use when setting up an agent quality harness with feedforward guides and feedback sensors.
- ▌ Pbi Challenge 3 · duc01226[Code Quality] Use when you need an AI-assisted Dev BA PIC review of PBI drafts.
- ▌ Plan Analysis 3 · 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 3 · duc01226[Planning] Use when you need to validate a plan with critical questions interview.
- ▌ Product Owner 3 · duc01226[Project Management] Use when you need to capture ideas, manage product backlogs, apply prioritization frameworks (RICE, MoSCoW), and facilitate stakeholder communication.
- ▌
- ▌ Skill Creator 3 · 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.
- ▌ Why Review Loop 3 · duc01226[Code Quality] Use when you need to combine /why-review + /fix in a recursive loop — each round runs /why-review to find validated findings then /fix to resolve them, then loops again over the CHANGED target until a fresh full /why-review produces zero findings (nothing left to fix).
- ▌ Workflow Bugfix 3 · duc01226[Workflow] Use when activating the Bug Fix workflow for systematic debugging with root cause investigation, fix, and verification.
- ▌ Integration Test 2 · duc01226 bundle[Testing] Use when you need to generate or review integration tests.
- ▌ Business Analyst 3 · duc01226[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.
- ▌ DOCX To Markdown 3 · duc01226 bundle[Document Processing] Use when you need to convert Microsoft Word ( DOCX) files to Markdown with GFM support (tables, images, code blocks).
- ▌ Knowledge Review 2 · duc01226[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.
- ▌ Markdown To DOCX 3 · duc01226 bundle[Document Processing] Use when you need to convert markdown files to Microsoft Word ( DOCX) format with GFM support and math rendering.
- ▌ Strategy Builder 3 · duc01226[Content] Use when you need to build marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.
- ▌ Workflow Feature 3 · duc01226[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.
- ▌ Branch Comparison 3 · duc01226[Git] Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed.
- ▌ Debug Investigate 3 · duc01226[Fix & Debug] Use when investigating a bug's root cause — reproduce the symptom, trace it end-to-start through the code, form and test hypotheses, and pinpoint the defect before any fix.
- ▌ Feature Implement 3 · duc01226[Implementation] Use when you need to implement a feature [step by step].
- ▌ Graph Connect API 3 · duc01226[Code Intelligence] Use when you need to detect frontend-to-backend API connections using the knowledge graph.
- ▌ Memory Management 3 · duc01226[Utilities] Use when saving or recovering task progress across sessions via file checkpoints — especially before context compaction.
- ▌ Graph Query 3 · duc01226[Code Intelligence] Use when you need to query code relationships and connections using the structural knowledge graph.
- ▌ Graph Trace 3 · duc01226[Code Intelligence] Use when investigating what happens when code executes, understanding blast radius, or tracing frontend-to-backend flows.
- ▌ Investigate 3 · 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 3 · duc01226[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.
- ▌ Refactoring 3 · duc01226[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.
- ▌ Release Doc 3 · duc01226[Documentation] Use when you need to generate a detailed, AI-analyzed release document from git history over a time range or custom prompt.
- ▌ Coding Level 3 · duc01226[Utilities] Use when you need to set coding experience level for tailored explanations.
- ▌ Custom Agent 3 · duc01226[AI & Tools] Use when you need create, verify, or enhance Claude Code custom agents (Claude Code custom agent files).
- ▌ Figma Design 3 · duc01226 bundle[Frontend] Use when you need to extract design context from Figma URLs via MCP, REST API, or screenshot fallback.
- ▌ Graph Export 3 · 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 3 · 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 2 · 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 3 · 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 Discovery 3 · duc01226[Investigation] Use when about to author a new Feature Spec from an idea — investigate all existing Feature Specs AND related code logic first to surface related/overlapping/affected specs, missing features, missing test cases/user stories, system unknowns, and the invariant landscape, before any spec is drafted.
- ▌ Start Workflow 3 · duc01226[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.
- ▌ Webapp Testing 3 · duc01226 bundle[Testing] Use when you need individual page/component testing with Python Playwright scripts.
- ▌ Security Review 2 · duc01226 bundle[Code Quality] Use when you need to perform a security review or audit on any scope — application code (OWASP Top 10 2025), secrets exposure, dependency/supply-chain malware, third-party repository vetting before install, infrastructure/config, CI/CD pipeline, AI-agent risks, and host/VPS compromise detection.
- ▌ Code Simplifier 3 · duc01226[Code Quality] Use when you need to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.
- ▌ Domain Analysis 3 · duc01226[Architecture] Use when you need to analyze business domain: bounded contexts, aggregates, entities, ERD, domain events, and cross-context integration.
- ▌ Estimate Actual 3 · duc01226[Planning] Use when calibrating estimates from actual code, diff, PR scope, and developer time.
- ▌ Markdown To PDF 3 · duc01226 bundle[Document Processing] Use when you need to convert markdown files to PDF with syntax highlighting and custom CSS support.
- ▌ Market Analysis 3 · duc01226[Research] Use when you need to analyze market landscape: competitors, sizing (TAM/SAM/SOM), trends, SWOT, customer segments.