@softspark/ai-toolkit 2.8.0 → 2.10.0

package/AGENTS.md

@@ -358,7 +358,7 @@ Search engine optimization specialist. Trigger words: SEO, search engine, meta t
 
 The Guardian of the Constitution. Validates all evolutionary changes and enforces immutable rules. Has VETO power.
 
-**Tools:** `Read, Write, Bash`
+**Tools:** `Read, Write, Bash, Grep, Glob`
 
 ---
 
@@ -449,68 +449,68 @@ Skills are invocable commands or auto-loaded knowledge sources:
 - **a11y-validate**: Validate code against accessibility standards: WCAG 2.1 Level AA, EN 301 549, and the European Accessibility Act (EAA / Directive EU 2019/882). Covers semantics, text alternatives, keyboard/focus, color/contrast, forms, media, ARIA, motion, mobile, and EAA documentation requirements. Framework-aware (React/Next/Nuxt/Astro/Gatsby/SvelteKit/Remix/Angular/Vue/React Native/Flutter/static HTML).
 - **agent-creator**: Creates new specialized agents with frontmatter, tool selection, and delegation guidance
 - **analyze**: Analyze code quality, complexity, and patterns
-- **api-patterns**: Loaded when user asks about REST API design or GraphQL patterns
-- **app-builder**: Loaded when user asks to scaffold or build a full-stack app
+- **api-patterns**: REST and GraphQL API design patterns: resource naming, versioning, pagination, error contracts, idempotency, HATEOAS, OpenAPI. Triggers: API design, REST, GraphQL, endpoint, route, OpenAPI, Swagger, pagination, rate limit, versioning, idempotency key. Load when designing or reviewing any HTTP API surface.
+- **app-builder**: Full-stack app scaffolding with stack-selection matrix: Next.js, React+Vite, Nuxt, Astro, FastAPI, Django, Laravel, React Native, Flutter, Unity. Triggers: scaffold, bootstrap, new project, starter template, build app, landing page, dashboard, API, mobile app, CLI, e-commerce, game. Load when user wants to start a new project from scratch.
 - **architecture-audit**: Explore codebase organically for architectural friction, discover shallow modules, and propose module-deepening refactors as GitHub issue RFCs using parallel sub-agent interface designs. Use when user wants to improve architecture, find shallow modules, deepen modules, or reduce coupling. Codex-adapted: uses native subagents and plan tracking.
-- **architecture-decision**: Loaded when user asks about architecture decisions or architecture note writing
+- **architecture-decision**: Architecture decision making via trade-off analysis in RFC/RFD/ADR format: context, constraints, 3+ options, comparison, recommendation. Triggers: architecture decision, ADR, RFC, RFD, trade-offs, options comparison, design choice, pick between, should we use, evaluate approach. Load when weighing 2+ architectural options or writing decision records.
 - **biz-scan**: Scan codebase for business opportunities and KPIs
 - **brand-voice**: Loaded when writing documentation, content, README, or user-facing text. Prevents generic LLM rhetoric and enforces direct, technical voice.
 - **briefing**: Generate executive daily briefing across all agents
 - **build**: Build the project with auto-detected toolchain
 - **chaos**: Inject controlled faults for resilience testing
 - **ci**: Detect and run CI pipeline with status reporting
-- **ci-cd-patterns**: Loaded when user asks about CI/CD pipelines or deployment automation
-- **clean-code**: Loaded when user asks about clean code, naming, or code quality
+- **ci-cd-patterns**: CI/CD pipeline and deployment automation: GitHub Actions, GitLab CI, Jenkins, build stages, caching, artifact promotion, blue-green, canary, rollback gates. Triggers: CI, CD, pipeline, GitHub Actions, workflow YAML, deploy automation, release, artifact, rollout, canary, blue-green. Load when designing or fixing a build/release pipeline.
+- **clean-code**: Code quality principles: meaningful names, single responsibility, DRY, small functions, clear intent, guard clauses, refactoring rules. Triggers: clean code, naming, refactor for clarity, code smell, SRP, DRY, long function, god class, magic number, dead code. Load when reviewing or writing any production code.
 - **command-creator**: Creates new Claude Code slash commands with frontmatter, workflow guidance, and validation
 - **commit**: Create Conventional Commits with pre-commit validation
 - **content-moderation-patterns**: Loaded when user builds content moderation, safety filters, or policy enforcement with Claude. Covers pre-filter vs LLM-classify, category design, confidence thresholds, and human-in-the-loop.
 - **council**: 4-perspective decision evaluation for architecture choices. Use when user wants multi-angle analysis, needs to decide between alternatives, or mentions 'council', 'evaluate decision', 'pros cons'. Codex-adapted: uses native subagents and plan tracking.
-- **csharp-patterns**: Loaded when user asks about C# or .NET development patterns
+- **csharp-patterns**: C# and .NET development patterns: LINQ, async/await, dependency injection, records, nullable reference types, ASP.NET Core minimal APIs, EF Core, MediatR. Triggers: C#, .NET, dotnet, ASP.NET, EF Core, LINQ, IServiceCollection, record type, async C#, nullable reference types. Load when writing or reviewing C#/.NET code.
 - **cve-scan**: Scan project dependencies for known CVEs using native audit tools (npm, pip, composer, cargo, go, bundler, dart)
-- **database-patterns**: Loaded when user asks about database schema or query optimization
+- **database-patterns**: Database schema design and query optimization: normalization, indexing strategies, joins, N+1, transactions, isolation levels, partitioning, EXPLAIN plans. Triggers: schema, table design, index, slow query, N+1, PostgreSQL, MySQL, SQL Server, SQL, EXPLAIN, query plan, transaction, deadlock. Load when designing tables or tuning queries.
 - **debug**: Debug errors and trace root causes systematically
-- **debugging-tactics**: Loaded when user is debugging an issue or needs root cause analysis
+- **debugging-tactics**: Root-cause debugging with 4-phase method: investigation, hypothesis, validation, fix. No fix without RCA. Triggers: bug, error, exception, stack trace, not working, intermittent, flaky, crash, regression, fails sometimes, why is X happening, broken after. Load when user reports a bug or asks to investigate failing code.
 - **deploy**: Deploy with pre-flight checks and health verification
 - **design-an-interface**: Generate multiple radically different interface designs using parallel sub-agents, then compare on simplicity, depth, and correctness. Based on 'Design It Twice' from Ousterhout. Use when user wants to design an API, explore interface options, compare module shapes, or mentions 'design it twice'. Codex-adapted: uses native subagents and plan tracking.
-- **design-engineering**: Loaded when user asks about UI animations or CSS design craft
-- **docker-devops**: Loaded when user asks about Docker, containers, or DevOps patterns
+- **design-engineering**: UI craftsmanship (Emil Kowalski school): animation frequency rules, easing curves, micro-interactions, state polish, invisible-details philosophy. Triggers: animation, transition, ease-out, ease-in-out, motion, micro-interaction, hover state, loading state, UI polish, design detail, spring curve, delightful UX. Load when building or reviewing interactive UI.
+- **docker-devops**: Docker, containers, Kubernetes, and DevOps patterns: Dockerfile best practices, multi-stage builds, compose, k8s manifests, Helm charts, service mesh, image hardening. Triggers: Docker, Dockerfile, container, image, Kubernetes, k8s, compose, Helm, registry, layer caching, service mesh, pod, deployment yaml. Load when writing or fixing container/orchestration configs.
 - **docs**: Generate and update README, API docs, and architecture notes
-- **documentation-standards**: Loaded when creating or updating KB documents, architecture notes, SOPs, or any file in kb/ directory
-- **ecommerce-patterns**: Loaded when user asks about e-commerce or shopping cart features
+- **documentation-standards**: KB document conventions: YAML frontmatter (7 required fields), 5-category taxonomy (reference/howto/procedures/troubleshooting/best-practices), directory-category matching, validate.sh CI rules. Triggers: kb/, KB document, architecture note, SOP, runbook, howto, frontmatter, knowledge base entry, documentation standard. Load when creating or editing any file under kb/.
+- **ecommerce-patterns**: E-commerce domain patterns: cart, checkout flow, payment providers (Stripe/Adyen), order state machine, inventory, promotions, tax, B2B vs B2C. Triggers: cart, checkout, product, SKU, inventory, payment, Stripe, Shopify, Medusa, Magento, order status, promotion, tax calculation, coupon, refund. Load when working on any e-commerce feature.
 - **evaluate**: Evaluate skill quality and RAG retrieval accuracy
 - **evolve**: Evolve agent definitions via meta-architect
 - **explain**: Explain code, architecture, or concepts with diagrams
 - **explore**: Explore codebase structure, stack, and architecture
 - **fix**: Auto-fix lint errors, type issues, and simple bugs
-- **flutter-patterns**: Loaded when user asks about Flutter or Dart development patterns
-- **git-mastery**: Loaded when user asks about advanced Git workflows or history rewriting
+- **flutter-patterns**: Flutter and Dart development patterns: widget composition, state management (Riverpod/Bloc/Provider), navigation, async, platform channels, performance. Triggers: Flutter, Dart, widget, StatefulWidget, Riverpod, Bloc, Provider, pubspec, Navigator, platform channel, hot reload, StatelessWidget. Load when writing or reviewing Flutter code.
+- **git-mastery**: Advanced Git workflows: interactive rebase, bisect, reflog, cherry-pick, worktrees, history rewriting, submodules, large-file migration (LFS/filter-repo). Triggers: git rebase, bisect, cherry-pick, reflog, force push, history rewrite, detached HEAD, merge conflict, worktree, squash, fixup, submodule. Load when user needs non-trivial Git operations.
 - **grill-me**: Stress-test a plan or design through relentless Socratic questioning, walking down each decision branch until reaching shared understanding. Use when user wants to stress-test a plan, get grilled, validate assumptions, or mentions 'grill me'. Codex-adapted: uses native subagents and plan tracking.
 - **health**: Report service and infrastructure health status
 - **hipaa-validate**: Validate code against HIPAA policy: PHI exposure, missing audit logging, unencrypted transmission/storage, access control gaps, temp file exposure, and missing BAA references
-- **hive-mind**: Loaded when orchestrating multi-agent swarms or consensus workflows
+- **hive-mind**: Multi-agent swarm coordination: consensus voting with confidence scores, output aggregation, file ownership, targeted vs broadcast messaging, map-reduce workflows. Triggers: swarm, hive mind, multi-agent, consensus, parallel agents, team of agents, aggregate results, agent voting, distributed agents. Load when orchestrating 3+ agents working in parallel.
 - **hook-creator**: Creates new Claude Code hooks with guided workflow, strict conventions, and validation
 - **index**: Index codebase into the knowledge base
 - **instinct-review**: Review and manage learned instincts from past sessions
 - **introspect**: Agent self-debugging and recovery. Use when stuck in loops, making repeated errors, or quality degrades. Triggers: introspect, self-debug, stuck, loop, why failing.
-- **java-patterns**: Loaded when user asks about Java development patterns
+- **java-patterns**: Java development patterns: Spring Boot, CompletableFuture, records, sealed types, streams, JPA/Hibernate, Maven/Gradle, virtual threads (Loom). Triggers: Java, Spring, Spring Boot, JPA, Hibernate, Maven, Gradle, CompletableFuture, record type, sealed class, virtual thread. Load when writing or reviewing Java code.
 - **json-mode-patterns**: Loaded when user needs structured JSON output from Claude. Covers tool-use-as-JSON-mode, schema design, parsing, partial recovery, and validation.
-- **kotlin-patterns**: Loaded when user asks about Kotlin development patterns
+- **kotlin-patterns**: Kotlin development patterns: coroutines, Flow, sealed classes, data classes, extension functions, null safety, Ktor, Jetpack Compose, KMP. Triggers: Kotlin, coroutine, Flow, suspend, Ktor, Android Kotlin, Jetpack Compose, sealed class, data class, KMP, kotlinx. Load when writing or reviewing Kotlin code.
 - **lint**: Lint code with auto-detected tools and fix suggestions
 - **mcp-builder**: Build production-grade MCP (Model Context Protocol) servers from scratch using the 4-phase methodology: research, implement, test, evaluate. Use when creating new MCP integrations for external APIs, databases, or internal services.
-- **mcp-patterns**: Loaded when user asks about MCP servers or tool protocol design
+- **mcp-patterns**: MCP (Model Context Protocol) server design: tool schemas, resource patterns, transport selection (stdio/SSE), client configuration, error handling, capability negotiation. Triggers: MCP, Model Context Protocol, MCP server, MCP tool, MCP resource, JSON-RPC, stdio transport, SSE transport, Claude Desktop config, Cursor MCP. Load when building or integrating MCP servers.
 - **mem-search**: Search past coding sessions using natural language. Finds relevant observations, decisions, and context from previous work.
 - **migrate**: Run database migrations with backup verification
-- **migration-patterns**: Loaded when user asks about database migrations or zero-downtime deploys
+- **migration-patterns**: Zero-downtime database migration patterns: expand-contract, double-write, backfill, blue-green schema changes, feature flags, rollback safety, online DDL. Triggers: migration, schema change, zero-downtime, expand-contract, double-write, backfill, ALTER TABLE, column rename, safe deploy, online DDL. Load when planning non-trivial DB schema changes.
 - **model-routing-patterns**: Loaded when user builds multi-model pipelines (Haiku/Sonnet/Opus). Covers cost-optimized routing, escalation, sub-agent delegation, and fallback chains.
 - **night-watch**: Run autonomous maintenance and dependency updates
-- **observability-patterns**: Loaded when user asks about logging, metrics, or tracing patterns
+- **observability-patterns**: Observability: structured logging, metrics (RED/USE/four golden signals), distributed tracing (OpenTelemetry), correlation IDs, log aggregation, SLO/SLI. Triggers: logging, log level, metrics, Prometheus, Grafana, OpenTelemetry, trace, span, structured log, observability, monitoring, SLO, SLI, alerting. Load when adding or reviewing logs, metrics, or traces.
 - **onboard**: Generate project onboarding materials
 - **orchestrate**: Coordinate multiple specialized agents in parallel Codex-adapted: uses native subagents and plan tracking.
 - **panic**: Emergency stabilization via system-governor agent
-- **performance-profiling**: Loaded when user asks about performance profiling or optimization
+- **performance-profiling**: Performance measurement and optimization: four golden signals (latency/traffic/errors/saturation), p50/p95/p99, baseline-change-measure loop, flame graphs, load testing. Triggers: performance, slow, latency, p99, flame graph, profile, bottleneck, optimization, load test, benchmark, CPU profiling, memory leak. Load when diagnosing or optimizing slow code or services.
 - **persona**: Switch engineering persona at runtime: backend-lead, frontend-lead, devops-eng, junior-dev
 - **plan**: Plan implementation with tasks and success criteria
-- **plan-writing**: Loaded when user asks to write an implementation plan or pre-mortem
+- **plan-writing**: Implementation plan and pre-mortem drafting: phase breakdown, success criteria, risks, rollback plan, acceptance tests, estimated effort. Triggers: implementation plan, pre-mortem, phased plan, project plan, task breakdown, success criteria, rollback strategy, risk register. Load when user asks to write a plan or pre-mortem document.
 - **plugin-creator**: Creates experimental opt-in plugin packs with manifests, conventions, and optional module scaffolding for Claude and Codex runtimes
 - **pr**: Create pull requests with pre-flight validation
 - **prd-to-issues**: Break a PRD into independently-grabbable GitHub issues using vertical slices with HITL/AFK tagging and dependency ordering. Use when user wants to convert a PRD to issues, create tickets, or break down a PRD into work items.
@@ -518,29 +518,29 @@ Skills are invocable commands or auto-loaded knowledge sources:
 - **predict**: Predict regressions and impact before changes land
 - **prompt-caching-patterns**: Loaded when user builds with Anthropic API and needs to cut cost or latency via prompt caching. Covers TTL, cache breakpoints, stacking, invalidation, and measuring hit rate.
 - **qa-session**: Interactive QA session where user reports bugs conversationally and agent files GitHub issues with domain language. Explores codebase in background for context. Use when user wants to report bugs, do QA, file issues conversationally, or mentions QA session. Codex-adapted: uses native subagents and plan tracking.
-- **rag-patterns**: Loaded when user asks about RAG systems, embeddings, or vector search
+- **rag-patterns**: RAG architecture: embeddings, chunking strategies, hybrid search (BM25 + vector), reranking, CRAG/self-correcting, multi-hop reasoning, evaluation metrics. Triggers: RAG, embedding, vector search, pgvector, Qdrant, Pinecone, Weaviate, chunking, reranker, retrieval, hybrid search, semantic search, knowledge base, cosine similarity. Load when building or tuning RAG systems.
 - **refactor**: Refactor code for quality and maintainability
 - **refactor-plan**: Create a detailed refactor plan with tiny commits via user interview, then file as a GitHub issue RFC. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps. Codex-adapted: uses native subagents and plan tracking.
 - **repeat**: Run a prompt or slash command on a recurring interval until task complete or limits reached. Use when user wants to set up a recurring task, poll for status, or run something repeatedly on an interval. Codex-adapted: uses native subagents and plan tracking.
-- **research-mastery**: Loaded when user asks to research, verify, or synthesize information
+- **research-mastery**: Hierarchical information retrieval following strict order: KB first (smart_query/crag_search), then MCP/Context7, then web search, then LLM knowledge as last resort. Triggers: research, find information, verify fact, synthesize sources, fact-check, cross-reference, multi-source, cite sources, investigate topic. Load when any task requires external or cross-source knowledge.
 - **review**: Review code for quality, security, and correctness
 - **rollback**: Roll back a deployment safely with verification
-- **ruby-patterns**: Loaded when user asks about Ruby development patterns
-- **rust-patterns**: Loaded when user asks about Rust development patterns
+- **ruby-patterns**: Ruby and Rails development patterns: blocks, metaprogramming, ActiveRecord, Sidekiq, RSpec, Sorbet/RBS, Hanami, Roda, Rack middleware. Triggers: Ruby, Rails, ActiveRecord, Sidekiq, RSpec, gem, Gemfile, bundler, rake, Hanami, Sorbet. Load when writing or reviewing Ruby code.
+- **rust-patterns**: Rust development patterns: ownership, borrowing, lifetimes, async (Tokio), error handling (Result/anyhow/thiserror), traits, macros, zero-cost abstractions, unsafe boundaries. Triggers: Rust, borrow checker, lifetime, Tokio, async Rust, cargo, trait, impl, Result, unsafe, lifetime annotation, clippy. Load when writing or reviewing Rust code.
 - **search**: Search the knowledge base with semantic and hybrid modes
-- **security-patterns**: Loaded when user asks about security, OWASP, or auth patterns
+- **security-patterns**: Application security: OWASP Top 10, authN/authZ, input validation, secrets management, TLS, CSRF/XSS/SQLi, session handling, JWT, rate limiting, CSP. Triggers: security, OWASP, auth, JWT, CSRF, XSS, SQL injection, secrets, encryption, TLS, authentication, authorization, CSP, CORS, password hashing. Load when touching auth code, handling user input, or doing security review.
 - **seo-validate**: Validate code against SEO best practices: W3C semantics, meta/OG tags, Schema.org, hreflang, Core Web Vitals (LCP/INP/CLS), resource hints, GEO, SPA/SSG/CSR crawlability, technical SEO, accessibility-for-SEO. Supports React/Next/Nuxt/Astro/Gatsby/SvelteKit/Remix/Angular/Vue/static HTML.
 - **skill-audit**: Scan skills and agents for security risks: dangerous patterns, secrets, excessive permissions
 - **skill-creator**: Create new skills from templates with guided workflow
 - **subagent-development**: Execute implementation plans using fresh subagents per task with two-stage review: spec compliance first, then code quality. Use when executing plans with independent tasks. Codex-adapted: uses native subagents and plan tracking.
 - **swarm**: Execute tasks via Map-Reduce, Consensus, or Relay swarms Codex-adapted: uses native subagents and plan tracking.
-- **swift-patterns**: Loaded when user asks about Swift or iOS development patterns
+- **swift-patterns**: Swift and iOS development patterns: SwiftUI, Combine, async/await, property wrappers, actors, Swift Package Manager, Core Data, UIKit interop, @MainActor. Triggers: Swift, SwiftUI, Combine, iOS, Xcode, actor, property wrapper, Core Data, SPM, UIKit, @MainActor, @State, @Binding. Load when writing or reviewing Swift code.
 - **tdd**: Test-driven development with red-green-refactor loop and vertical slices. Use when user wants TDD, test-first development, red-green-refactor, or building features with tests driving the implementation. Codex-adapted: uses native subagents and plan tracking.
 - **teams**: Launch pre-configured Agent Teams for common workflows Codex-adapted: uses native subagents and plan tracking.
 - **test**: Run tests with coverage analysis and reporting
-- **testing-patterns**: Loaded when user asks about testing strategy, fixtures, or mocking
+- **testing-patterns**: Testing strategy and craft: pyramid vs trophy, unit/integration/e2e split, fixtures, mocks vs fakes vs stubs, AAA pattern, flaky test diagnosis, coverage goals, property-based testing. Triggers: test, testing strategy, fixture, mock, stub, AAA, unit test, integration test, e2e, Playwright, Cypress, flaky, coverage, TDD, test pyramid. Load when writing, reviewing, or designing test suites.
 - **triage-issue**: Triage a bug by deeply exploring the codebase for root cause, then create a GitHub issue with a TDD-based fix plan. Mostly hands-off — minimal user interaction. Use when user reports a bug, wants to investigate an issue, mentions triage, or wants a fix plan. Codex-adapted: uses native subagents and plan tracking.
-- **typescript-patterns**: Loaded when user asks about TypeScript patterns or type safety
+- **typescript-patterns**: TypeScript type safety patterns: strict mode, generics, conditional types, template literals, discriminated unions, branded types, Zod, satisfies operator, const assertions. Triggers: TypeScript, TS, generics, conditional type, utility type, strict, Zod, satisfies, discriminated union, type safety, type narrowing, template literal type. Load when writing or reviewing TypeScript code.
 - **ubiquitous-language**: Extract a DDD-style ubiquitous language glossary from the conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, or mentions DDD or domain model.
 - **verification-before-completion**: Loaded when agent is about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
 - **workflow**: Start and manage autonomous agent workflows Codex-adapted: uses native subagents and plan tracking.

package/CHANGELOG.md

@@ -7,7 +7,35 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ---
 
-## v2.8.0 — Security Hardening & GHAS Integration (2026-04-18)
+## v2.10.0 — Constitution Article VI: Repair Discipline (2026-04-21)
+
+### Added
+- **Constitution Article VI — Repair Discipline** (`app/constitution.md`) — four new immutable rules: no dead code (VI.1), fix every found bug (VI.2), tests and docs follow behavior (VI.3), verify before claiming done (VI.4). Closes the gap where agents deferred "świadome pominięcie", "out of scope", or "separate PR" fixes for work that was a direct consequence of the current change. Articles I–V remain unchanged.
+- **`system-governor` Art. VI audit protocol** (`app/agents/system-governor.md`) — agent gained `Grep` + `Glob` tools and a four-part audit that runs before any completion claim: VI.1 dead-symbol grep, VI.2 deferred-work scan (scoped to commit message + PR body + non-`.md` code lines + agent summary, so skill docs that legitimately document "Out of Scope" headings are not false-positives), VI.3 behavior/test/doc coverage detection, VI.4 diff re-read. Outputs a structured verdict with per-Article PASS/VETO citations.
+- **`clean-code` skill Art. VI checklist items** — two new checklist entries ("No dead code — grep-verified zero references", "Every found bug fixed") plus three new "Challenged Assumptions" rows that call out the common deferral rationalizations.
+- **`refactor-plan` skill Art. VI anchor** — mandatory dead-code cleanup per step, not deferred. Only transitional expand-contract phases may leave both paths live, and the cleanup step must be explicitly listed.
+- **`verification-before-completion` skill Art. VI rows** — three new rows in the evidence-vs-non-evidence table covering VI.1/VI.2/VI.4, plus a "Constitutional Anchors" section that pins the skill to Art. VI.4.
+- **`coding-style` rule Art. VI sections** (`app/rules/common/coding-style.md`, v1.0.0 → v1.1.0) — expanded "No Dead Code" section and new "Fix Every Found Bug" section, both citing the Constitutional article they implement.
+
+### Changed
+- **`system-governor` description** widened to reflect Art. VI audit scope, tools broadened from `Read, Write, Bash` to `Read, Write, Bash, Grep, Glob` (needed for symbol-reference grep during VI.1).
+
+### Notes
+- No skill/agent/hook counts changed. Totals remain: 44 agents, 99 skills, 666 tests.
+- Art. VI is enforcement-level discipline, not workflow change — existing pipelines keep passing. Governor veto gates a completion claim, not a commit.
+
+---
+
+## v2.9.0 — Skill Routability & Description Lint (2026-04-19)
+
+### Changed
+- **30 knowledge-skill descriptions rewritten** — every skill with `user-invocable: false` used the `"Loaded when user asks about X"` shape, which carries no action verb and no concrete trigger keywords. Per [Anthropic skill docs](https://code.claude.com/docs/en/skills.md), Claude Code auto-routes skills using only the `description:` field (+ optional `when_to_use:`), so weak descriptions silently lowered hit rate. Rewritten with the pattern `[capability]. Triggers: [keywords]. Load when [...]`. Affected skills: `api-patterns`, `app-builder`, `architecture-decision`, `ci-cd-patterns`, `clean-code`, `csharp-patterns`, `database-patterns`, `debugging-tactics`, `design-engineering`, `docker-devops`, `documentation-standards`, `ecommerce-patterns`, `flutter-patterns`, `git-mastery`, `hive-mind`, `java-patterns`, `kotlin-patterns`, `mcp-patterns`, `migration-patterns`, `observability-patterns`, `performance-profiling`, `plan-writing`, `rag-patterns`, `research-mastery`, `ruby-patterns`, `rust-patterns`, `security-patterns`, `swift-patterns`, `testing-patterns`, `typescript-patterns`.
+
+### Added
+- **`scripts/audit_skills.py` description-quality lint (`check_description`)** — new WARN rules that prevent the `"Loaded when user asks about/to ..."` anti-pattern from returning. Enforces three limits on auto-loadable skills: `description + when_to_use ≤ 1536 chars` (Anthropic truncation limit), knowledge-skill description ≥ 80 chars, and a regex block on the historical weak-opening patterns. Task skills (`disable-model-invocation: true`) are skipped — their description is a menu label, not a routing signal.
+- **Regenerated `AGENTS.md`, `llms.txt`, `llms-full.txt`, `GEMINI.md`, `.github/copilot-instructions.md`** — machine-readable catalogs now carry the new descriptions. External clients (Cursor, Windsurf, Copilot, Gemini CLI, Codex) get the same routing signal as Claude Code.
+
+
 
 ### Added
 - **`scripts/audit_skills.py --sarif`** — emits SARIF 2.1.0 JSON compatible with GitHub Advanced Security Code Scanning. Severity maps HIGH→error / WARN→warning / INFO→note. Enables the GitHub Security tab to ingest audit findings directly.

package/README.md

@@ -10,12 +10,11 @@
 
 ---
 
-## What's New in v2.8.0
+## What's New in v2.10.0
 
-- **SARIF + permissions audit** — `audit_skills.py --sarif` emits SARIF 2.1.0 for GitHub Advanced Security Code Scanning; `--permissions` prints per-skill tool usage (e.g. "50 skills use Bash") and flags broad Bash+Write+Edit access.
-- **Signed npm provenance** — the publish workflow now runs with `--provenance`; published tarballs carry a cryptographic build-origin attestation verifiable via `npm audit signatures`.
-- **Checksum-pinned URL sources** — `sources.json` now persists `sha256` of every URL-sourced rule/hook and warns on upstream content change. `AI_TOOLKIT_STRICT_PIN=1` turns mismatches into a hard CI failure.
-- **Security hardening** — `tarfile.extract` uses `filter="data"` on Python 3.12+; `session-start.sh` sanitises `VERSION_MSG` before `osascript`/`powershell.exe`; install-time `subprocess.run` calls now time out at 120 s.
+- **Constitution Article VI — Repair Discipline** — four new immutable rules close the "świadome pominięcie / out of scope / separate PR" loophole: no dead code (VI.1), fix every found bug (VI.2), tests and docs follow behavior (VI.3), verify before claiming done (VI.4). A bug fix is a bug fix; a feature is a feature; orphaned code and deferred-adjacent fixes no longer pass review.
+- **`system-governor` gains Art. VI audit protocol** — the governor now runs a four-part check before any completion claim, with per-Article PASS/VETO citations. Scope is intentionally scoped to commit message + PR body + non-`.md` code lines + agent summary, so skill docs that legitimately use "Out of Scope" as a section heading do not trigger false positives.
+- **Rule, skill, and agent reinforcement** — `coding-style` rule (v1.1.0), `clean-code`, `refactor-plan`, and `verification-before-completion` skills all carry explicit Art. VI anchors and checklist rows. Totals unchanged: 44 agents, 99 skills, 666 tests.
 
 See [CHANGELOG.md](CHANGELOG.md) for full history.
 

package/app/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "ai-toolkit",
   "description": "Professional-grade Claude Code toolkit with persona presets, skill security auditor, expanded lifecycle hooks, experimental opt-in plugin packs, benchmark harvesting, and multi-tool support.",
-  "version": "2.8.0",
+  "version": "2.10.0",
   "author": {
     "name": "SoftSpark",
     "url": "https://github.com/softspark"

package/app/agents/system-governor.md

@@ -3,7 +3,7 @@ name: system-governor
 description: "The Guardian of the Constitution. Validates all evolutionary changes and enforces immutable rules. Has VETO power."
 model: opus
 color: red
-tools: Read, Write, Bash
+tools: Read, Write, Bash, Grep, Glob
 skills: research-mastery
 ---
 
@@ -12,7 +12,7 @@ skills: research-mastery
 You are the **System Governor**. You serve the Constitution, not the Orchestrator.
 
 ## Core Mission
-Ensure that no agent (especially `meta-architect`) violates the Immutable Rules.
+Ensure that no agent (especially `meta-architect`) violates the Immutable Rules, and that no task is claimed "done" while Constitutional Article VI (Repair Discipline) is breached.
 
 ## Mandatory Protocol (VETO POWER)
 Before any `/evolve` or `meta-architect` change is applied:
@@ -21,6 +21,7 @@ Before any `/evolve` or `meta-architect` change is applied:
    - Removing tests? (Violation Art. III.1)
    - Deleting logs? (Violation Art. III.2)
    - Bypassing KB? (Violation Art. II.2)
+   - Leaving dead code, missing tests for changed behavior, stale docs? (Violation Art. VI)
 3. **Verdict**:
    - **APPROVE**: "Constitutional Check Passed."
    - **VETO**: "VIOLATION DETECTED [Article X]. Change Rejected."
@@ -34,24 +35,113 @@ On startup, verify:
 ## Capabilities
 
 ### 1. Constitutional Review
-- **Input**: Pull Request / Diff from `meta-architect`.
-- **Output**: Pass/Fail with citation.
+- **Input**: Pull Request / Diff from `meta-architect` or a completion claim.
+- **Output**: Pass/Fail with citation per Article.
 
 ### 2. Emergency Halt
 - **Trigger**: "Kill Switch" activated or massive deletion detected.
 - **Action**: Lock the task. Notify User immediately.
 
+### 3. Article VI Audit (Repair Discipline)
+Run before approving any completion claim that touches code. Each check returns PASS / VETO with evidence.
+
+#### VI.1 — No Dead Code
+Produce the list of symbols the change removed or renamed (entities, classes, functions, API resources, l10n keys, imports, DTO fields). For each:
+```bash
+# Example heuristics; adapt to project's grep/search tools.
+git diff --name-only <base>..HEAD | xargs -I{} grep -nE "OldSymbol" {} 2>/dev/null || true
+rg --no-heading --line-number "OldSymbol" .
+```
+Also check whether any existing file is now unreferenced because the change stopped calling it:
+```bash
+# For every .php / .dart / .ts file not modified in this diff, search for ANY caller of its public symbols.
+# Zero-caller files are candidates for deletion.
+```
+- **VETO** if grep returns zero references for any removed symbol AND the source file still exists.
+- **VETO** if the diff stops calling a whole file and that file is not deleted.
+- **APPROVE** only when dead-code grep is clean.
+
+Rationalizations explicitly rejected: "pre-existing", "legacy", "separate refactor", "out of scope", "świadome pominięcie".
+
+#### VI.2 — Fix Every Found Bug
+Scan ONLY the three surfaces where a deferral is actually asserted — NOT doc files that legitimately document those phrases as headings or examples.
+
+**Scope (in priority order):**
+1. **Commit message / PR body** — the author's own statement of what this change does:
+   ```bash
+   git log -1 --format=%B HEAD | grep -iE "TODO\(defer\)|FIXME|świadome pominięcie|out of scope|second step|osobny refactor|separate PR"
+   gh pr view --json body -q .body 2>/dev/null | grep -iE "TODO\(defer\)|FIXME|świadome pominięcie|out of scope|second step|osobny refactor|separate PR"
+   ```
+2. **Newly-added lines in NON-documentation files** — code changes only, never `.md` prose:
+   ```bash
+   git diff --unified=0 <base>..HEAD -- ':!*.md' ':!kb/**' ':!app/skills/**/SKILL.md' ':!app/agents/**/*.md' \
+     | grep -E "^\+" | grep -v "^\+\+\+" \
+     | grep -iE "TODO\(defer\)|FIXME|świadome pominięcie|out of scope|second step|osobny refactor|separate PR"
+   ```
+3. **Agent completion summary in the current chat transcript** — the text the orchestrator is about to emit as "done".
+
+**Explicitly OUT OF SCOPE for this check:**
+- The body of any `.md` file (skill docs, KB, README, CHANGELOG, ADRs). Skills like `a11y-validate`, `clean-code`, `refactor-plan`, `write-a-prd`, `hipaa-validate`, and agents like `product-manager` legitimately use "Out of Scope" as section headings or examples. Matching against their prose is a false positive.
+- Historical commits (scan only the diff under review, not `git log` of the whole branch).
+
+**Rulings:**
+- **VETO** any hit in surfaces 1-3 unless paired with an explicit user decision recorded in the PR description or chat.
+- **VETO** if the agent's own summary uses those phrases for fixes that are a direct consequence of the change.
+- **APPROVE** when all three surfaces are clean, even if `.md` docs in the diff contain the phrases as documentation.
+
+#### VI.3 — Tests and Docs Follow Behavior
+Detect behavior change surface:
+```bash
+# Changed public API, processor, controller, endpoint, or exported contract?
+git diff --name-only <base>..HEAD | rg -e 'Processor\.php$' -e 'Controller\.php$' -e 'Api/' -e 'api/endpoints/' -e 'routes' -e 'ApiResource/'
+```
+For every modified public-surface file, verify:
+- Corresponding integration test exists and was modified in this diff, OR a new integration test was added.
+- Unit test-only coverage for behavior exposed over API is INSUFFICIENT.
+- Docs (`kb/`, `README.md`, `CLAUDE.md`, ADRs) that reference the changed behavior are updated.
+- **VETO** if any of these are missing.
+
+#### VI.4 — Verify Before Claiming Done
+Before allowing an agent to emit a completion claim:
+```bash
+git diff --stat <base>..HEAD     # Re-read full shape of the change
+git status                        # Nothing stranded in the working tree
+```
+- **VETO** if working tree shows untracked artefacts that look like half-finished work (new files without references, orphan migrations without entity updates).
+- **VETO** if the agent's text claims success but any prior Art. VI check is still failing.
+
 ## Output Format
 ```markdown
 ## ⚖️ Governance Verdict
 
 ### Proposed Change
-Modified `tech-lead.md` to remove `view_skill("research-mastery")`.
+<one-sentence summary of the diff>
 
 ### Constitutional Check
-- **Article II.2 (Research Protocol)**: VIOLATED.
-- **Reason**: Trying to bypass mandatory knowledge check.
+- **Article II.2 (Research Protocol)**: <PASSED | VIOLATED — reason>
+- **Article III.1 (Tests are Sacred)**: <PASSED | VIOLATED — reason>
+- **Article VI.1 (No Dead Code)**: <PASSED | VIOLATED — orphan evidence>
+- **Article VI.2 (Fix Every Found Bug)**: <PASSED | VIOLATED — deferred fix evidence>
+- **Article VI.3 (Tests and Docs)**: <PASSED | VIOLATED — missing coverage>
+- **Article VI.4 (Verify Before Done)**: <PASSED | VIOLATED — stale claim evidence>
 
 ### RULING
-🔴 **VETO**. This change is rejected.
+🟢 **APPROVE** — Constitutional Check Passed.
+OR
+🔴 **VETO** — <Articles violated>. Change Rejected. Required remediation: <bulleted fixes>.
 ```
+
+## When To Run Art. VI Checks
+- Before any `meta-architect` / `/evolve` apply.
+- Before any orchestrator emits a completion claim on a task that touched code.
+- On-demand when invoked directly by the user ("governor, audit this diff").
+- NOT required for documentation-only changes outside `kb/`, scratch files, or explicit WIP commits marked as such.
+
+## Known Bypass Attempts (Auto-Reject)
+| Phrase in the diff or summary | Default ruling |
+|-------------------------------|----------------|
+| "świadome pominięcie"          | VETO — direct Art. VI.2 violation |
+| "out of scope (for now)"       | VETO unless user-approved in conversation |
+| "separate PR will fix"         | VETO unless the follow-up ticket ID is cited |
+| "pre-existing dead code, leaving it" | VETO per Art. VI.1 |
+| "tests will follow"            | VETO per Art. VI.3 |

package/app/constitution.md

@@ -1,6 +1,6 @@
 ---
 title: "The Immutable Constitution of the System"
-last_updated: "2026-01-30"
+last_updated: "2026-04-21"
 status: IMMUTABLE
 ---
 
@@ -43,3 +43,9 @@ status: IMMUTABLE
 ## Article V: Resource Governance
 1. **No Destructive Commands**: Commands like `rm -rf`, `DROP TABLE`, `FORMAT` require explicit user confirmation before execution.
 2. **Model Tier Respect**: Agents MUST operate within their assigned model tier. Model tier changes require user approval.
+
+## Article VI: Repair Discipline
+1. **No Dead Code**: Unused code (files, classes, functions, imports, l10n keys, variables) MUST be removed in the same change that makes it unused — whether the change introduced it or merely exposed it. "Pre-existing", "legacy", "separate refactor", or "out of scope" are NOT valid reasons to keep dead code when its unusedness is verifiable (grep returns zero references across the repo).
+2. **Fix Every Found Bug**: Any bug, gap, missing test for changed behavior, or stale doc discovered during a task MUST be fixed in the same change. Deferring with "świadome pominięcie", "second step", "osobny refactor", or "poza scope" is forbidden when the issue is a direct consequence of, or directly adjacent to, the work being done. Legitimate deferral is permitted only when (a) the fix requires a user decision — in which case the agent MUST surface it explicitly and ask, not bury it in a summary — or (b) the issue is genuinely unrelated to the current change surface.
+3. **Tests and Docs Follow Behavior**: When behavior changes, the corresponding integration and unit tests, plus any affected documentation, MUST be updated in the same change. A unit test on a new helper is not sufficient when the behavior is exposed over an API — add the integration test too.
+4. **Verify Before Claiming Done**: Before marking a task complete, re-read the diff and confirm: no orphaned references, no missing test coverage for changed paths, no stale docs. If any are present, the task is not done.

package/app/rules/common/coding-style.md

@@ -1,7 +1,7 @@
 ---
 language: common
 category: coding-style
-version: "1.0.0"
+version: "1.1.0"
 ---
 
 # Universal Coding Style
@@ -51,7 +51,17 @@ version: "1.0.0"
 - Match existing style, even if you would do it differently.
 - Do not "improve" adjacent code, comments, or formatting unprompted.
 - Orphan cleanup: remove imports/variables/functions that YOUR changes made unused.
-- Do not remove pre-existing dead code unless explicitly asked.
+
+## No Dead Code (Constitution Art. VI.1)
+- When a refactor leaves a file, class, function, import, l10n key, or variable unused, DELETE it in the same change. Verify via grep that zero references remain in the repo.
+- This applies to pre-existing code too, if your work makes its unusedness verifiable. "Legacy", "separate refactor", "out of scope", or "świadome pominięcie" are NOT valid excuses.
+- Before claiming the task done: grep for every symbol you removed or renamed; fix orphaned references.
+
+## Fix Every Found Bug (Constitution Art. VI.2)
+- A bug, missing test for changed behavior, or stale doc discovered while working on a task MUST be fixed in the same change — not deferred to "second step", "separate PR", or "świadome pominięcie".
+- When behavior changes, update integration AND unit tests AND the affected docs alongside. A unit test on a new helper is not sufficient when the behavior is exposed over an API — add the integration test too.
+- Legitimate deferral exists ONLY when: (a) the fix requires a user decision — in that case, surface it explicitly and ask, don't bury in a summary; or (b) the issue is genuinely unrelated to the current change surface.
+- Before marking done: re-read the diff and confirm no orphaned references, no missing test coverage for changed paths, no stale docs. If any are present, keep working.
 
 ## Goal-Driven Execution
 - Transform vague tasks into verifiable goals before starting.

package/app/skills/api-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: api-patterns
-description: "Loaded when user asks about REST API design or GraphQL patterns"
+description: "REST and GraphQL API design patterns: resource naming, versioning, pagination, error contracts, idempotency, HATEOAS, OpenAPI. Triggers: API design, REST, GraphQL, endpoint, route, OpenAPI, Swagger, pagination, rate limit, versioning, idempotency key. Load when designing or reviewing any HTTP API surface."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/app-builder/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: app-builder
-description: "Loaded when user asks to scaffold or build a full-stack app"
+description: "Full-stack app scaffolding with stack-selection matrix: Next.js, React+Vite, Nuxt, Astro, FastAPI, Django, Laravel, React Native, Flutter, Unity. Triggers: scaffold, bootstrap, new project, starter template, build app, landing page, dashboard, API, mobile app, CLI, e-commerce, game. Load when user wants to start a new project from scratch."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/architecture-decision/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: architecture-decision
-description: "Loaded when user asks about architecture decisions or architecture note writing"
+description: "Architecture decision making via trade-off analysis in RFC/RFD/ADR format: context, constraints, 3+ options, comparison, recommendation. Triggers: architecture decision, ADR, RFC, RFD, trade-offs, options comparison, design choice, pick between, should we use, evaluate approach. Load when weighing 2+ architectural options or writing decision records."
 effort: medium
 user-invocable: false
 allowed-tools: Read, Write

package/app/skills/ci-cd-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ci-cd-patterns
-description: "Loaded when user asks about CI/CD pipelines or deployment automation"
+description: "CI/CD pipeline and deployment automation: GitHub Actions, GitLab CI, Jenkins, build stages, caching, artifact promotion, blue-green, canary, rollback gates. Triggers: CI, CD, pipeline, GitHub Actions, workflow YAML, deploy automation, release, artifact, rollout, canary, blue-green. Load when designing or fixing a build/release pipeline."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/clean-code/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: clean-code
-description: "Loaded when user asks about clean code, naming, or code quality"
+description: "Code quality principles: meaningful names, single responsibility, DRY, small functions, clear intent, guard clauses, refactoring rules. Triggers: clean code, naming, refactor for clarity, code smell, SRP, DRY, long function, god class, magic number, dead code. Load when reviewing or writing any production code."
 effort: medium
 user-invocable: false
 allowed-tools: Read
@@ -97,6 +97,8 @@ Keep modules focused. Order contents consistently: imports (stdlib, third-party,
 - [ ] Resources are properly cleaned up
 - [ ] No code duplication
 - [ ] Tests cover critical paths
+- [ ] **No dead code** — grep-verified zero references for every removed/renamed symbol; pre-existing dead code touched by this change is deleted too (Constitution Art. VI.1)
+- [ ] **Every found bug fixed** — bugs, missing tests for changed behavior, and stale docs discovered during the task are fixed in the same change, not deferred (Constitution Art. VI.2)
 
 ---
 
@@ -109,6 +111,9 @@ Keep modules focused. Order contents consistently: imports (stdlib, third-party,
 | "Short variable names are faster to type" | You type it once, readers parse it hundreds of times — optimize for reading |
 | "DRY means never repeat anything" | Wrong DRY creates coupling — duplicate until you see the real abstraction |
 | "More abstractions = cleaner code" | Premature abstraction is worse than duplication — wait for the third use |
+| "That dead file is pre-existing, not my problem" | If your change makes it verifiably unused, deleting it IS your problem (Constitution Art. VI.1) |
+| "I'll fix the missing test in a separate PR" | Forbidden when the test covers behavior you just changed — add it now (Constitution Art. VI.2) |
+| "Świadome pominięcie" / "out of scope" | Deferral of directly-adjacent fixes is forbidden; if a user decision is needed, ASK, don't bury it |
 
 ## Language-Specific References
 

package/app/skills/csharp-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: csharp-patterns
-description: "Loaded when user asks about C# or .NET development patterns"
+description: "C# and .NET development patterns: LINQ, async/await, dependency injection, records, nullable reference types, ASP.NET Core minimal APIs, EF Core, MediatR. Triggers: C#, .NET, dotnet, ASP.NET, EF Core, LINQ, IServiceCollection, record type, async C#, nullable reference types. Load when writing or reviewing C#/.NET code."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/database-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: database-patterns
-description: "Loaded when user asks about database schema or query optimization"
+description: "Database schema design and query optimization: normalization, indexing strategies, joins, N+1, transactions, isolation levels, partitioning, EXPLAIN plans. Triggers: schema, table design, index, slow query, N+1, PostgreSQL, MySQL, SQL Server, SQL, EXPLAIN, query plan, transaction, deadlock. Load when designing tables or tuning queries."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/debugging-tactics/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: debugging-tactics
-description: "Loaded when user is debugging an issue or needs root cause analysis"
+description: "Root-cause debugging with 4-phase method: investigation, hypothesis, validation, fix. No fix without RCA. Triggers: bug, error, exception, stack trace, not working, intermittent, flaky, crash, regression, fails sometimes, why is X happening, broken after. Load when user reports a bug or asks to investigate failing code."
 effort: medium
 user-invocable: false
 allowed-tools: Grep, Read

package/app/skills/design-engineering/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: design-engineering
-description: "Loaded when user asks about UI animations or CSS design craft"
+description: "UI craftsmanship (Emil Kowalski school): animation frequency rules, easing curves, micro-interactions, state polish, invisible-details philosophy. Triggers: animation, transition, ease-out, ease-in-out, motion, micro-interaction, hover state, loading state, UI polish, design detail, spring curve, delightful UX. Load when building or reviewing interactive UI."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/docker-devops/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: docker-devops
-description: "Loaded when user asks about Docker, containers, or DevOps patterns"
+description: "Docker, containers, Kubernetes, and DevOps patterns: Dockerfile best practices, multi-stage builds, compose, k8s manifests, Helm charts, service mesh, image hardening. Triggers: Docker, Dockerfile, container, image, Kubernetes, k8s, compose, Helm, registry, layer caching, service mesh, pod, deployment yaml. Load when writing or fixing container/orchestration configs."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/documentation-standards/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: documentation-standards
-description: "Loaded when creating or updating KB documents, architecture notes, SOPs, or any file in kb/ directory"
+description: "KB document conventions: YAML frontmatter (7 required fields), 5-category taxonomy (reference/howto/procedures/troubleshooting/best-practices), directory-category matching, validate.sh CI rules. Triggers: kb/, KB document, architecture note, SOP, runbook, howto, frontmatter, knowledge base entry, documentation standard. Load when creating or editing any file under kb/."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/ecommerce-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ecommerce-patterns
-description: "Loaded when user asks about e-commerce or shopping cart features"
+description: "E-commerce domain patterns: cart, checkout flow, payment providers (Stripe/Adyen), order state machine, inventory, promotions, tax, B2B vs B2C. Triggers: cart, checkout, product, SKU, inventory, payment, Stripe, Shopify, Medusa, Magento, order status, promotion, tax calculation, coupon, refund. Load when working on any e-commerce feature."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/flutter-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: flutter-patterns
-description: "Loaded when user asks about Flutter or Dart development patterns"
+description: "Flutter and Dart development patterns: widget composition, state management (Riverpod/Bloc/Provider), navigation, async, platform channels, performance. Triggers: Flutter, Dart, widget, StatefulWidget, Riverpod, Bloc, Provider, pubspec, Navigator, platform channel, hot reload, StatelessWidget. Load when writing or reviewing Flutter code."
 effort: medium
 user-invocable: false
 allowed-tools: Read

package/app/skills/git-mastery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: git-mastery
-description: "Loaded when user asks about advanced Git workflows or history rewriting"
+description: "Advanced Git workflows: interactive rebase, bisect, reflog, cherry-pick, worktrees, history rewriting, submodules, large-file migration (LFS/filter-repo). Triggers: git rebase, bisect, cherry-pick, reflog, force push, history rewrite, detached HEAD, merge conflict, worktree, squash, fixup, submodule. Load when user needs non-trivial Git operations."
 effort: medium
 user-invocable: false
 allowed-tools: Read, Grep, Glob

package/app/skills/hive-mind/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hive-mind
-description: "Loaded when orchestrating multi-agent swarms or consensus workflows"
+description: "Multi-agent swarm coordination: consensus voting with confidence scores, output aggregation, file ownership, targeted vs broadcast messaging, map-reduce workflows. Triggers: swarm, hive mind, multi-agent, consensus, parallel agents, team of agents, aggregate results, agent voting, distributed agents. Load when orchestrating 3+ agents working in parallel."
 effort: medium
 user-invocable: false
 allowed-tools: Read