duc01226
- 632 skills
- 0 followers
- 2 days ago last updated
- ▌ Spec 3 · 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.
- ▌
- ▌ Learn 3 · duc01226[Utilities] Use when you need to teach Claude lessons that persist across sessions.
- ▌ Scout 2 · duc01226[Investigation] Use when quickly locating relevant files and affected areas across a large codebase.
- ▌ Story 3 · duc01226[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
- ▌ Commit 3 · 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 3 · 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).
- ▌ Refine 3 · duc01226[Project Management] Use when converting ideas to PBIs, validating problem hypotheses, adding acceptance criteria, or refining requirements.
- ▌ UI Review · duc01226 bundle[Code Quality] Use when reviewing UI/frontend changes for long-content overflow, responsive multi-screen layout (flex-wrap / row-to-column on small devices), flex-vs-fixed sizing, z-index discipline, SCSS/BEM styling quality, and async UI states & feedback (loading indicator, error surface, empty state).
- ▌ UI Review 2 · duc01226 bundle[Code Quality] Use when reviewing UI/frontend changes for long-content overflow, responsive multi-screen layout (flex-wrap / row-to-column on small devices), flex-vs-fixed sizing, z-index discipline, SCSS/BEM styling quality, and async UI states & feedback (loading indicator, error surface, empty state).
- ▌ Why Review · duc01226 bundle[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.
- ▌ Understand 2 · duc01226 bundle[Process] Use when the developer wants something explained or taught, or wants to know HOW TO REVIEW a change — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a teacher-and-coach review guide, high level first then detail: what was done, a VISUAL MAP (system flowchart, domain ERD, sequence diagrams), the user stories and business rules with their REAL test-case IDs, a REVIEW PATH naming which files to open first and in what order with an exit criterion per stage, the technical concepts needed to follow it, how it works, why THIS solution, every alternative option with pros/cons, the trade-offs accepted, the blast radius, HOW TO TEST AND DEMO the change, the developer's decision levers, and written challenge prompts that provoke the reader to pressure-test the work. Works at ANY scope — from one line of code to the whole project: it SIZES the target into a
- ▌ Why Review 2 · duc01226 bundle[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.
- ▌ Code Review · duc01226 bundle[Code Quality] Use when evaluating review feedback, requesting targeted code-quality review, or verifying completion claims.
- ▌ Plan Review · duc01226 bundle[Planning] Use when you need to auto-review a plan for validity, correctness, and best practices — recursive: review, validate findings with why-review, fix validated findings, full re-review until no findings.
- ▌ Code Review 2 · duc01226 bundle[Code Quality] Use when evaluating review feedback, requesting targeted code-quality review, or verifying completion claims.
- ▌ Plan Review 2 · duc01226 bundle[Planning] Use when you need to auto-review a plan for validity, correctness, and best practices — recursive: review, validate findings with why-review, fix validated findings, full re-review until no findings.
- ▌ Changes Review · duc01226 bundle[Code Quality] Use when reviewing current changes, staged or unstaged diffs, or branch-to-branch diffs.
- ▌ Changes Review 2 · duc01226 bundle[Code Quality] Use when reviewing current changes, staged or unstaged diffs, or branch-to-branch diffs.
- ▌ Artifact Review · duc01226 bundle[Code Quality] Use when you need to review artifact quality (PBI, user story, test spec, design spec) before handoff. Supports --type={pbi|story|spec-tests|design}.
- ▌ Artifact Review 2 · duc01226 bundle[Code Quality] Use when you need to review artifact quality (PBI, user story, test spec, design spec) before handoff. Supports --type={pbi|story|spec-tests|design}.
- ▌ Performance Review · duc01226 bundle[Debugging] Use when analyzing or optimizing performance bottlenecks: database queries, N+1 fan-out, indexing, API latency, memory/GC, concurrency and pool saturation, algorithmic complexity (O(n²)), network/protocol round trips, frontend rendering and Core Web Vitals, caching, and distributed/resilience paths. Calibration constants and domain laws (latency ladder, Little's Law, utilization knee, CWV thresholds, symptom→cause triage) live in references/performance-knowledge.md.
- ▌ Performance Review 2 · duc01226 bundle[Debugging] Use when analyzing or optimizing performance bottlenecks: database queries, N+1 fan-out, indexing, API latency, memory/GC, concurrency and pool saturation, algorithmic complexity (O(n²)), network/protocol round trips, frontend rendering and Core Web Vitals, caching, and distributed/resilience paths. Calibration constants and domain laws (latency ladder, Little's Law, utilization knee, CWV thresholds, symptom→cause triage) live in references/performance-knowledge.md.
- ▌ Architecture Design · duc01226 bundle[Architecture] Use when designing solution architecture across backend, frontend, data & consistency, integration & APIs, deployment, monitoring, testing, and code quality. Architecture laws, style-selection triggers, coupling taxonomy, trade-off tables and the anti-pattern catalog live in `.claude/docs/architecture-knowledge.md`.
- ▌ Architecture Review · duc01226 bundle[Code Quality] Use when reviewing architecture compliance for layers, messaging, service boundaries, CQRS, repos, entity events, and data/consistency/tenancy boundaries. Universal architecture laws, coupling taxonomy and the anti-pattern catalog live in `.claude/docs/architecture-knowledge.md` (project docs always outrank it).
- ▌ Architecture Design 2 · duc01226 bundle[Architecture] Use when designing solution architecture across backend, frontend, data & consistency, integration & APIs, deployment, monitoring, testing, and code quality. Architecture laws, style-selection triggers, coupling taxonomy, trade-off tables and the anti-pattern catalog live in `.claude/docs/architecture-knowledge.md`.
- ▌ Architecture Review 2 · duc01226 bundle[Code Quality] Use when reviewing architecture compliance for layers, messaging, service boundaries, CQRS, repos, entity events, and data/consistency/tenancy boundaries. Universal architecture laws, coupling taxonomy and the anti-pattern catalog live in `.claude/docs/architecture-knowledge.md` (project docs always outrank it).
- ▌ Domain Entities Review · duc01226 bundle[DDD Quality] Use when you need to review domain entities and value objects for DDD design quality.
- ▌ Domain Entities Review 2 · duc01226 bundle[DDD Quality] Use when you need to review domain entities and value objects for DDD design quality.
- ▌ Integration Test Review · duc01226 bundle[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code alignment.
- ▌ Integration Test Review 2 · duc01226 bundle[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code alignment.
- ▌ Production Readiness Review · duc01226 bundle[Code Quality] Use when reviewing service-layer and API changes for production readiness.
- ▌ Production Readiness Review 2 · duc01226 bundle[Code Quality] Use when reviewing service-layer and API changes for production readiness.
- ▌ Deep Research 2 · duc01226[Research] Use when deeply researching the top sources surfaced by web-research.
- ▌ Documentation 2 · duc01226[Code Quality] Use when enhancing documentation, adding code comments, creating API docs, or updating READMEs.
- ▌ Harness Setup 2 · duc01226[Quality] Use when setting up an agent quality harness with feedforward guides and feedback sensors.
- ▌ Pbi Challenge 2 · duc01226[Code Quality] Use when running an AI-assisted Dev BA PIC review of PBI drafts.
- ▌ Plan Analysis 2 · duc01226[Planning] Use when the user supplies a plan file and asks to analyze it, assess impact, or verify planned changes.
- ▌ Plan Validate 2 · duc01226[Planning] Use when validating a plan through a critical-questions interview.
- ▌ Product Owner 2 · duc01226[Project Management] Use when capturing ideas, managing backlogs, applying prioritization frameworks, or facilitating stakeholder communication.
- ▌ Release Notes 2 · duc01226 bundle[Git] Use when creating release notes or a release document from git history at any scope (tag-to-tag, branch-to-branch, time range), producing markdown plus a standalone HTML presentation.
- ▌ Skill Creator 2 · duc01226 bundle[Skill Management] Use when creating a skill, adding skill references or scripts, fixing invalid skill headers, or packaging skills.
- ▌ UI UX Pro Max 2 · duc01226 bundle[Frontend] Use when designing aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
- ▌ Claude Md Init 2 · duc01226 bundle[Documentation] Use when initializing, updating, or refactoring CLAUDE.md from project-config and codebase scans.
- ▌ Course Builder 2 · duc01226[Content] Use when building course material — Bloom objectives, modules, lessons, exercises, assessments.
- ▌ Project Config 2 · duc01226[Utilities] Use when scanning the workspace to update docs/project-config.json to match current structure.
- ▌ Prompt Enhance 2 · duc01226[Skill Management] Use when enhancing, compressing, or expanding prompts, docs, or skills. Flag: --op={compress|expand|enhance} (default enhance).
- ▌ Seed Test Data 2 · duc01226[Dev Data] Use when implementing or enhancing test-data seeders that simulate QC happy paths via application-layer commands. Flag: --mode=review audits a seeder read-only.
- ▌ Spec Discovery 2 · duc01226[Investigation] Use when about to author a new Feature Spec — surface related, overlapping, or affected specs, missing test cases, and the invariant landscape first.
- ▌ Start Workflow 2 · duc01226[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.
- ▌ Webapp Testing 2 · duc01226 bundle[Testing] Use when testing an individual page or component with Python Playwright scripts.
- ▌ Problem Solving 3 · duc01226 bundle[Utilities] Use when applying structured problem-solving frameworks to complex, blocked, recurring, or uncertain decisions.
- ▌ Code Simplifier 2 · duc01226[Code Quality] Use when simplifying code for clarity, consistency, and maintainability while preserving behavior.
- ▌ Domain Analysis 2 · duc01226[Architecture] Use when analyzing the business domain — bounded contexts, aggregates, entities, ERD, domain events, cross-context integration.
- ▌ Estimate Actual 2 · duc01226[Planning] Use when calibrating estimates against actual code, diff, PR scope, and developer time.
- ▌ Markdown To PDF 2 · duc01226 bundle[Document Processing] Use when converting Markdown to PDF with syntax highlighting and custom CSS.
- ▌ Market Analysis 2 · duc01226[Research] Use when analyzing the market landscape — competitors, TAM/SAM/SOM sizing, trends, SWOT, customer segments.
- ▌ Package Upgrade 2 · duc01226[Code Quality] Use when analyzing package upgrades, outdated dependencies, npm/NuGet update plans, or breaking changes.
- ▌ PDF To Markdown 2 · duc01226 bundle[Document Processing] Use when converting PDFs to Markdown, including scanned documents via OCR.
- ▌ Project Manager 2 · duc01226 bundle[Project Management] Use when generating project status reports, tracking dependencies, managing risk registers, or facilitating team syncs.
- ▌ Why Review Loop 2 · duc01226[Code Quality] Use when looping /why-review + /fix recursively over a target until a fresh full review clears the severity bar.
- ▌ Workflow Bugfix 2 · duc01226[Workflow] Use when fixing a bug, error, or crash — root-cause investigation, fix, verification.
- ▌ Business Analyst 2 · duc01226[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.
- ▌ DOCX To Markdown 2 · duc01226 bundle[Document Processing] Use when converting Word DOCX files to Markdown with GFM support.
- ▌ Markdown To DOCX 2 · duc01226 bundle[Document Processing] Use when converting Markdown to Word DOCX with GFM and math rendering.
- ▌ Strategy Builder 2 · duc01226[Content] Use when building a marketing strategy — positioning, channels, messaging, campaigns, budget, KPIs.
- ▌ Workflow Feature 2 · duc01226[Workflow] Use when implementing a well-defined feature, adding a component, or building a capability — including TDD and spec-driven test-first work.
- ▌ Branch Comparison 2 · duc01226[Git] Use when comparing branches, analyzing git diffs, or reviewing what changed between two refs.
- ▌ Debug Investigate 2 · duc01226[Fix & Debug] Use when finding a bug's root cause — reproduce, trace end-to-start, test hypotheses, pinpoint the defect before any fix.
- ▌
- ▌ Graph Connect API 2 · duc01226[Code Intelligence] Use when detecting frontend-to-backend API connections via the knowledge graph.
- ▌ Memory Management 2 · duc01226[Utilities] Use when saving or recovering task progress across sessions via file checkpoints, especially before compaction.
- ▌ Workflow Refactor 2 · duc01226[Workflow] Use when restructuring, reorganizing, or cleaning up code without changing behavior.
- ▌ Workflow Research 2 · duc01226[Workflow] Use when researching a topic from web sources then synthesizing. Flag: --output={synthesis|business-eval|marketing|course}.
- ▌ Excalidraw Diagram 2 · duc01226 bundle[Utilities] Use when visualizing workflows, architectures, or concepts as Excalidraw diagram JSON.
- ▌ Graph Blast Radius 2 · duc01226[Code Intelligence] Use when analyzing the blast radius of current code changes via the knowledge graph.
- ▌ Workflow Spec Sync 2 · duc01226[Workflow] Use when updating test specs and feature docs after code changes, bug fixes, or PR reviews.
- ▌ Workflow Visualize 2 · duc01226[Workflow] Use when creating Excalidraw diagrams from codebase investigation or web research.
- ▌ Business Evaluation 2 · duc01226[Content] Use when evaluating business idea viability — Business Model Canvas, financial projections, risk matrix, go-to-market, execution plan.
- ▌ Changes Review Loop 2 · duc01226[Code Quality] Use when looping /changes-review + /fix recursively over a fixed diff scope until one full pass clears the severity bar.
- ▌ Knowledge Synthesis 2 · duc01226[Research] Use when synthesizing research findings into a structured report.
- ▌ Quality Gate Review 2 · duc01226[Project Management] Use when enforcing quality gates, verifying standards compliance, tracking metrics, or generating audit trails.
- ▌ Sequential Thinking 2 · duc01226 bundle[AI & Tools] Use when applying structured, reflective problem-solving to complex multi-step analysis needing revision and hypothesis verification.
- ▌ Tech Stack Research 2 · duc01226[Architecture] Use when researching and comparing tech stack options as a solution architect.
- ▌ Context Optimization 2 · duc01226[Utilities] Use when managing context window usage, compressing long sessions, or optimizing tokens.
- ▌ Feature Presentation 2 · duc01226 bundle[Documentation] Use when synthesizing specs, PBIs, ideas, and mockups into one standalone HTML slide deck for stakeholders.
- ▌ Git Conflict Resolve 2 · duc01226[Git] Use when resolving git merge, cherry-pick, or rebase conflicts with backup and analysis.
- ▌ Scan Codebase Health 2 · duc01226[Documentation] Use when detecting codebase health issues — unused exports, doc count-drift, orphan files, stale config references.
- ▌ Workflow Big Feature 2 · duc01226[Workflow] Use when implementing a large, ambiguous, or research-driven feature.
- ▌ Workflow Idea To Pbi 2 · duc01226[Workflow] Use when turning an idea or product vision into prioritized PBIs and stories (single-PBI deep mode or multi-opportunity discovery).
- ▌ Workflow Spec To Pbi 2 · duc01226[Workflow] Use when converting canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.
- ▌ Markdown Novel Viewer 2 · duc01226 bundle[Content] Use when serving markdown files in a calm, book-like reading view over local HTTP.
- ▌ Web Design Guidelines 2 · duc01226 bundle[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.
- ▌ Workflow Code To Spec 2 · duc01226[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 Feature Spec 2 · duc01226[Workflow] Use when creating or updating 8-section tech-free business feature documentation.
- ▌ Workflow Idea To Spec 2 · duc01226[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.
- ▌ Project Skill Protocol 2 · duc01226 bundle[Utilities] Use when a project adds, changes, lists, or removes its OWN protocol rules layered over a framework skill. Overlays are ADDITIVE ONLY. Subcommands: list | add | update | delete.
- ▌ Integration Test Verify 2 · duc01226[Testing] Use when verifying integration tests pass after writing and reviewing them.
- ▌ Workflow Seed Test Data 2 · duc01226[Workflow] Use when seeding test data or implementing idempotent QC happy-path seeders.
- ▌ Workflow Greenfield Init 2 · duc01226[Workflow] Use when starting a new project from scratch — full waterfall inception from idea through implementation and integration testing.