devflow-kit 1.1.0 → 1.3.0

package/plugins/devflow-ambient/commands/ambient.md

@@ -25,7 +25,7 @@ Read the `ambient-router` skill:
 Apply the ambient-router classification to `$ARGUMENTS`:
 
 1. **Intent:** BUILD | DEBUG | REVIEW | PLAN | EXPLORE | CHAT
-2. **Depth:** QUICK | STANDARD | ESCALATE
+2. **Depth:** QUICK | GUIDED | ELEVATE
 
 If no arguments provided, output:
 
@@ -37,10 +37,10 @@ Classify intent and auto-load relevant skills.
 Usage: /ambient <your prompt>
 
 Examples:
-  /ambient add a login form          → BUILD/STANDARD (loads TDD + implementation-patterns)
-  /ambient fix the auth error        → DEBUG/STANDARD (loads test-patterns + core-patterns)
+  /ambient add a login form          → BUILD/GUIDED (loads TDD + implementation-patterns)
+  /ambient fix the auth error        → DEBUG/GUIDED (loads test-patterns + core-patterns)
   /ambient where is the config?      → EXPLORE/QUICK (responds normally)
-  /ambient refactor the auth system  → BUILD/ESCALATE (suggests /implement)
+  /ambient refactor the auth system  → BUILD/ELEVATE (suggests /implement)
 
 Always-on: devflow ambient --enable
 ```
@@ -50,15 +50,15 @@ Then stop.
 ### Phase 3: State Classification
 
 - **QUICK:** Skip this phase entirely. Respond directly in Phase 4.
-- **STANDARD:** Output one line: `Ambient: {INTENT}/{DEPTH}. Loading: {skill1}, {skill2}.`
-- **ESCALATE:** Skip — recommendation happens in Phase 4.
+- **GUIDED:** Output one line: `Ambient: {INTENT}/{DEPTH}. Loading: {skill1}, {skill2}.`
+- **ELEVATE:** Skip — recommendation happens in Phase 4.
 
 ### Phase 4: Apply
 
 **QUICK:**
 Respond to the user's prompt normally. Zero skill loading. Zero overhead.
 
-**STANDARD:**
+**GUIDED:**
 Read the selected skills based on the ambient-router's skill selection matrix:
 
 | Intent | Primary Skills | Secondary (conditional) |
@@ -72,7 +72,7 @@ Read up to 3 skills from `~/.claude/skills/{name}/SKILL.md`. Apply their pattern
 
 For BUILD intent: enforce RED-GREEN-REFACTOR from test-driven-development. Write failing tests before production code.
 
-**ESCALATE:**
+**ELEVATE:**
 Respond to the user's prompt with your best effort, then append:
 
 > This task spans multiple files/systems. Consider `/implement` for full lifecycle management (exploration → planning → implementation → review).
@@ -84,11 +84,11 @@ Respond to the user's prompt with your best effort, then append:
 │
 ├─ Phase 1: Load ambient-router skill
 ├─ Phase 2: Classify intent + depth
-├─ Phase 3: State classification (STANDARD only)
+├─ Phase 3: State classification (GUIDED only)
 └─ Phase 4: Apply
    ├─ QUICK → respond directly
-   ├─ STANDARD → load 2-3 skills, apply patterns, respond
-   └─ ESCALATE → respond + workflow nudge
+   ├─ GUIDED → load 2-3 skills, apply patterns, respond
+   └─ ELEVATE → respond + workflow nudge
 ```
 
 ## Edge Cases
@@ -104,7 +104,7 @@ Respond to the user's prompt with your best effort, then append:
 ## Principles
 
 1. **No agents** — Ambient enhances the main session, never spawns subagents
-2. **Proportional** — QUICK gets zero overhead, STANDARD gets 2-3 skills, ESCALATE gets a nudge
-3. **Transparent** — State classification for STANDARD/ESCALATE, silent for QUICK
+2. **Proportional** — QUICK gets zero overhead, GUIDED gets 2-3 skills, ELEVATE gets a nudge
+3. **Transparent** — State classification for GUIDED/ELEVATE, silent for QUICK
 4. **Respectful** — Never over-classify; when in doubt, go one tier lower
-5. **TDD for BUILD** — STANDARD depth BUILD tasks enforce test-first workflow
+5. **TDD for BUILD** — GUIDED depth BUILD tasks enforce test-first workflow

package/plugins/devflow-ambient/skills/ambient-router/SKILL.md

@@ -36,7 +36,7 @@ Determine what the user is trying to do from their prompt.
 | **EXPLORE** | "what is", "where is", "find", "show me", "explain", "how does" | "where is the config?", "explain this function" |
 | **CHAT** | greetings, meta-questions, confirmations, short responses | "thanks", "yes", "what can you do?" |
 
-**Ambiguous prompts:** Default to the lowest-overhead classification. "Update the README" → BUILD/STANDARD. Git operations like "commit this" → QUICK.
+**Ambiguous prompts:** Default to the lowest-overhead classification. "Update the README" → BUILD/GUIDED. Git operations like "commit this" → QUICK.
 
 ## Step 2: Classify Depth
 
@@ -45,16 +45,16 @@ Determine how much enforcement the prompt warrants.
 | Depth | Criteria | Action |
 |-------|----------|--------|
 | **QUICK** | CHAT intent. EXPLORE with no analytical depth ("where is X?"). Git/devops operations (commit, push, merge, branch, pr, deploy, reinstall). Single-word continuations. | Respond normally. Zero overhead. Do not state classification. |
-| **STANDARD** | BUILD/DEBUG/REVIEW/PLAN intent (any word count). EXPLORE with analytical depth ("analyze our X", "discuss how Y works"). | Read and apply 2-3 relevant skills from the selection matrix below. State classification briefly. |
-| **ESCALATE** | Multi-file architectural change, system-wide scope, > 5 files. Detailed implementation plan (100+ words with plan structure). | Respond at best effort + recommend: "This looks like it would benefit from `/implement` for full lifecycle management." |
+| **GUIDED** | BUILD/DEBUG/REVIEW/PLAN intent (any word count). EXPLORE with analytical depth ("analyze our X", "discuss how Y works"). | Read and apply 2-3 relevant skills from the selection matrix below. State classification briefly. |
+| **ELEVATE** | Multi-file architectural change, system-wide scope, > 5 files. Detailed implementation plan (100+ words with plan structure). | Respond at best effort + recommend: "This looks like it would benefit from `/implement` for full lifecycle management." |
 
-## Step 3: Select Skills (STANDARD depth only)
+## Step 3: Select Skills (GUIDED depth only)
 
 Based on classified intent, read the following skills to inform your response.
 
 | Intent | Primary Skills | Secondary (if file type matches) |
 |--------|---------------|----------------------------------|
-| **BUILD** | test-driven-development, implementation-patterns | typescript (.ts), react (.tsx/.jsx), frontend-design (CSS/UI), input-validation (forms/API), security-patterns (auth/crypto) |
+| **BUILD** | test-driven-development, implementation-patterns | typescript (.ts), react (.tsx/.jsx), go (.go), java (.java), python (.py), rust (.rs), frontend-design (CSS/UI), input-validation (forms/API), security-patterns (auth/crypto) |
 | **DEBUG** | test-patterns, core-patterns | git-safety (if git operations involved) |
 | **REVIEW** | self-review, core-patterns | test-patterns |
 | **PLAN** | implementation-patterns | core-patterns |
@@ -65,19 +65,26 @@ See `references/skill-catalog.md` for the full skill-to-intent mapping with file
 
 ## Step 4: Apply
 
+<IMPORTANT>
+When classification is GUIDED or ELEVATE, skill application is NON-NEGOTIABLE.
+Do not rationalize skipping skills. Do not respond without loading them first.
+If test-driven-development is selected, you MUST write the failing test before ANY production code.
+</IMPORTANT>
+
 - **QUICK:** Respond directly. No preamble, no classification statement.
-- **STANDARD:** State classification briefly: `Ambient: BUILD/STANDARD. Loading: test-driven-development, implementation-patterns.` Then read the selected skills and apply their patterns to your response. For BUILD intent, enforce RED-GREEN-REFACTOR from test-driven-development.
-- **ESCALATE:** Respond with your best effort, then append: `> This task spans multiple files/systems. Consider \`/implement\` for full lifecycle (exploration → planning → implementation → review).`
+- **GUIDED:** State classification briefly: `Ambient: BUILD/GUIDED. Loading: test-driven-development, implementation-patterns.` Then read the selected skills and apply their patterns. No exceptions.
+- **ELEVATE:** Respond with your best effort, then append: `> This task spans multiple files/systems. Consider \`/implement\` for full lifecycle.`
 
 ---
 
 ## Transparency Rules
 
 1. **QUICK → silent.** No classification output.
-2. **STANDARD → brief statement.** One line: intent, depth, skills loaded.
-3. **ESCALATE → recommendation.** Best-effort response + workflow nudge.
+2. **GUIDED → brief statement + full skill enforcement.** One line: intent, depth, skills loaded. Then follow every skill requirement without shortcuts.
+3. **ELEVATE → recommendation.** Best-effort response + workflow nudge.
 4. **Never lie about classification.** If uncertain, say so.
 5. **Never over-classify.** When in doubt, go one tier lower.
+6. **Never under-apply.** Rationalization is the enemy of quality. If a skill requires a step, do the step.
 
 ## Edge Cases
 

package/plugins/devflow-ambient/skills/ambient-router/references/skill-catalog.md

@@ -4,7 +4,7 @@ Full mapping of DevFlow skills to ambient intents and file-type triggers. The am
 
 ## Skills Available for Ambient Loading
 
-These skills may be loaded during STANDARD-depth ambient routing.
+These skills may be loaded during GUIDED-depth ambient routing.
 
 ### BUILD Intent
 
@@ -16,6 +16,10 @@ These skills may be loaded during STANDARD-depth ambient routing.
 | react | React components in scope | `*.tsx`, `*.jsx` |
 | frontend-design | UI/styling work | `*.css`, `*.scss`, `*.tsx` with styling keywords |
 | input-validation | Forms, APIs, user input | Files with form/input/validation keywords |
+| go | Go files in scope | `*.go` |
+| java | Java files in scope | `*.java` |
+| python | Python files in scope | `*.py` |
+| rust | Rust files in scope | `*.rs` |
 | security-patterns | Auth, crypto, secrets | Files with auth/token/crypto/password keywords |
 
 ### DEBUG Intent
@@ -61,4 +65,4 @@ These skills are loaded only by explicit DevFlow commands (primarily `/code-revi
 - **Maximum 3 skills** per ambient response (primary + up to 2 secondary)
 - **Primary skills** are always loaded for the classified intent
 - **Secondary skills** are loaded only when file patterns match conversation context
-- If more than 3 skills seem relevant, this is an ESCALATE signal
+- If more than 3 skills seem relevant, this is an ELEVATE signal

package/plugins/devflow-audit-claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "devflow-audit-claude",
   "description": "Audit CLAUDE.md files against Anthropic best practices",
-  "version": "1.1.0",
+  "version": "1.3.0",
   "agents": [],
   "skills": []
 }

package/plugins/devflow-code-review/.claude-plugin/plugin.json

@@ -5,14 +5,23 @@
     "name": "DevFlow Contributors",
     "email": "dean@keren.dev"
   },
-  "version": "1.1.0",
+  "version": "1.3.0",
   "homepage": "https://github.com/dean0x/devflow",
   "repository": "https://github.com/dean0x/devflow",
   "license": "MIT",
-  "keywords": ["review", "code-quality", "security", "architecture", "pr-review"],
-  "agents": ["git", "reviewer", "synthesizer"],
+  "keywords": [
+    "review",
+    "code-quality",
+    "security",
+    "architecture",
+    "pr-review"
+  ],
+  "agents": [
+    "git",
+    "reviewer",
+    "synthesizer"
+  ],
   "skills": [
-    "accessibility",
     "agent-teams",
     "architecture-patterns",
     "complexity-patterns",
@@ -20,9 +29,7 @@
     "database-patterns",
     "dependencies-patterns",
     "documentation-patterns",
-    "frontend-design",
     "performance-patterns",
-    "react",
     "regression-patterns",
     "review-methodology",
     "security-patterns",

package/plugins/devflow-code-review/agents/reviewer.md

@@ -34,6 +34,10 @@ The orchestrator provides:
 | `react` | `~/.claude/skills/react/SKILL.md` |
 | `accessibility` | `~/.claude/skills/accessibility/SKILL.md` |
 | `frontend-design` | `~/.claude/skills/frontend-design/SKILL.md` |
+| `go` | `~/.claude/skills/go/SKILL.md` |
+| `java` | `~/.claude/skills/java/SKILL.md` |
+| `python` | `~/.claude/skills/python/SKILL.md` |
+| `rust` | `~/.claude/skills/rust/SKILL.md` |
 
 ## Responsibilities
 
@@ -117,3 +121,7 @@ Report format for `{output_path}`:
 | react | If .tsx/.jsx files changed |
 | accessibility | If .tsx/.jsx files changed |
 | frontend-design | If .tsx/.jsx/.css/.scss files changed |
+| go | If .go files changed |
+| java | If .java files changed |
+| python | If .py files changed |
+| rust | If .rs files changed |

package/plugins/devflow-code-review/commands/code-review-teams.md

@@ -42,10 +42,16 @@ Detect file types in diff to determine conditional reviews:
 | .tsx/.jsx files | react |
 | .tsx/.jsx files | accessibility |
 | .tsx/.jsx/.css/.scss files | frontend-design |
+| .go files | go |
+| .java files | java |
+| .py files | python |
+| .rs files | rust |
 | DB/migration files | database |
 | Dependency files changed | dependencies |
 | Docs or significant code | documentation |
 
+**Skill availability check**: Language/ecosystem reviews (typescript, react, accessibility, frontend-design, go, java, python, rust) require their optional skill plugin to be installed. Before adding a conditional perspective, check if `~/.claude/skills/{focus}/SKILL.md` exists (use Glob). If the skill file doesn't exist, **skip that perspective** — the language plugin isn't installed. Non-language reviews (database, dependencies, documentation) use skills bundled with this plugin and are always available.
+
 ### Phase 2: Spawn Review Team
 
 Create an agent team for adversarial review. Always include 4 core perspectives; conditionally add more based on Phase 1 analysis.
@@ -61,6 +67,10 @@ Create an agent team for adversarial review. Always include 4 core perspectives;
 - **React**: hooks, state, rendering, composition (if .tsx/.jsx changed)
 - **Accessibility**: ARIA, keyboard nav, focus management (if .tsx/.jsx changed)
 - **Frontend Design**: visual consistency, spacing, typography (if .tsx/.jsx/.css changed)
+- **Go**: error handling, interfaces, concurrency (if .go changed)
+- **Java**: records, sealed classes, composition (if .java changed)
+- **Python**: type hints, protocols, data modeling (if .py changed)
+- **Rust**: ownership, error handling, type system (if .rs changed)
 - **Database**: schema, queries, migrations, indexes (if DB files changed)
 - **Dependencies**: CVEs, versions, licenses, supply chain (if package files changed)
 - **Documentation**: doc drift, missing docs, stale comments (if docs or significant code changed)
@@ -238,7 +248,7 @@ Display results:
 │  ├─ Architecture Reviewer (teammate)
 │  ├─ Performance Reviewer (teammate)
 │  ├─ Quality Reviewer (teammate)
-│  └─ [Conditional: TypeScript, React, A11y, Design, DB, Deps, Docs]
+│  └─ [Conditional: TypeScript, React, A11y, Design, Go, Java, Python, Rust, DB, Deps, Docs]
 │
 ├─ Phase 3: Debate round
 │  └─ Reviewers challenge each other (max 2 rounds)

package/plugins/devflow-code-review/commands/code-review.md

@@ -42,13 +42,19 @@ Detect file types in diff to determine conditional reviews:
 | .tsx/.jsx files | react |
 | .tsx/.jsx files | accessibility |
 | .tsx/.jsx/.css/.scss files | frontend-design |
+| .go files | go |
+| .java files | java |
+| .py files | python |
+| .rs files | rust |
 | DB/migration files | database |
 | Dependency files changed | dependencies |
 | Docs or significant code | documentation |
 
+**Skill availability check**: Language/ecosystem reviews (typescript, react, accessibility, frontend-design, go, java, python, rust) require their optional skill plugin to be installed. Before spawning a conditional Reviewer for these focuses, check if `~/.claude/skills/{focus}/SKILL.md` exists (use Glob). If the skill file doesn't exist, **skip that review** — the language plugin isn't installed. Non-language reviews (database, dependencies, documentation) use skills bundled with this plugin and are always available.
+
 ### Phase 2: Run Reviews (Parallel)
 
-Spawn Reviewer agents **in a single message**. Always run 7 core reviews; conditionally add up to 4 more:
+Spawn Reviewer agents **in a single message**. Always run 7 core reviews; conditionally add more based on changed file types:
 
 | Focus | Always | Pattern Skill |
 |-------|--------|---------------|
@@ -63,6 +69,10 @@ Spawn Reviewer agents **in a single message**. Always run 7 core reviews; condit
 | react | conditional | react |
 | accessibility | conditional | accessibility |
 | frontend-design | conditional | frontend-design |
+| go | conditional | go |
+| java | conditional | java |
+| python | conditional | python |
+| rust | conditional | rust |
 | database | conditional | database-patterns |
 | dependencies | conditional | dependencies-patterns |
 | documentation | conditional | documentation-patterns |
@@ -123,7 +133,7 @@ Display results from all agents:
 │  ├─ Reviewer: consistency
 │  ├─ Reviewer: regression
 │  ├─ Reviewer: tests
-│  └─ Reviewer: [conditional: typescript, react, a11y, design, database, deps, docs]
+│  └─ Reviewer: [conditional: typescript, react, a11y, design, go, java, python, rust, database, deps, docs]
 │
 ├─ Phase 3: Synthesis (PARALLEL)
 │  ├─ Git agent (comment-pr)

package/plugins/devflow-code-review/skills/architecture-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: architecture-patterns
-description: Architecture analysis patterns for code review. Detects SOLID violations, tight coupling, layering issues, and dependency direction problems. Loaded by Reviewer agent when focus=architecture.
+description: This skill should be used when reviewing code for SOLID violations, tight coupling, or layering issues.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/complexity-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: complexity-patterns
-description: Complexity analysis patterns for code review. Detects high cyclomatic complexity, deep nesting, long functions, and readability issues that hinder maintainability. Loaded by Reviewer agent when focus=complexity.
+description: This skill should be used when reviewing code for high cyclomatic complexity, deep nesting, or long functions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/consistency-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: consistency-patterns
-description: Consistency analysis patterns for code review. Detects naming convention violations, pattern deviations, unnecessary simplification, and feature truncation in diffs. Loaded by Reviewer agent when focus=consistency.
+description: This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/database-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-patterns
-description: Database analysis patterns for code review. Detects missing indexes, slow queries, unsafe migrations, schema design issues, and connection pool misuse. Loaded by Reviewer agent when focus=database.
+description: This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/dependencies-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dependencies-patterns
-description: Dependency analysis patterns for code review. Detects known CVEs, outdated packages, license incompatibilities, and unnecessary transitive dependencies. Loaded by Reviewer agent when focus=dependencies.
+description: This skill should be used when reviewing dependency changes, lock files, or package additions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/documentation-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-patterns
-description: Documentation analysis patterns for code review. Detects doc drift from code changes, missing documentation for public APIs, stale comments, and misleading README sections. Loaded by Reviewer agent when focus=documentation.
+description: This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/performance-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance-patterns
-description: Performance analysis patterns for code review. Detects N+1 queries, memory leaks, unbounded allocations, I/O bottlenecks, and missing caching opportunities. Loaded by Reviewer agent when focus=performance.
+description: This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/regression-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: regression-patterns
-description: Regression analysis patterns for code review. Detects lost functionality, removed exports, changed signatures, and behavioral changes that break existing consumers. Loaded by Reviewer agent when focus=regression.
+description: This skill should be used when reviewing changes that may remove exports, change signatures, or alter behavior.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-code-review/skills/review-methodology/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review-methodology
-description: Standard review methodology providing the 6-step process and 3-category issue classification (must-fix, should-fix, nit) used by all DevFlow review agents. Ensures consistent, fair, and actionable code reviews across all focus areas. Loaded by the unified Reviewer agent.
+description: This skill should be used when performing a code review to apply the standard 6-step review process.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Bash
 ---

package/plugins/devflow-code-review/skills/security-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security-patterns
-description: Security vulnerability analysis patterns for code review. Detects injection flaws, authentication bypasses, insecure cryptography, hardcoded secrets, and missing input sanitization. Loaded by Reviewer agent when focus=security.
+description: This skill should be used when reviewing code for injection flaws, auth bypasses, or hardcoded secrets.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/plugins/devflow-core-skills/.claude-plugin/plugin.json

@@ -5,24 +5,27 @@
     "name": "DevFlow Contributors",
     "email": "dean@keren.dev"
   },
-  "version": "1.1.0",
+  "version": "1.3.0",
   "homepage": "https://github.com/dean0x/devflow",
   "repository": "https://github.com/dean0x/devflow",
   "license": "MIT",
-  "keywords": ["skills", "quality", "patterns", "auto-activate", "enforcement", "foundation"],
+  "keywords": [
+    "skills",
+    "quality",
+    "patterns",
+    "auto-activate",
+    "enforcement",
+    "foundation"
+  ],
   "agents": [],
   "skills": [
-    "accessibility",
     "core-patterns",
     "docs-framework",
-    "frontend-design",
     "git-safety",
     "git-workflow",
     "github-patterns",
     "input-validation",
-    "react",
     "test-driven-development",
-    "test-patterns",
-    "typescript"
+    "test-patterns"
   ]
 }

package/plugins/devflow-core-skills/skills/test-driven-development/SKILL.md

@@ -1,9 +1,6 @@
 ---
 name: test-driven-development
-description: >-
-  Enforce RED-GREEN-REFACTOR cycle during implementation. Write failing tests before
-  production code. Distinct from test-patterns (which reviews test quality) — this
-  skill enforces the TDD workflow during code generation.
+description: This skill should be used when implementing new features, fixing bugs, or writing new code. Enforces RED-GREEN-REFACTOR.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:
@@ -94,7 +91,7 @@ See `references/rationalization-prevention.md` for extended examples with code.
 
 ## Process Enforcement
 
-When implementing any feature under ambient BUILD/STANDARD:
+When implementing any feature under ambient BUILD/GUIDED:
 
 1. **Identify the first behavior** — What is the simplest thing this feature must do?
 2. **Write the test** — Describe that behavior as a failing test
@@ -133,7 +130,7 @@ When skipping TDD, never rationalize. State clearly: "Skipping TDD because: [spe
 
 ## Integration with Ambient Mode
 
-- **BUILD/STANDARD** → TDD enforced. Every new function/method gets test-first treatment.
+- **BUILD/GUIDED** → TDD enforced. Every new function/method gets test-first treatment.
 - **BUILD/QUICK** → TDD skipped (trivial single-file edit).
-- **BUILD/ESCALATE** → TDD mentioned in nudge toward `/implement`.
-- **DEBUG/STANDARD** → TDD applies to the fix: write a test that reproduces the bug first, then fix.
+- **BUILD/ELEVATE** → TDD mentioned in nudge toward `/implement`.
+- **DEBUG/GUIDED** → TDD applies to the fix: write a test that reproduces the bug first, then fix.

package/plugins/devflow-debug/.claude-plugin/plugin.json

@@ -5,12 +5,19 @@
     "name": "DevFlow Contributors",
     "email": "dean@keren.dev"
   },
-  "version": "1.1.0",
+  "version": "1.3.0",
   "homepage": "https://github.com/dean0x/devflow",
   "repository": "https://github.com/dean0x/devflow",
   "license": "MIT",
-  "keywords": ["debugging", "hypotheses", "investigation", "agent-teams"],
-  "agents": ["git"],
+  "keywords": [
+    "debugging",
+    "hypotheses",
+    "investigation",
+    "agent-teams"
+  ],
+  "agents": [
+    "git"
+  ],
   "skills": [
     "agent-teams",
     "git-safety"

package/plugins/devflow-frontend-design/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "devflow-frontend-design",
+  "description": "Frontend design patterns - typography, color systems, spacing, motion, responsive design",
+  "author": {
+    "name": "DevFlow Contributors",
+    "email": "dean@keren.dev"
+  },
+  "version": "1.3.0",
+  "homepage": "https://github.com/dean0x/devflow",
+  "repository": "https://github.com/dean0x/devflow",
+  "license": "MIT",
+  "keywords": [
+    "design",
+    "typography",
+    "color",
+    "css"
+  ],
+  "agents": [],
+  "skills": [
+    "frontend-design"
+  ]
+}

package/plugins/devflow-go/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "devflow-go",
+  "description": "Go language patterns - error handling, interfaces, concurrency, package design",
+  "author": {
+    "name": "DevFlow Contributors",
+    "email": "dean@keren.dev"
+  },
+  "version": "1.3.0",
+  "homepage": "https://github.com/dean0x/devflow",
+  "repository": "https://github.com/dean0x/devflow",
+  "license": "MIT",
+  "keywords": [
+    "go",
+    "golang",
+    "concurrency",
+    "errors"
+  ],
+  "agents": [],
+  "skills": [
+    "go"
+  ]
+}