devflow-kit 3.2.0 → 3.4.0

package/src/assets/skills/boundary-validation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: boundary-validation
-description: This skill should be used when the user asks to "validate input", "parse request data", "handle form data", "add Zod schema", "sanitize user input", or creates API endpoints and system boundaries. Provides parse-don't-validate patterns with schema validation for type-safe boundary enforcement and hostile input defense.
+description: This skill should be used when the user asks to "validate input", "parse request data", "add Zod schema", or creates API endpoints and system boundaries.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, AskUserQuestion
 ---

package/src/assets/skills/complexity/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: complexity
-description: This skill should be used when reviewing code for high cyclomatic complexity, deep nesting, or long functions.
+description: This skill should be used when reviewing code for deep nesting or long functions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/compliance/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: compliance
-description: This skill should be used when reviewing code handling PII, payment data, health records, audit logs, data retention, or IaC under GDPR, HIPAA, PCI DSS, SOC 2, ISO 27001, or SOX.
+description: This skill should be used when reviewing code that handles PII, payments or health data.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/consistency/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: consistency
-description: This skill should be used when reviewing code for naming convention violations, pattern deviations, or inconsistent API styles.
+description: This skill should be used when reviewing code for naming or pattern inconsistencies.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/database/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database
-description: This skill should be used when reviewing database queries, migrations, indexes, or schema changes.
+description: This skill should be used when reviewing queries, migrations or schema changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/dependencies/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dependencies
-description: This skill should be used when reviewing dependency changes, lock files, or package additions.
+description: This skill should be used when reviewing dependency or lock file changes.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/dependency-research/SKILL.md

@@ -1,9 +1,6 @@
 ---
 name: dependency-research
-description: >-
-  This skill should be used when the user asks to "add a utility", "create a helper",
-  "implement parsing", "build a wrapper", or writes infrastructure/utility code that
-  may already exist as a well-maintained package. Enforces research before building.
+description: This skill should be used when the user asks to "add a utility", "create a helper", "build a wrapper", or writes utility code a maintained package may already provide.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---
@@ -54,9 +51,9 @@ Nice-to-haves: {optional features}
 
 ### Phase 2: Search
 
-Delegate research to an Explore subagent to keep main session context clean.
+Spawn an Explore subagent when you can spawn agents, to keep main session context clean; otherwise search directly, using the template's questions as your checklist.
 
-**Spawn an Explore agent** with this prompt template:
+**Prompt template** for the Explore agent:
 
 ```
 Agent(subagent_type="Explore"):

package/src/assets/skills/design-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: design-review
-description: This skill should be used when reviewing implementation plans for anti-patterns, checking design quality before implementation, or performing plan-level quality assessment. Provides 6 anti-pattern detection rules for the Design agent and inline planning.
+description: This skill should be used when reviewing implementation plans for anti-patterns.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/docs-framework/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: docs-framework
-description: This skill should be used when the user asks to "create a review report", "write a status log", "add documentation", "name this artifact", or creates files in the .devflow/docs/ directory. Provides naming conventions, templates, and directory structure for reviews, debug sessions, design docs, and all persistent Devflow documentation artifacts.
+description: This skill should be used when creating files in the .devflow/docs/ directory.
 user-invocable: false
 allowed-tools: Read, Bash, Glob
 ---

package/src/assets/skills/documentation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation
-description: This skill should be used when reviewing for documentation drift, missing API docs, or stale comments.
+description: This skill should be used when reviewing for documentation drift or stale comments.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/feature-knowledge/SKILL.md

@@ -102,16 +102,20 @@ updated: {ISO date}
 
 # {Feature Area Name}
 
+## Rules
+- **KB-AP-1** [one-line anti-pattern or gotcha: what to avoid, and the consequence]
+- **KB-INV-1** [one-line invariant that must hold]
+
 ## Overview
 [1-2 paragraphs: what this knowledge covers and why it matters for this codebase]
 
 ## [Main Sections — vary by category, see Category Templates below]
 
 ## Anti-Patterns
-[What to avoid and why — with explanation of consequences]
+[The longer explanation of each anti-pattern, headed by its ID — never a restatement of the Rules bullet]
 
 ## Gotchas
-[Non-obvious behaviors, edge cases, things that break silently]
+[Non-obvious behaviors, edge cases, things that break silently — headed by the ID of the Rules bullet each explains]
 
 ## Key Files
 [Most important files with one-line descriptions]
@@ -120,6 +124,23 @@ updated: {ISO date}
 [Links to other feature knowledge entries and key source files — never an ADR/PF ID]
 ```
 
+### Rules Section
+
+`## Rules` comes first, after the title: the anti-patterns, gotchas and invariants of the feature area as one-line bullets, in about 3–5K characters. A bullet fits one line and never starts with `## `.
+
+- **IDs**: anti-pattern and gotcha bullets take `KB-AP-n`; invariant bullets take `KB-INV-n`. Numbers are unique within a KB. A bullet keeps its ID across rewrites; a removed bullet's ID is retired and never reused. A citation names the slug and the ID together, as `{slug} KB-AP-n`; a bare ID is never cited.
+- **Explanations**: `## Anti-Patterns` and `## Gotchas` stay below Rules as the longer explanations, each headed by the IDs it explains.
+- **No volatile numbers**: a volatile number is a count, size, line number, version or threshold that changes when the code changes. Where a value matters, name the test or constant that pins it. Bullet IDs are not volatile numbers.
+- **Legacy KBs**: a KB without `## Rules` is valid until curated. Readers take one to three entries from its Anti-Patterns or Gotchas, cited by section name, with the KB path and heading index.
+
+### Size Budget
+
+Per KB: target 30,000 characters, ceiling 40,000. An index line is at most 300 characters and a description at most 220, so slug, areas and description fit one line. **Curate, never truncate**: reword or consolidate, and nothing is cut or dropped to meet the budget. Split into focused sub-knowledge bases (each with its own index entry) only when curation cannot bring a KB under the ceiling.
+
+### Refreshing an Existing KB
+
+When `EXISTING_KB` is provided, change only the sections the new work touches, and add or update Rules bullets for what changed. Never renumber, and never rewrite untouched sections to meet the budget. A KB still above the ceiling after a refresh is written as it stands, and the final message says so.
+
 ### Category Templates
 
 Use the matching template as your main sections. Anti-Patterns, Gotchas, Key Files, and Related are shared across all categories.
@@ -159,6 +180,7 @@ The `description` field is how this feature knowledge entry gets discovered. It
 - Start with "Use when"
 - Name specific scenarios where this knowledge applies
 - Include keywords a developer would search for
+- Stay within 220 characters
 
 Good: `"Use when adding a new vendor integration, implementing API clients, or connecting to external services. Keywords: integration, vendor, API client, webhook."`
 Bad: `"Integration stuff"`
@@ -205,7 +227,7 @@ Never include bare code snippets without context.
 | No code examples at all | Insufficient actionable guidance |
 | Examples without inline comments | Missing required context |
 | "In the future, we might..." | Speculative — remove it |
-| 500+ lines in a single file | Should be split into focused files |
+| Over 40,000 characters, or volatile numbers in Rules | Curate it; name the pinning test or constant instead of a count |
 | No cross-references in Related | Isolated knowledge island |
 
 ---
@@ -228,7 +250,8 @@ Run through this before writing. If any check fails, go back and fix it.
 **Structure:**
 - [ ] Category is correct and main sections follow the matching template
 - [ ] Description field starts with "Use when" and includes keywords
-- [ ] File stays under 500 lines (split if necessary)
+- [ ] `## Rules` comes first: one-line bullets with `KB-AP-n` / `KB-INV-n` IDs, about 3–5K characters, no volatile numbers
+- [ ] File within the 40,000-character ceiling (curate, never truncate); description at most 220 characters
 
 **Connections:**
 - [ ] Cross-references to related feature knowledge entries in Related section; decisions and pitfalls stated in words, with no ADR/PF ID anywhere in the file
@@ -249,10 +272,10 @@ After writing KNOWLEDGE.md, update the index cache directly:
 - **{slug}** — {areas} — {Use-when description}
 ```
 
-Where:
+The whole line is at most 300 characters; reword a longer one, never cut it. Where:
 - `{slug}` matches the `feature:` frontmatter field
 - `{areas}` is a comma-separated summary of the `directories:` frontmatter field
-- `{Use-when description}` is the `description:` frontmatter field value (the full "Use when..." sentence)
+- `{Use-when description}` is the `description:` frontmatter field value (the full "Use when..." sentence, at most 220 characters)
 
 If `index.md` does not exist, create it with just this line. If the file already has an entry for this slug, replace that line in-place. This is the discoverable cache read by `knowledge_load()` — the KNOWLEDGE.md frontmatter is always authoritative.
 
@@ -275,9 +298,17 @@ updated: 2026-04-30
 
 # Third-Party Integrations
 
+## Rules
+
+- **KB-AP-1** Fetch logic never lives in a command file: it breaks the lib/command split and cannot be tested alone.
+- **KB-AP-2** URLs never live in lib modules: they go through `config.ts`.
+- **KB-AP-3** A lib module never calls `showError()`: lib modules throw, commands catch and display.
+- **KB-AP-4** `spawn` needs the binary on PATH: detect `ENOENT` and give an install URL.
+- **KB-INV-1** Every external constant lives in `src/lib/config.ts`.
+
 ## Overview
 
-This project integrates with external systems in three ways: spawning CLI processes, fetching files from remote registries, and writing to directories that AI editors watch. Each integration lives in its own module under `src/lib/` and is wired into a command in `src/commands/`. All external constants are centralized in `src/lib/config.ts`.
+This project integrates with external systems by spawning CLI processes, fetching files from remote registries, and writing to directories that AI editors watch. Each integration lives in its own module under `src/lib/` and is wired into a command in `src/commands/`. All external constants are centralized in `src/lib/config.ts`.
 
 The key cross-cutting pattern is the separation between lib modules (which integrate) and commands (which orchestrate). Violating this creates coupling that breaks the error handling model.
 
@@ -289,7 +320,7 @@ The key cross-cutting pattern is the separation between lib modules (which integ
 
 ## Standard Structure
 
-Every integration follows the same file organization. This example shows the pattern that all three existing integrations (Claude CLI, GitHub, AI editors) follow:
+Every integration follows the same file organization. This example shows the pattern that every existing integration (Claude CLI, GitHub, AI editors) follows:
 
 ```
 src/lib/
@@ -309,13 +340,13 @@ All constants use `SCREAMING_SNAKE_CASE` with a descriptive prefix. If a value c
 
 ## Anti-Patterns
 
-- **Putting fetch logic in a command file** — breaks the lib/command separation and makes the integration untestable in isolation.
-- **Hardcoding URLs in lib modules** — always use `config.ts`. Scattered strings become stale and hard to find.
-- **Calling `showError()` from a lib module** — lib modules throw; commands catch and display.
+- **KB-AP-1, putting fetch logic in a command file** — breaks the lib/command separation and makes the integration untestable in isolation.
+- **KB-AP-2, hardcoding URLs in lib modules** — always use `config.ts`. Scattered strings become stale and hard to find.
+- **KB-AP-3, calling `showError()` from a lib module** — lib modules throw; commands catch and display.
 
 ## Gotchas
 
-- `spawn` requires the binary on PATH. If integrating a tool that may not be globally installed, detect `ENOENT` and provide an install URL.
+- **KB-AP-4**: `spawn` requires the binary on PATH. If integrating a tool that may not be globally installed, detect `ENOENT` and provide an install URL.
 - Temp files use `Date.now()`. If two processes run simultaneously, add a random suffix to avoid collisions.
 
 ## Key Files

package/src/assets/skills/gap-analysis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: gap-analysis
-description: This skill should be used when analyzing design documents, specifications, or plans for completeness gaps, architectural issues, security concerns, and performance implications. Provides focus-specific detection patterns for the Design agent.
+description: This skill should be used when analyzing specs or plans for completeness gaps.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/git/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: git
-description: This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", "manage branches", "fix merge conflicts", "undo a commit", "comment on a PR", "create a release", or performs any git/GitHub operations. Provides safety patterns, atomic commit formatting, PR descriptions, sensitive file detection, and GitHub API usage.
+description: This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", or performs any git/GitHub operation.
 user-invocable: false
 allowed-tools: Bash, Read, Grep, Glob
 ---

package/src/assets/skills/go/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: go
-description: This skill should be used when the user works with Go files (.go), asks about "error handling", "interfaces", "goroutines", "channels", "packages", or discusses Go idioms and concurrency. Provides patterns for error handling, interface design, concurrency, and package organization.
+description: This skill should be used when the user works with Go files (.go), asks about "error handling", "interfaces", "goroutines", or discusses Go idioms and concurrency.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/java/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: java
-description: This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "Optional", "streams", "composition over inheritance", or discusses modern Java patterns and API design. Provides patterns for type system usage, error handling, immutability, and concurrency.
+description: This skill should be used when the user works with Java files (.java), asks about "records", "sealed classes", "streams", or discusses modern Java patterns.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: patterns
-description: This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", "add configuration", or builds features involving database operations, REST/GraphQL APIs, pub/sub patterns, or service configuration. Provides implementation patterns that follow existing codebase conventions.
+description: This skill should be used when the user asks to "create an API endpoint", "add CRUD operations", "implement event handlers", "set up logging", or adds database operations, REST/GraphQL APIs, pub/sub.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/performance/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance
-description: This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
+description: This skill should be used when reviewing code for N+1 queries or memory leaks.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/python/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: python
-description: This skill should be used when the user works with Python files (.py), asks about "type hints", "protocols", "dataclasses", "async/await", "decorators", or discusses Pythonic patterns and data modeling. Provides patterns for type safety, error handling, data modeling, and async programming.
+description: This skill should be used when the user works with Python files (.py), asks about "type hints", "protocols", "dataclasses", "async/await", or discusses Pythonic patterns.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/qa/SKILL.md

@@ -1,8 +1,6 @@
 ---
 name: qa
-description: This skill should be used when performing scenario-based acceptance testing,
-  designing QA test plans, or validating that implementation behavior matches acceptance
-  criteria beyond unit tests.
+description: This skill should be used when designing or running scenario-based acceptance tests.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Bash
 ---

package/src/assets/skills/quality-gates/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: quality-gates
-description: This skill should be used when evaluating implementation quality before submission, checking correctness, security, and simplicity.
+description: This skill should be used when evaluating implementation quality before submission.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Edit, Write, Bash
 ---
@@ -26,12 +26,12 @@ Based on [Google Engineering Practices](https://google.github.io/eng-practices/r
 |----------|--------|---------|
 | **P0** | MUST fix | Design, Functionality, Security |
 | **P1** | SHOULD fix | Complexity, Error Handling, Tests |
-| **P2** | FIX if time | Naming, Consistency, Documentation |
+| **P2** | FIX if straightforward | Documentation (Naming and Consistency belong to the Simplify agent: report them as SKIP) |
 
 ### P0 - Design
 Does the implementation fit the architecture? Follows existing patterns, respects layer boundaries, dependencies injected.
 
-If `FEATURE_KNOWLEDGE` is provided, verify implementation respects the feature area's documented architecture and anti-patterns. Flag deviations as P0-Design issues when the documented pattern is clearly intentional.
+If `FEATURE_KNOWLEDGE` is provided (Rules bullets and the KB path, no heading index), verify implementation respects each bullet's anti-pattern, gotcha or invariant; Read a KB section from its path for the architecture. Flag deviations as P0-Design issues when the documented pattern is clearly intentional.
 
 ### P0 - Functionality
 Does the code work? Happy path, edge cases (null, empty, boundary), no race conditions.
@@ -48,11 +48,8 @@ Errors handled explicitly? No swallowed exceptions, helpful messages, resources
 ### P1 - Tests
 New code tested? Covers happy path, errors, edges. Tests behavior, not implementation.
 
-### P2 - Naming
-Names clear and descriptive? No cryptic abbreviations, consistent style.
-
-### P2 - Consistency
-Matches existing patterns? Same style, same conventions, no unnecessary divergence.
+### P2 - Naming and Consistency
+Owned by the Simplify agent, which applies the project's naming and style standards. Report both as SKIP; do not judge or fix them here.
 
 ### P2 - Documentation
 Will others understand? Complex logic commented, public APIs documented, no outdated comments.
@@ -99,7 +96,7 @@ Check Design, Functionality, Security. If issues found and fixable, fix immediat
 Check Complexity, Error Handling, Tests. Fix issues found.
 
 ### Step 4: Evaluate P2 Pillars
-Check Naming, Consistency, Documentation. Fix if time permits.
+Check Documentation and fix it if straightforward. Naming and Consistency are the Simplify agent's: SKIP.
 
 ### Step 5: Generate Report
 Document status of each pillar, fixes applied, and overall readiness.
@@ -122,13 +119,13 @@ Document status of each pillar, fixes applied, and overall readiness.
 - Tests: PASS/FIXED
 
 ### P2 Pillars
-- Naming: PASS/FIXED/SKIP
-- Consistency: PASS/FIXED/SKIP
-- Documentation: PASS/FIXED/SKIP
+- Naming: SKIP (Simplify agent)
+- Consistency: SKIP (Simplify agent)
+- Documentation: PASS/FIXED
 
 ### Summary
 Issues Found: {n}, Fixed: {n}
-Status: READY / BLOCKED
+Status: PASS / FIXED / BLOCKED
 ```
 
 ---

package/src/assets/skills/quality-gates/references/report-template.md

@@ -44,13 +44,13 @@ Use this template when generating your self-review report.
 
 ---
 
-### P2 Pillars (FIX if Time Permits)
+### P2 Pillars (Documentation only)
 
 | Pillar | Status | Notes |
 |--------|--------|-------|
-| Naming | PASS/FIXED/SKIP | {details} |
-| Consistency | PASS/FIXED/SKIP | {details} |
-| Documentation | PASS/FIXED/SKIP | {details} |
+| Naming | SKIP | Simplify agent |
+| Consistency | SKIP | Simplify agent |
+| Documentation | PASS/FIXED | {details if fixed} |
 
 **Fixes Applied** (if any):
 - {file:line} - {what was fixed}
@@ -61,7 +61,7 @@ Use this template when generating your self-review report.
 
 **Issues Found**: {total count}
 **Issues Fixed**: {count}
-**Status**: READY / BLOCKED
+**Status**: PASS / FIXED / BLOCKED
 
 {If BLOCKED, explain what cannot be fixed and why}
 ```
@@ -105,12 +105,12 @@ Add user profile update endpoint
 
 ---
 
-### P2 Pillars (FIX if Time Permits)
+### P2 Pillars (Documentation only)
 
 | Pillar | Status | Notes |
 |--------|--------|-------|
-| Naming | PASS | Clear, descriptive names |
-| Consistency | PASS | Matches existing patterns |
+| Naming | SKIP | Simplify agent |
+| Consistency | SKIP | Simplify agent |
 | Documentation | PASS | JSDoc on public methods |
 
 ---
@@ -119,7 +119,7 @@ Add user profile update endpoint
 
 **Issues Found**: 0
 **Issues Fixed**: 0
-**Status**: READY
+**Status**: PASS
 ```
 
 ### Example 2: Issues Fixed
@@ -165,12 +165,12 @@ Implement order cancellation flow
 
 ---
 
-### P2 Pillars (FIX if Time Permits)
+### P2 Pillars (Documentation only)
 
 | Pillar | Status | Notes |
 |--------|--------|-------|
-| Naming | PASS | Clear names |
-| Consistency | PASS | Matches existing order methods |
+| Naming | SKIP | Simplify agent |
+| Consistency | SKIP | Simplify agent |
 | Documentation | FIXED | Added JSDoc explaining cancellation rules |
 
 **Fixes Applied**:
@@ -182,7 +182,7 @@ Implement order cancellation flow
 
 **Issues Found**: 5
 **Issues Fixed**: 5
-**Status**: READY
+**Status**: FIXED
 ```
 
 ### Example 3: Blocked
@@ -233,12 +233,12 @@ before implementing refund feature.
 
 ## Status Definitions
 
-| Status | Meaning |
-|--------|---------|
-| PASS | No issues found for this pillar |
-| FIXED | Issue found and resolved |
-| SKIP | P2 only - issue noted but not fixed due to time |
-| BLOCKED | Cannot fix - requires escalation |
+| Status | Pillar | Overall (`### Status`) |
+|--------|--------|------------------------|
+| PASS | No issues found for this pillar | No change was needed |
+| FIXED | Issue found and resolved | Fixes were committed and every P0 and P1 is fixed |
+| SKIP | Naming and Consistency only - owned by the Simplify agent | - |
+| BLOCKED | Cannot fix - requires escalation | A P0 cannot be fixed in scope |
 
 ---
 
@@ -247,7 +247,7 @@ before implementing refund feature.
 Before submitting report:
 - [ ] All P0 pillars are PASS or FIXED
 - [ ] All P1 pillars are PASS or FIXED
-- [ ] P2 pillars evaluated (PASS/FIXED/SKIP)
+- [ ] Documentation evaluated (PASS/FIXED); Naming and Consistency reported as SKIP
 - [ ] All fixes documented with file:line
 - [ ] Summary accurately reflects status
 - [ ] If BLOCKED, clear explanation provided

package/src/assets/skills/react/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: react
-description: This skill should be used when the user works with React components (.tsx/.jsx), asks about "hooks", "state management", "context providers", "memo optimization", "useEffect", or discusses component composition and rendering performance. Provides patterns for hooks, state, effects, memoization, and React-specific architecture.
+description: This skill should be used when the user works with React components (.tsx/.jsx), asks about "hooks", "state management", "memo optimization", or discusses component composition.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/regression/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: regression
-description: This skill should be used when reviewing changes that may remove exports, change signatures, or alter behavior.
+description: This skill should be used when reviewing changes that may break existing behavior.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/reliability/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: reliability
-description: This skill should be used when reviewing code for unbounded loops, missing assertions, excessive allocation, or deep indirection.
+description: This skill should be used when reviewing code for unbounded loops or missing assertions.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/research-codebase/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-codebase
-description: Local codebase research — find patterns, trace flows, map dependencies without browsing the web
+description: Local codebase research — find patterns, trace flows, map dependencies
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/research-competitor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-competitor
-description: Competitor analysis — structured feature comparison, positioning analysis, and gap identification
+description: Competitor analysis — feature comparison, positioning and gap identification
 user-invocable: false
 allowed-tools: WebSearch, WebFetch
 ---

package/src/assets/skills/research-external/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-external
-description: External web research — find documentation, articles, and community knowledge with untrusted-data discipline
+description: External web research — docs, articles, community knowledge; untrusted data
 user-invocable: false
 allowed-tools: WebSearch, WebFetch
 ---

package/src/assets/skills/research-technology/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: research-technology
-description: Technology evaluation — assess libraries, frameworks, and tools against project requirements
+description: Technology evaluation — assess libraries, frameworks and tools against requirements
 user-invocable: false
 allowed-tools: WebSearch, WebFetch, Read
 ---

package/src/assets/skills/review-methodology/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review-methodology
-description: This skill should be used when performing a code review to apply the standard 6-step review process.
+description: This skill should be used when performing a code review (the 6-step process).
 user-invocable: false
 allowed-tools: Read, Grep, Glob, Bash
 ---

package/src/assets/skills/rust/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rust
-description: This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "Result/Option", "traits", or discusses memory safety and type-driven design. Provides patterns for ownership, error handling, type system usage, and safe concurrency.
+description: This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "traits", or discusses memory safety.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 activation:

package/src/assets/skills/security/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security
-description: This skill should be used when reviewing code for injection flaws, auth bypasses, or hardcoded secrets.
+description: This skill should be used when reviewing code for injection, auth or secrets flaws.
 user-invocable: false
 allowed-tools: Read, Grep, Glob
 ---

package/src/assets/skills/software-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: software-design
-description: This skill should be used when the user asks to "handle errors", "inject dependencies", "return Result", "make it immutable", "compose with pipes", or implements business logic, error handling, or service composition. Provides Result type patterns, dependency injection, immutability by default, pipe composition, and structured logging for robust application architecture.
+description: This skill should be used when the user asks to "handle errors", "inject dependencies", "return Result", "make it immutable", or implements business logic or error handling.
 user-invocable: false
 allowed-tools: Read, Grep, Glob, AskUserQuestion
 ---