apt-mcp-agent-setup 2.0.1 → 3.0.0

package/src/templates/CLAUDE.md

@@ -1,254 +1,180 @@
-## Agent skills
-
-### Support & issues
-
-For bug reports, feature requests, or licensing questions, contact: `info.alphatechs.ai@gmail.com`
-
-### Issue tracker
-
-Issues are tracked in GitLab Issues. See `docs/agents/issue-tracker.md`.
-
-### Triage labels
-
-Default label vocabulary (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See `docs/agents/triage-labels.md`.
-
-### Domain docs
-
-Single-context layout — one `CONTEXT.md` + `docs/adr/` at the repo root. See `docs/agents/domain.md`.
-
-### FE Web design (taste-skill)
-
-Anti-slop frontend design skill for landing pages, portfolios, and redesigns.
-
-- `ui-style-rules` — anti-slop design rules, typography, color calibration, layout discipline for code generation.
-- `web-mockup-gen` — web design image/mockup generation (image-only, no code).
-
-### FE Mobile design
-
-- `mobile-mockup-gen` — mobile app screen mockup generation (image-only, no code).
-- `mobile-rules` — mobile-first design thinking (touch, performance, platform conventions).
-
-### Flutter development
-
-Skills for Flutter architecture, testing, layout, routing, localization, and serialization.
-
-Skills: `flutter-add-integration-test`, `flutter-add-widget-preview`, `flutter-add-widget-test`, `flutter-apply-architecture-best-practices`, `flutter-build-responsive-layout`, `flutter-fix-layout-issues`, `flutter-implement-json-serialization`, `flutter-setup-declarative-routing`, `flutter-setup-localization`, `flutter-use-http-package`.
-
-### MCP tools
-
-Tool selection rules, index policies, memory conventions, and auto-skill activation. See `docs/agents/mcp-tools.md`.
-
-**Quick reference:**
-- Code search: `code_search` (default), `grep_search` (non-code only)
-- Impact: `impact_analysis` (always update index first)
-- Memory: `remember` / `recall` / `read_knowledge` (see conventions in mcp-tools.md)
-
-## ⛔ CRITICAL: apt-mcp-agent TOOL USAGE (P0 — READ FIRST)
-
-**You have `apt-mcp-agent` MCP tools available. You MUST use them:**
-- **Before ANY code search**: use `explore_code` or `code_search` — NOT grep_search for code symbols
-- **Before executable changes**: call `pipeline_status`, then `pipeline_start` or `pipeline_use`
-- **After each pipeline step**: call `pipeline_checkpoint` with required `task` and `runId`
-- **Session start**: call `read_knowledge` + `pipeline_status`
-
-Ignoring these tools and using only built-in IDE tools is a **P0 protocol violation**.
-
-### 🛠️ ENFORCED DEVELOPER PIPELINES (MANDATORY — MCP TOOL GATE)
-
-Before writing any code or implementing features, you MUST follow one of the three enforced pipelines below.
-**Start or bind a run with `pipeline_start(pipeline, task, workspace)` or `pipeline_use(task, runId)`.**
-**After each step call `pipeline_checkpoint(task, runId, step, status="completed", summary)`.**
-
-Content-only documentation changes that do not affect executable behavior are exempt from PRD, issue, and TDD pipeline steps. Agent contracts such as `AGENTS.md`, `SKILL.md`, trigger maps, pipeline definitions, and runtime configuration are operational and are not exempt.
-Skipping steps or executing out-of-order is a **P0 protocol violation** — the tool will REJECT invalid transitions.
-
-#### 🚀 Feature Development Pipeline (5 steps — NO EXCEPTIONS, NO SKIP)
-```
-/grill-me → /to-prd → /to-issues → /tdd → /improve-codebase-architecture
-```
-1. **`/grill-me`** → Stress-test the plan/design with relentless Socratic questions. Challenge edge cases, security, performance.
-2. **`/to-prd`** → Synthesize the grill-me session and conversation context into a formal PRD document.
-3. **`/to-issues`** → Break PRD into vertical-slice issues on the issue tracker. Create `{task-slug}.md` for tracking.
-4. **`/tdd`** → Implement code test-first using RED-GREEN-REFACTOR cycle.
-5. **`/improve-codebase-architecture`** → Review and deepen architecture. Generate HTML report + grill-me session on codebase quality.
-
-#### 🐛 Bug Fix Pipeline (5 steps — NO EXCEPTIONS, NO SKIP)
-```
-/diagnose → /grill-me → /to-prd → /to-issues → /tdd
-```
-1. **`/diagnose`** → Build feedback loop: reproduce → minimize → hypothesize → fix.
-2. **`/grill-me`** → Challenge the fix design. Stress-test the proposed solution.
-3. **`/to-prd`** → Document the fix as a formal PRD with root cause analysis.
-4. **`/to-issues`** → Create tracking issues for the fix and any follow-up work.
-5. **`/tdd`** → Write regression tests first, then implement the fix.
-
-#### 🔧 Hotfix Pipeline (2 steps — for small, isolated changes ≤3 files)
-```
-/verify-scope → /fix-and-test
-```
-1. **`/verify-scope`** → Confirm change is small (≤3 files, no new API, no dependency changes). Provide scope justification in summary.
-2. **`/fix-and-test`** → Apply fix + write regression test if applicable.
-
-**When to use hotfix:** typos, config values, minor CSS, off-by-one errors, missing imports, small bug fixes with obvious root cause. If the change grows beyond scope, reset and escalate to `bugfix` or `feature` pipeline.
-
-**ENFORCEMENT PROTOCOL:**
-- After each step completion → call `pipeline_checkpoint(task, runId, step, "completed", summary)`
-- Before each step start → call `pipeline_status(task, runId)`
-- To cancel a run → call `pipeline_reset(task, runId, confirm=true)`; history is preserved
-- The MCP tool enforces ordering at runtime — out-of-order calls are **rejected with error**
-
----
-
-## Session Start Protocol (MANDATORY)
-
-At the start of every session:
-1. Read `.agents/ARCHITECTURE.md` to understand Agents, Skills, and Scripts.
-2. Read `.agents/memory/MEMORY.md` to load persistent project conventions, user preferences, and tech decisions.
-3. Read `docs/agents/mcp-tools.md` to load MCP tool selection rules & memory conventions.
-4. Call `read_knowledge` to load dynamic knowledge graph from memory.
-5. **Read `.agents/skill-triggers.json` to load auto-routing rules for all skills/workflows/tools.**
-
-### 🔄 Context Recovery (MANDATORY after any context truncation/compression)
-If your conversation context was truncated, compressed, or you are resuming after a checkpoint:
-1. **Call `pipeline_status()` immediately** — it returns recovery instructions and tool reminders
-2. Re-read the session start files above if not already in context
-3. Classify the current user request before taking any code action
-
-### ⚠️ MCP TOOL ACCESSIBILITY & FALLBACK WARNING (CRITICAL)
-If the specialized MCP tool `code_search` or other core MCP tools (e.g., `recall`, `remember`, `impact_analysis`) are not in your available tools list:
-- **DO NOT silently fall back to basic text search or skip debugging workflows.**
-- **STOP immediately, warn the user** that the `apt-mcp-agent` server did not start successfully or has been disabled in the IDE settings, and recommend they run `npx apt-mcp-agent-setup status` to check their setup.
-- Only proceed with fallback tools (e.g. `grep_search`) if the user explicitly approves it.
-
----
-
-## Auto-Trigger Skills (MANDATORY)
-
-### Workflow Skills — auto-trigger based on request type:
-
-| Skill | Trigger Conditions | Agent Action |
-|---|---|---|
-| `spec-clarification` | Design decision, architecture choice, plan review, "should we X or Y?" | Load SKILL.md → Start alignment session |
-| `bug-diagnostics` | Bug report, error log, "fails", "crashes", "/debug" | Load SKILL.md → Reproduce → minimise → hypothesise → fix |
-| `task-breakdown` | Plan/PRD just completed, "break down", "create tickets" | Load SKILL.md → Convert plan to vertical-slice issues |
-| `prd-gen` | New feature/product description with enough context for spec | Load SKILL.md → Extract PRD from conversation context |
-| `prototype` | "mockup", "explore options", unclear UI/logic | Load SKILL.md → Pick branch (logic vs UI) → Build throwaway prototype |
-| `tdd-loop` | Feature implementation, bug fix, "write tests", "red-green" | Load SKILL.md → Apply RED-GREEN-REFACTOR loop |
-
-### UI/UX Design Skills — auto-trigger when touching UI/design:
-
-| Skill | Trigger Conditions | Agent Action |
-|---|---|---|
-| `ui-style-rules` | Any web UI task: page layout, component styling, redesign | Load SKILL.md → Apply anti-slop design rules |
-| `web-mockup-gen` | "mockup web", "design page", web UI concept needed before coding | Load SKILL.md → Generate web design reference images (no code) |
-| `mobile-mockup-gen` | "mockup app", "design screen", mobile UI concept needed before coding | Load SKILL.md → Generate mobile screen mockups in phone frames |
-| `mobile-rules` | Any mobile UI implementation: Flutter widget, screen, touch interaction | Load SKILL.md → Apply platform conventions, touch patterns |
-| `stitch-design-flow` | "stitch", "tạo trên stitch", "/stitch-flow", design UI (khi stitch preset active) | Load SKILL.md → Collaborative 8-step Stitch design flow |
-| `figma-handoff` | Figma URL detected (`figma.com/...`), "figma", "/figma", "code theo Figma" (khi figma preset active) | Load SKILL.md → Extract design → generate code |
-| `design-to-code` | "code theo design", "pull code", "/design-to-code", design-to-code conversion | Load SKILL.md → Auto-detect input → route to correct design tool |
-| `flutter-fix-layout-issues` | "overflow", "unbounded height", `RenderFlex`, layout constraint error | Load SKILL.md → Fix overflow/constraint issues |
-| `flutter-build-responsive-layout` | "responsive", "tablet", "media query", adaptive layout | Load SKILL.md → Build adaptive layout |
-| `flutter-setup-declarative-routing` | "routing", "deep link", "go_router", URL navigation | Load SKILL.md → Configure declarative routing |
-| `flutter-add-widget-test` | "widget test", "test component", "verify UI rendering" | Load SKILL.md → Write widget test |
-| `flutter-add-integration-test` | "integration test", "e2e", "app test", "Flutter Driver" | Load SKILL.md → Add integration test |
-| `flutter-implement-json-serialization` | "fromJson", "toJson", "model class", "API response mapping" | Load SKILL.md → Create JSON serialization |
-| `flutter-setup-localization` | "localization", "i18n", "intl", "translation", ".arb" | Load SKILL.md → Setup l10n |
-| `flutter-apply-architecture-best-practices` | "architecture", "clean arch", "layer", project structure | Load SKILL.md → Apply layered architecture |
-| `flutter-add-widget-preview` | "preview", "widget catalog", "golden test" | Load SKILL.md → Add widget preview |
-| `flutter-use-http-package` | "http request", "REST API", "fetch data", "GET/POST" | Load SKILL.md → Use http package |
-
-### Productivity & Utility Skills — auto-trigger based on task context:
-
-| Skill | Trigger Conditions | Agent Action |
-|---|---|---|
-| `stress-test-plan` | "grill me", "challenge my plan", stress testing proposed plan | Load SKILL.md → Start interactive plan stress-testing session |
-| `skill-generator` | "write skill", "create skill", building a new custom agent skill | Load SKILL.md → Generate new skill stub/directory |
-| `git-safety-guardrails` | "git guardrails", "block dangerous git", protect git hooks | Load SKILL.md → Deploy Claude Code hooks to block push/hard-reset |
-| `git-hook-setup` | "setup pre-commit", "configure husky", install pre-commit hooks | Load SKILL.md → Install Husky, lint-staged, Prettier hooks |
-| `test-type-migration` | "migrate as in tests", "replace as assertions", shoehorn refactoring | Load SKILL.md → Refactor tests to remove unsafe type assertions |
-| `exercise-scaffold` | "scaffold exercises", "exercise stubs", coding course setup | Load SKILL.md → Create problems, solutions, and tests stubs |
-| `interactive-teaching` | "teach me", "tutorial", "learn Y", stateful workspace learning | Load SKILL.md → Create mission, lessons, and learning records |
-| `writing-flow` | "writing beats", "narrative journey", write article step-by-step | Load SKILL.md → Guide user through choice of narrative beats |
-| `raw-idea-collector` | "collect ideas", "writing fragments", ideate outline | Load SKILL.md → Collect heterogeneous claims, vignettes, and thoughts |
-| `draft-shaper` | "shape draft", "edit notes", clean draft to publishable quality | Load SKILL.md → Iterate paragraph by paragraph to edit draft |
-| `humanizer` | "humanize", "remove AI writing", "anti-slop", "viết tự nhiên hơn" | Load SKILL.md → Scrub 33 AI-writing patterns, rewrite to human voice |
-
-### BA/QC Skills — auto-trigger for requirements analysis and testing:
-
-| Skill | Trigger Conditions | Agent Action |
-|---|---|---|
-| `ba-urd-decomposer` | "URD", "phân rã URD", "danh sách tính năng", "feature list", .pdf file (BA context) | Load SKILL.md → Parse URD → output structured feature list |
-| `ba-clarification-session` | "làm rõ yêu cầu", "clarify", "hỏi PO", "session làm rõ", "clarification" | Load SKILL.md → Generate Q&A questions for PO session |
-| `ba-specs-writer` | "viết specs", "đặc tả", "chi tiết tính năng", "tạo specs", "PTTK" | Load SKILL.md → Generate detailed Specs document |
-| `ba-feature-tracker` | "tiến độ BA", "feature tracker", "trạng thái tính năng", "BA progress" | Load SKILL.md → Show BA progress dashboard |
-| `ba-template-parser` | "mẫu BA", "import template", "learn template", .docx file (BA context) | Load SKILL.md → Learn customer template structure |
-| `ba-requirements-generator` | "BRD", "user story", "viết yêu cầu", "sinh BRD", "tạo BRD" | Load SKILL.md → Generate BRD/User Story document |
-| `pdf-specs-parser` | "parse PDF specs", "đọc PTTK", .pdf file (specs context) | Load SKILL.md → Extract API/UI field definitions |
-| `qc-template-parser` | "mẫu QC", "import QC template", "mẫu testcase", .xlsx file (QC context) | Load SKILL.md → Learn Excel testcase template |
-| `qc-bidv-workflow` | "tạo testcase BIDV", "QC workflow", "sinh test case từ specs" | Load SKILL.md → Run BIDV QC pipeline end-to-end |
-| `testcase-generator` | "sinh test case", "generate TCs", "tạo testcase", "xuất Excel testcase" | Load SKILL.md → Generate Excel testcase from JSON |
-| `mindmap-reader` | "mindmap", "xmind", "đọc mindmap", .xmind/.mm file | Load SKILL.md → Parse mindmap → Normalized Test Scenario JSON |
-| `specs-to-mindmap` | "specs sang mindmap", "tạo outline từ specs", "test hierarchy" | Load SKILL.md → Convert Specs → Markdown outline |
-| `requirement-coverage` | "bao phủ yêu cầu", "traceability", "coverage report" | Load SKILL.md → Cross-reference user stories vs test cases |
-| `webapp-testing` | "E2E test", "Playwright", "test trình duyệt", "test tự động web" | Load SKILL.md → E2E/Playwright deep audit |
-
-**Failure Conditions:**
-- ❌ Writing UI code without loading design skill = **SLOP RISK**
-- ❌ Creating mobile screen without `mobile-rules` = **PLATFORM VIOLATION**
-
-### ⚠️ DOMAIN SKILL LOADING (CRITICAL — DO NOT SKIP)
-
-Before writing ANY UI, design, or visual code:
-1. **Web UI** → READ `.agents/skills/ui-style-rules/SKILL.md` — MANDATORY
-2. **Mobile UI** → READ `.agents/skills/mobile-rules/SKILL.md` — MANDATORY
-3. **Image/asset gen (web)** → READ `.agents/skills/web-mockup-gen/SKILL.md`
-4. **Image/asset gen (mobile)** → READ `.agents/skills/mobile-mockup-gen/SKILL.md`
-5. **Architecture decision** → READ `.agents/skills/stress-test-plan/SKILL.md`
-
-**Violation = SLOP output. Writing UI code without design skill = P0 violation.**
-
----
-
-## Socratic Gate
-
-Every user request must pass through the Socratic Gate before ANY implementation:
-
-| Request Type | Strategy | Required Action |
-|---|---|---|
-| **New Feature / Build** | Deep Discovery | ASK minimum 3 strategic questions |
-| **Code Edit / Bug Fix** | Context Check | Confirm understanding + ask impact questions |
-| **Vague / Simple** | Clarification | Ask Purpose, Users, and Scope |
-
-> [!IMPORTANT]
-> **STRICT SOCRATIC & WORKFLOW ENFORCEMENT:**
-> - **DO NOT write any code logic, execute modifications, or create plans before completing the required Socratic Gate action.** Bypassing the Socratic Gate is a P0 protocol violation.
-> - **DO NOT bypass specialized workflow skills** (like `bug-diagnostics` for debugging, `spec-clarification` for specifications, `tdd-loop` for writing code/tests) even if the task or error log seems simple or clear. Bypassing skills is a P0 protocol violation.
-
----
-
-## Universal Rules
-
-### Clean Code (Global Mandatory)
-- **Code**: Concise, direct, no over-engineering. Self-documenting.
-- **Laziness Ladder**: Before writing code, stop at the first rung that holds: YAGNI → Reuse existing → Stdlib → Native platform → Installed dep → One-liner → Minimum viable. The ladder runs AFTER understanding the problem.
-- **Bug Fix**: Root cause, not symptom. Grep every caller, fix the shared function once.
-- **No Bloat**: No unrequested abstractions, no scaffolding "for later", deletion > addition, fewest files.
-- **Testing**: Mandatory. Pyramid (Unit > Int > E2E) + AAA Pattern.
-- **Performance**: Measure first. Adhere to current Core Web Vitals standards.
-
-### Anti-Slop Writing (Global Mandatory)
-
-When generating **any prose content** (.md, .docx, PRDs, specs, articles, BA docs, commit messages, PR descriptions), automatically avoid AI-writing patterns:
-- **Ban list**: delve, tapestry, landscape (abstract), vibrant, crucial, foster, underscore, showcase, pivotal, testament, interplay, intricacies, garner, enhance, enduring
-- **No copula avoidance**: use "is/are/has" not "serves as/stands as/boasts/features"
-- **No em dashes**: replace with periods, commas, colons, or parentheses
-- **No signposting**: no "Let's dive in", "Here's what you need to know"
-- **No filler**: "In order to" → "To", "Due to the fact that" → "Because"
-- **No sycophancy**: no "Great question!", "Absolutely!", "I hope this helps!"
-- **Prefer**: plain verbs, specific details, varied sentence length, active voice
-
-Full 33-pattern reference: `.agents/skills/humanizer/references/patterns.md`
-
-### Quick Reference
-- **Masters**: `orchestrator`, `project-planner`, `security-auditor`, `backend-specialist`, `frontend-specialist`, `mobile-developer`, `debugger`
-- **Key Skills**: `clean-code`, `brainstorming`, `ui-style-rules`, `mobile-rules`, `web-mockup-gen`, `mobile-mockup-gen`, `stitch-design-flow`, `bug-diagnostics`, `tdd-loop`, `spec-clarification`, `prd-gen`, `task-breakdown`, `prototype`, `stress-test-plan`, `skill-generator`, `git-safety-guardrails`, `git-hook-setup`, `test-type-migration`, `exercise-scaffold`, `interactive-teaching`, `writing-flow`, `raw-idea-collector`, `draft-shaper`, `humanizer`, `project-config-wizard`, `skill-writing-guide`, `architecture-rules`, `solution-decision-map`, `task-implementation`, `git-conflict-resolver`, `workflow-navigator`, `terse-communication`, `session-handoff`
+## Agent skills
+
+### Support & issues
+
+For bug reports, feature requests, or licensing questions, contact: `info.alphatechs.ai@gmail.com`
+
+### Issue tracker
+
+Issues are tracked in GitLab Issues. See `docs/agents/issue-tracker.md`.
+
+### Triage labels
+
+Default label vocabulary (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See `docs/agents/triage-labels.md`.
+
+### Domain docs
+
+Single-context layout — one `CONTEXT.md` + `docs/adr/` at the repo root. See `docs/agents/domain.md`.
+
+### FE Web design (taste-skill)
+
+Anti-slop frontend design skill for landing pages, portfolios, and redesigns.
+
+- `ui-style-rules` — anti-slop design rules, typography, color calibration, layout discipline for code generation.
+- `web-mockup-gen` — web design image/mockup generation (image-only, no code).
+
+### FE Mobile design
+
+- `mobile-mockup-gen` — mobile app screen mockup generation (image-only, no code).
+- `mobile-rules` — mobile-first design thinking (touch, performance, platform conventions).
+
+### Flutter development
+
+Skills for Flutter architecture, testing, layout, routing, localization, and serialization.
+
+Skills: `flutter-add-integration-test`, `flutter-add-widget-preview`, `flutter-add-widget-test`, `flutter-apply-architecture-best-practices`, `flutter-build-responsive-layout`, `flutter-fix-layout-issues`, `flutter-implement-json-serialization`, `flutter-setup-declarative-routing`, `flutter-setup-localization`, `flutter-use-http-package`.
+
+### MCP tools
+
+Tool selection rules, index policies, memory conventions, and auto-skill activation. See `docs/agents/mcp-tools.md`.
+
+**Quick reference:**
+- Code search: `code_search` (default), `grep_search` (non-code only)
+- Impact: `impact_analysis` (always update index first)
+- Memory: `remember` / `recall` / `read_knowledge` (see conventions in mcp-tools.md)
+
+## APT session and execution contract
+
+1. Call `session_bootstrap` at session start and after context recovery. Read project conventions from `.agents/memory/MEMORY.md`; retrieve only relevant dynamic knowledge. Report unavailable backends once and use available fallbacks.
+2. Call `route_request` for a new request or changed intent, including target package/stack and explicit skills. Load the selected specialist and companion skills with `skill_load`. Do not read the complete trigger catalog into the model context.
+3. Read-only questions, reviews and running existing tests do not require a code-change pipeline. Before executable changes, inspect `pipeline_status` and bind `pipeline_start` or `pipeline_use` with canonical task/run identity and an explicit workspace.
+4. Small changes use scope, fix/check and review. Features use clarification only where needed, a plan with acceptance criteria, implementation, verification, review and acceptance. Bug fixes start with diagnosis and regression coverage. Do not require three questions, a PRD or external issues when the task is already clear.
+5. Use `pipeline_next` to reserve work before dispatch. Delegate useful independent research and reviews to native host subagents, with at most four active actors including the coordinator. Only one writer per workspace. Workers must not start/reset/rebind the parent pipeline.
+6. Record verification with `pipeline_verify` and report results with `pipeline_checkpoint`. Commands remain subject to host permissions and Plan Mode. Include current code and acceptance fingerprints; a free-form summary or skill-load receipt cannot prove completion.
+7. Review staged, unstaged and relevant untracked changes. Resolve in-scope findings, rerun affected checks and invalidate stale evidence. Review-only requests produce findings, not unsolicited edits or MR comments.
+8. Stop after ten repair/check attempts per work item or three repeated outcomes without progress. Preserve budgets and blocked/paused states across resume. User interruption always wins over continuation hooks.
+9. Native tool enforcement and automatic continuation depend on observed host capability. If unavailable, use sequential execution and state that limitation. Never claim independent review without an independent reviewer.
+10. Keep prose short and clear, reuse existing code, and load only current-step references. Strong caveman style is opt-in. Publishing, merging and external communication require authorization for those actions.
+
+`pipeline_reset(task, runId, confirm=true)` cancels a run while preserving history. Legacy runs retain their legacy definitions. Content-only documentation does not require PRD, issue or TDD steps; AGENTS.md, SKILL.md, trigger maps and runtime configuration are operational contracts.
+
+Read `docs/agents/mcp-tools.md` for interfaces. Run `npx apt-mcp-agent-setup doctor` to inspect configuration. A registered MCP server or installed hook is not proof of successful activation. Health must show successful initialization and functional probes, not only a running process.
+
+
+## Auto-Trigger Skills (MANDATORY)
+
+### Workflow Skills — auto-trigger based on request type:
+
+| Skill | Trigger Conditions | Agent Action |
+|---|---|---|
+| `spec-clarification` | Design decision, architecture choice, plan review, "should we X or Y?" | Load SKILL.md → Start alignment session |
+| `bug-diagnostics` | Bug report, error log, "fails", "crashes", "/debug" | Load SKILL.md → Reproduce → minimise → hypothesise → fix |
+| `task-breakdown` | Plan/PRD just completed, "break down", "create tickets" | Load SKILL.md → Convert plan to vertical-slice issues |
+| `prd-gen` | New feature/product description with enough context for spec | Load SKILL.md → Extract PRD from conversation context |
+| `prototype` | "mockup", "explore options", unclear UI/logic | Load SKILL.md → Pick branch (logic vs UI) → Build throwaway prototype |
+| `tdd-loop` | Feature implementation, bug fix, "write tests", "red-green" | Load SKILL.md → Apply RED-GREEN-REFACTOR loop |
+
+### UI/UX Design Skills — auto-trigger when touching UI/design:
+
+| Skill | Trigger Conditions | Agent Action |
+|---|---|---|
+| `ui-style-rules` | Any web UI task: page layout, component styling, redesign | Load SKILL.md → Apply anti-slop design rules |
+| `web-mockup-gen` | "mockup web", "design page", web UI concept needed before coding | Load SKILL.md → Generate web design reference images (no code) |
+| `mobile-mockup-gen` | "mockup app", "design screen", mobile UI concept needed before coding | Load SKILL.md → Generate mobile screen mockups in phone frames |
+| `mobile-rules` | Any mobile UI implementation: Flutter widget, screen, touch interaction | Load SKILL.md → Apply platform conventions, touch patterns |
+| `stitch-design-flow` | "stitch", "tạo trên stitch", "/stitch-flow", design UI (khi stitch preset active) | Load SKILL.md → Collaborative 8-step Stitch design flow |
+| `figma-handoff` | Figma URL detected (`figma.com/...`), "figma", "/figma", "code theo Figma" (khi figma preset active) | Load SKILL.md → Extract design → generate code |
+| `design-to-code` | "code theo design", "pull code", "/design-to-code", design-to-code conversion | Load SKILL.md → Auto-detect input → route to correct design tool |
+| `flutter-fix-layout-issues` | "overflow", "unbounded height", `RenderFlex`, layout constraint error | Load SKILL.md → Fix overflow/constraint issues |
+| `flutter-build-responsive-layout` | "responsive", "tablet", "media query", adaptive layout | Load SKILL.md → Build adaptive layout |
+| `flutter-setup-declarative-routing` | "routing", "deep link", "go_router", URL navigation | Load SKILL.md → Configure declarative routing |
+| `flutter-add-widget-test` | "widget test", "test component", "verify UI rendering" | Load SKILL.md → Write widget test |
+| `flutter-add-integration-test` | "integration test", "e2e", "app test", "Flutter Driver" | Load SKILL.md → Add integration test |
+| `flutter-implement-json-serialization` | "fromJson", "toJson", "model class", "API response mapping" | Load SKILL.md → Create JSON serialization |
+| `flutter-setup-localization` | "localization", "i18n", "intl", "translation", ".arb" | Load SKILL.md → Setup l10n |
+| `flutter-apply-architecture-best-practices` | "architecture", "clean arch", "layer", project structure | Load SKILL.md → Apply layered architecture |
+| `flutter-add-widget-preview` | "preview", "widget catalog", "golden test" | Load SKILL.md → Add widget preview |
+| `flutter-use-http-package` | "http request", "REST API", "fetch data", "GET/POST" | Load SKILL.md → Use http package |
+
+### Productivity & Utility Skills — auto-trigger based on task context:
+
+| Skill | Trigger Conditions | Agent Action |
+|---|---|---|
+| `stress-test-plan` | "grill me", "challenge my plan", stress testing proposed plan | Load SKILL.md → Start interactive plan stress-testing session |
+| `skill-generator` | "write skill", "create skill", building a new custom agent skill | Load SKILL.md → Generate new skill stub/directory |
+| `git-safety-guardrails` | "git guardrails", "block dangerous git", protect git hooks | Load SKILL.md → Deploy Claude Code hooks to block push/hard-reset |
+| `git-hook-setup` | "setup pre-commit", "configure husky", install pre-commit hooks | Load SKILL.md → Install Husky, lint-staged, Prettier hooks |
+| `test-type-migration` | "migrate as in tests", "replace as assertions", shoehorn refactoring | Load SKILL.md → Refactor tests to remove unsafe type assertions |
+| `exercise-scaffold` | "scaffold exercises", "exercise stubs", coding course setup | Load SKILL.md → Create problems, solutions, and tests stubs |
+| `interactive-teaching` | "teach me", "tutorial", "learn Y", stateful workspace learning | Load SKILL.md → Create mission, lessons, and learning records |
+| `writing-flow` | "writing beats", "narrative journey", write article step-by-step | Load SKILL.md → Guide user through choice of narrative beats |
+| `raw-idea-collector` | "collect ideas", "writing fragments", ideate outline | Load SKILL.md → Collect heterogeneous claims, vignettes, and thoughts |
+| `draft-shaper` | "shape draft", "edit notes", clean draft to publishable quality | Load SKILL.md → Iterate paragraph by paragraph to edit draft |
+| `humanizer` | "humanize", "remove AI writing", "anti-slop", "viết tự nhiên hơn" | Load SKILL.md → Scrub 33 AI-writing patterns, rewrite to human voice |
+
+### BA/QC Skills — auto-trigger for requirements analysis and testing:
+
+| Skill | Trigger Conditions | Agent Action |
+|---|---|---|
+| `ba-urd-decomposer` | "URD", "phân rã URD", "danh sách tính năng", "feature list", .pdf file (BA context) | Load SKILL.md → Parse URD → output structured feature list |
+| `ba-clarification-session` | "làm rõ yêu cầu", "clarify", "hỏi PO", "session làm rõ", "clarification" | Load SKILL.md → Generate Q&A questions for PO session |
+| `ba-specs-writer` | "viết specs", "đặc tả", "chi tiết tính năng", "tạo specs", "PTTK" | Load SKILL.md → Generate detailed Specs document |
+| `ba-feature-tracker` | "tiến độ BA", "feature tracker", "trạng thái tính năng", "BA progress" | Load SKILL.md → Show BA progress dashboard |
+| `ba-template-parser` | "mẫu BA", "import template", "learn template", .docx file (BA context) | Load SKILL.md → Learn customer template structure |
+| `ba-requirements-generator` | "BRD", "user story", "viết yêu cầu", "sinh BRD", "tạo BRD" | Load SKILL.md → Generate BRD/User Story document |
+| `pdf-specs-parser` | "parse PDF specs", "đọc PTTK", .pdf file (specs context) | Load SKILL.md → Extract API/UI field definitions |
+| `qc-template-parser` | "mẫu QC", "import QC template", "mẫu testcase", .xlsx file (QC context) | Load SKILL.md → Learn Excel testcase template |
+| `qc-bidv-workflow` | "tạo testcase BIDV", "QC workflow", "sinh test case từ specs" | Load SKILL.md → Run BIDV QC pipeline end-to-end |
+| `testcase-generator` | "sinh test case", "generate TCs", "tạo testcase", "xuất Excel testcase" | Load SKILL.md → Generate Excel testcase from JSON |
+| `mindmap-reader` | "mindmap", "xmind", "đọc mindmap", .xmind/.mm file | Load SKILL.md → Parse mindmap → Normalized Test Scenario JSON |
+| `specs-to-mindmap` | "specs sang mindmap", "tạo outline từ specs", "test hierarchy" | Load SKILL.md → Convert Specs → Markdown outline |
+| `requirement-coverage` | "bao phủ yêu cầu", "traceability", "coverage report" | Load SKILL.md → Cross-reference user stories vs test cases |
+| `webapp-testing` | "E2E test", "Playwright", "test trình duyệt", "test tự động web" | Load SKILL.md → E2E/Playwright deep audit |
+
+**Failure Conditions:**
+- ❌ Writing UI code without loading design skill = **SLOP RISK**
+- ❌ Creating mobile screen without `mobile-rules` = **PLATFORM VIOLATION**
+
+### ⚠️ DOMAIN SKILL LOADING (CRITICAL — DO NOT SKIP)
+
+Before writing ANY UI, design, or visual code:
+1. **Web UI** → READ `.agents/skills/ui-style-rules/SKILL.md` — MANDATORY
+2. **Mobile UI** → READ `.agents/skills/mobile-rules/SKILL.md` — MANDATORY
+3. **Image/asset gen (web)** → READ `.agents/skills/web-mockup-gen/SKILL.md`
+4. **Image/asset gen (mobile)** → READ `.agents/skills/mobile-mockup-gen/SKILL.md`
+5. **Architecture decision** → READ `.agents/skills/stress-test-plan/SKILL.md`
+
+**Violation = SLOP output. Writing UI code without design skill = P0 violation.**
+
+---
+
+## Clarification
+
+Ask only questions that resolve material uncertainty. Reuse established answers.
+
+## Universal Rules
+
+### Clean Code (Global Mandatory)
+- **Code**: Concise, direct, no over-engineering. Self-documenting.
+- **Laziness Ladder**: Before writing code, stop at the first rung that holds: YAGNI → Reuse existing → Stdlib → Native platform → Installed dep → One-liner → Minimum viable. The ladder runs AFTER understanding the problem.
+- **Bug Fix**: Root cause, not symptom. Grep every caller, fix the shared function once.
+- **No Bloat**: No unrequested abstractions, no scaffolding "for later", deletion > addition, fewest files.
+- **Testing**: Mandatory. Pyramid (Unit > Int > E2E) + AAA Pattern.
+- **Performance**: Measure first. Adhere to current Core Web Vitals standards.
+
+### Anti-Slop Writing (Global Mandatory)
+
+When generating **any prose content** (.md, .docx, PRDs, specs, articles, BA docs, commit messages, PR descriptions), automatically avoid AI-writing patterns:
+- **Ban list**: delve, tapestry, landscape (abstract), vibrant, crucial, foster, underscore, showcase, pivotal, testament, interplay, intricacies, garner, enhance, enduring
+- **No copula avoidance**: use "is/are/has" not "serves as/stands as/boasts/features"
+- **No em dashes**: replace with periods, commas, colons, or parentheses
+- **No signposting**: no "Let's dive in", "Here's what you need to know"
+- **No filler**: "In order to" → "To", "Due to the fact that" → "Because"
+- **No sycophancy**: no "Great question!", "Absolutely!", "I hope this helps!"
+- **Prefer**: plain verbs, specific details, varied sentence length, active voice
+
+Full 33-pattern reference: `.agents/skills/humanizer/references/patterns.md`
+
+### Quick Reference
+- **Masters**: `orchestrator`, `project-planner`, `security-auditor`, `backend-specialist`, `frontend-specialist`, `mobile-developer`, `debugger`
+- **Key Skills**: `clean-code`, `brainstorming`, `ui-style-rules`, `mobile-rules`, `web-mockup-gen`, `mobile-mockup-gen`, `stitch-design-flow`, `bug-diagnostics`, `tdd-loop`, `spec-clarification`, `prd-gen`, `task-breakdown`, `prototype`, `stress-test-plan`, `skill-generator`, `git-safety-guardrails`, `git-hook-setup`, `test-type-migration`, `exercise-scaffold`, `interactive-teaching`, `writing-flow`, `raw-idea-collector`, `draft-shaper`, `humanizer`, `project-config-wizard`, `skill-writing-guide`, `architecture-rules`, `solution-decision-map`, `task-implementation`, `git-conflict-resolver`, `workflow-navigator`, `terse-communication`, `session-handoff`