@event4u/agent-config 2.26.0 → 3.1.0

package/.agent-src/skills/playwright-testing/SKILL.md

@@ -3,6 +3,18 @@ name: playwright-testing
 description: "Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns."
 source: package
 domain: quality
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # playwright-testing

package/.agent-src/skills/po-discovery/SKILL.md

@@ -6,6 +6,18 @@ personas:
   - stakeholder
 source: package
 domain: product
+workspaces:
+  - product
+packs:
+  - product-basic
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # po-discovery

package/.agent-src/skills/positioning-strategy/SKILL.md

@@ -6,6 +6,18 @@ tier: senior
 source: package
 domain: product
 context_spine: [product, customer-segment]
+workspaces:
+  - gtm
+packs:
+  - gtm-marketing
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # positioning-strategy

package/.agent-src/skills/privacy-review/SKILL.md

@@ -7,8 +7,18 @@ source: package
 domain: process
 context_spine: [regulatory-regime, customer-segment, product]
 recommended_for_user_types: [ops, finance, creator]
-
-
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # privacy-review

package/.agent-src/skills/project-analysis-core/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-core
 description: "Raw discovery primitives — project discovery, version resolution, docs loading, architecture mapping, execution flow. Called by `universal-project-analysis`. Single-pass scan → `project-analyzer`."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-analysis-core

package/.agent-src/skills/project-analysis-hypothesis-driven/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-hypothesis-driven
 description: "Use when a bug has multiple plausible causes across layers — competing hypotheses, validation loops, evidence-based conclusions — even when the user just says 'why is this happening?'."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-analysis-hypothesis-driven

package/.agent-src/skills/project-analysis-laravel/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-laravel
 description: "Use for deep Laravel project analysis: boot flow, request lifecycle, container usage, Eloquent/data flow, async systems, and Laravel-specific failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-laravel

package/.agent-src/skills/project-analysis-nextjs/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-nextjs
 description: "Use for deep Next.js analysis: server vs client boundaries, routing, data fetching, caching, rendering modes, and hydration/runtime issues."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - nextjs
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-nextjs

package/.agent-src/skills/project-analysis-node-express/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-node-express
 description: "Use for deep Node.js / Express project analysis: boot flow, middleware order, async behavior, data layer, auth/security, and Node-specific runtime failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - typescript
+lifecycle: experimental
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-node-express

package/.agent-src/skills/project-analysis-react/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-react
 description: "Use for deep React analysis: component tree, state flow, props flow, hooks usage, rendering behavior, and React-specific failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - react
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-react

package/.agent-src/skills/project-analysis-symfony/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-symfony
 description: "Use for deep Symfony project analysis: kernel/bootstrap, container wiring, routing/request flow, Doctrine, security, Messenger, and Symfony-specific failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - symfony
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-symfony

package/.agent-src/skills/project-analysis-zend-laminas/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-zend-laminas
 description: "Use for deep Zend Framework or Laminas project analysis: bootstrap, config merge order, service manager, MVC flow, data layer, and migration-specific risks."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - php
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-zend-laminas

package/.agent-src/skills/project-analyzer/SKILL.md

@@ -1,8 +1,20 @@
 ---
 name: project-analyzer
-description: "ONLY when user asks for single-pass tech-stack detection or `agents/analysis/` write-up. Deep multi-pass audit → `universal-project-analysis`. Raw primitives → `project-analysis-core`."
+description: "ONLY when user asks for single-pass tech-stack detection or `agents/evidence/analysis/` write-up. Deep multi-pass audit → `universal-project-analysis`. Raw primitives → `project-analysis-core`."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-analyzer
@@ -29,20 +41,20 @@ A **project analysis** is a systematic walkthrough of the entire codebase that:
 1. **Detects** — framework, language, tech stack, patterns, legacy vs. modern
 2. **Inventories** — modules, services, models, endpoints, tests
 3. **Analyzes** — business domains, data flows, API contracts, dependencies
-4. **Documents** — writes structured analysis files to `agents/analysis/`
+4. **Documents** — writes structured analysis files to `agents/evidence/analysis/`
 5. **Assesses** — identifies gaps, technical debt, missing docs
 
 It orchestrates other skills and commands to produce a comprehensive picture.
 
 ## Analysis output
 
-All analysis results are written to `agents/analysis/` in a structured directory layout.
+All analysis results are written to `agents/evidence/analysis/` in a structured directory layout.
 The goal: **someone could rebuild the project from these documents alone.**
 
 ### Directory structure
 
 ```
-agents/analysis/
+agents/evidence/analysis/
 ├── overview.md                  ← Project profile, tech stack, architecture summary
 ├── architecture/
 │   ├── database.md              ← Schema, connections, multi-tenancy, migrations
@@ -70,7 +82,7 @@ agents/analysis/
 
 ### Domain analysis files
 
-Each business domain gets its own file in `agents/analysis/domains/`. A domain groups
+Each business domain gets its own file in `agents/evidence/analysis/domains/`. A domain groups
 related models, services, controllers, jobs, and events around a business concept:
 
 | Domain             | What it covers                                           |
@@ -139,7 +151,7 @@ Each domain file should contain:
 
 ### Module analysis files
 
-Each module gets its own file in `agents/analysis/modules/`. Format:
+Each module gets its own file in `agents/evidence/analysis/modules/`. Format:
 
 ```markdown
 # Module: {Name}
@@ -247,7 +259,7 @@ After detecting **any** match, record the stack in the analysis output and selec
 - Detect framework, version, tech stack
 - Identify build tools and quality tooling
 - Classify: legacy vs. modern, monolith vs. modular
-- **Output:** `agents/analysis/overview.md`
+- **Output:** `agents/evidence/analysis/overview.md`
 
 ### Phase 2: Architecture
 
@@ -255,14 +267,14 @@ After detecting **any** match, record the stack in the analysis output and selec
 - Identify architectural patterns (MVC, modules, services, repositories)
 - Detect multi-tenancy, queue system, caching
 - Count: models, controllers, services, jobs, commands
-- **Output:** `agents/analysis/architecture/*.md`
+- **Output:** `agents/evidence/analysis/architecture/*.md`
 
 ### Phase 3: Data layer
 
 - List all models with their connections, tables, and key relationships
 - Map database schema: tables, foreign keys, indexes
 - Document multi-tenant split (which tables in which DB)
-- **Output:** `agents/analysis/models/api-database.md`, `customer-database.md`
+- **Output:** `agents/evidence/analysis/models/api-database.md`, `customer-database.md`
 
 ### Phase 4: Business domains
 
@@ -270,38 +282,38 @@ After detecting **any** match, record the stack in the analysis output and selec
 - For each domain: map models → services → controllers → jobs → events
 - Document business rules and data flows
 - Document inter-domain dependencies
-- **Output:** `agents/analysis/domains/{domain}.md` (one per domain)
+- **Output:** `agents/evidence/analysis/domains/{domain}.md` (one per domain)
 
 ### Phase 5: API surface
 
 - List all endpoints with controller, request, resource, OpenAPI attributes
 - Document request/response contracts (field names, types, validation rules)
 - Map version differences (v1 vs v2)
-- **Output:** `agents/analysis/api/endpoints-v1.md`, `endpoints-v2.md`, `contracts.md`
+- **Output:** `agents/evidence/analysis/api/endpoints-v1.md`, `endpoints-v2.md`, `contracts.md`
 
 ### Phase 6: Service map
 
 - List all services with purpose, key methods, and dependencies
 - Map service → repository → model relationships
 - Identify God services (too many responsibilities)
-- **Output:** `agents/analysis/services/service-map.md`
+- **Output:** `agents/evidence/analysis/services/service-map.md`
 
 ### Phase 7: Module inventory (if modules exist)
 
 - List all modules with purpose
 - For each module: structure, public API, internal components, tests
 - Check for module-level agent docs
-- **Output:** `agents/analysis/modules/{module}.md` (one per module)
+- **Output:** `agents/evidence/analysis/modules/{module}.md` (one per module)
 
 ### Phase 8: Infrastructure & testing
 
 - Docker setup, CI/CD pipelines, deployment
 - Test suites, coverage areas, test data strategy
-- **Output:** `agents/analysis/architecture/infrastructure.md`, `agents/analysis/testing/test-map.md`
+- **Output:** `agents/evidence/analysis/architecture/infrastructure.md`, `agents/evidence/analysis/testing/test-map.md`
 
 ### Phase 9: Agent docs audit
 
-- List all existing docs in `agents/docs/`, `agents/contexts/`, module `agents/`
+- List all existing docs in `agents/reference/docs/`, `agents/settings/contexts/`, module `agents/`
 - Check for outdated docs (reference deleted files/classes)
 - Identify undocumented areas
 - Check for stale roadmaps
@@ -341,7 +353,7 @@ After detecting **any** match, record the stack in the analysis output and selec
 
 ## Output format
 
-1. Structured analysis document in agents/analysis/
+1. Structured analysis document in agents/evidence/analysis/
 2. Tech stack inventory with versions and dependencies
 3. Architecture diagram or module map
 
@@ -355,7 +367,7 @@ After detecting **any** match, record the stack in the analysis output and selec
 
 - Full project analysis can take several minutes — warn the user about the time investment.
 - Don't analyze parts of the codebase that the user hasn't asked about — respect scope.
-- Analysis documents go in `agents/analysis/`, not in `.augment/`.
+- Analysis documents go in `agents/evidence/analysis/`, not in `.augment/`.
 
 ## Do NOT
 
@@ -364,5 +376,5 @@ After detecting **any** match, record the stack in the analysis output and selec
 - Do NOT commit or push.
 - Do NOT overwhelm the user — present findings incrementally, one phase at a time.
 - Do NOT analyze third-party code in `vendor/` or `node_modules/`.
-- Do NOT duplicate content that already exists in `agents/docs/` or `agents/contexts/` —
+- Do NOT duplicate content that already exists in `agents/reference/docs/` or `agents/settings/contexts/` —
   reference it instead. Analysis files complement existing docs, they don't replace them.

package/.agent-src/skills/project-docs/SKILL.md

@@ -1,8 +1,20 @@
 ---
 name: project-docs
-description: "Use when looking for project-specific documentation. Knows which docs exist in agents/docs/ and agents/contexts/ and maps work areas to relevant docs."
+description: "Use when looking for project-specific documentation. Knows which docs exist in agents/reference/docs/ and agents/settings/contexts/ and maps work areas to relevant docs."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-docs
@@ -55,7 +67,7 @@ agents/
 
 ## Domain Contexts
 
-If `agents/contexts/domain/` exists, it contains **business domain knowledge** — industry terms,
+If `agents/settings/contexts/domain/` exists, it contains **business domain knowledge** — industry terms,
 regulations, workflows, and edge cases that the agent needs to understand the problem space.
 
 **When to read domain contexts:**
@@ -64,28 +76,28 @@ regulations, workflows, and edge cases that the agent needs to understand the pr
 - When writing validations, business rules, or data models for a specific domain
 
 **How to find the right file:**
-- List `agents/contexts/domain/` and read files whose name matches the work area
+- List `agents/settings/contexts/domain/` and read files whose name matches the work area
 - Files prefixed with `job-` describe industry/profession knowledge
 - When in doubt, read all domain context files — they are short orientation docs
 
 ## How to Find Relevant Docs
 
-1. **List `agents/contexts/`** — read any context file whose name matches the work area.
-2. **List `agents/contexts/domain/`** — read domain knowledge files relevant to the business logic.
-3. **List `agents/docs/`** — read detail docs for the specific topic you're working on.
+1. **List `agents/settings/contexts/`** — read any context file whose name matches the work area.
+2. **List `agents/settings/contexts/domain/`** — read domain knowledge files relevant to the business logic.
+3. **List `agents/reference/docs/`** — read detail docs for the specific topic you're working on.
 4. **Check module docs** — if working in a module, also check:
    - `app/Modules/{Module}/agents/` — module-specific docs
-   - `app/Modules/{Module}/agents/contexts/` — module-specific contexts (if exists)
-   - `app/Modules/{Module}/agents/contexts/domain/` — module-specific domain knowledge (if exists)
+   - `app/Modules/{Module}/agents/settings/contexts/` — module-specific contexts (if exists)
+   - `app/Modules/{Module}/agents/settings/contexts/domain/` — module-specific domain knowledge (if exists)
 
 ### Reading order
 
 | Step | What | Why |
 |---|---|---|
-| 1 | `agents/contexts/*.md` | Quick orientation — big picture in ~100 lines |
-| 2 | `agents/contexts/domain/job-*.md` | Domain knowledge — business terms, rules, edge cases |
-| 3 | Module `agents/contexts/` | Module-specific contexts (if working in a module) |
-| 4 | `agents/docs/*.md` | Deep dive — code examples, conventions, patterns |
+| 1 | `agents/settings/contexts/*.md` | Quick orientation — big picture in ~100 lines |
+| 2 | `agents/settings/contexts/domain/job-*.md` | Domain knowledge — business terms, rules, edge cases |
+| 3 | Module `agents/settings/contexts/` | Module-specific contexts (if working in a module) |
+| 4 | `agents/reference/docs/*.md` | Deep dive — code examples, conventions, patterns |
 
 ### Matching work areas to docs
 
@@ -104,7 +116,7 @@ Do NOT hardcode a mapping — always **list the directory** and pick by relevanc
 - **Don't skip docs because you "know" the pattern** — project-specific conventions often differ
   from standard framework patterns.
 - **Update docs when you change conventions** — if your change introduces a new pattern or
-  deprecates an old one, update the relevant doc in `agents/docs/`.
+  deprecates an old one, update the relevant doc in `agents/reference/docs/`.
 
 ## Cross-References
 

package/.agent-src/skills/prompt-engineering-patterns/SKILL.md

@@ -4,6 +4,18 @@ description: "Use when designing production-LLM prompts — few-shot, chain-of-t
 source: package
 domain: product
 status: active
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # prompt-engineering-patterns
@@ -142,5 +154,5 @@ Production prompts handle their own failure cases:
 
 - Adopted from: `Microck/ordinary-claude-skills@8f5c83174f7aa683b4ddc7433150471983b93131:skills_all/prompt-engineering-patterns/SKILL.md` (MIT, © 2025 Microck) — restructured into a decision-framework shape; vendor `prompt_optimizer` Python snippets dropped (project-specific to Microck).
 - Cross-linked: [`prompt-optimizer`](../prompt-optimizer/SKILL.md), [`refine-prompt`](../refine-prompt/SKILL.md), [`mcp-builder`](../mcp-builder/SKILL.md), [`async-python-patterns`](../async-python-patterns/SKILL.md).
-- Provenance registry: `agents/contexts/skills-provenance.yml` (entry: `prompt-engineering-patterns`).
+- Provenance registry: `agents/settings/contexts/skills-provenance.yml` (entry: `prompt-engineering-patterns`).
 - Iron-Law floor: `verify-before-complete`, `skill-quality`, `non-destructive-by-default`.

package/.agent-src/skills/prompt-optimizer/SKILL.md

@@ -3,6 +3,18 @@ name: prompt-optimizer
 description: "Use when the user wants a prompt optimized for ChatGPT, Claude, Gemini, or another AI — 'make this prompt better', 'optimize for ChatGPT', 'rewrite my prompt' — even without saying 'optimize'."
 source: package
 domain: product
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # prompt-optimizer
@@ -130,4 +142,4 @@ Format per § Output format. Do **not** execute the optimized prompt yourself un
 
 - [`refine-prompt`](../refine-prompt/SKILL.md) — engine-inbound sibling; same `prompt_optimization` setting controls its mode
 - [`docs/guidelines/prompt-templates.md`](../../../docs/guidelines/prompt-templates.md) — 12-template catalogue cited from Develop step
-- AI Council session: `agents/council-responses/prompt-master-mini.json` (2026-05-17) — analysis behind template adoption and the 5-safe-dogma rejection <!-- council-ref-allowed: ADR decision trace -->
+- AI Council session: `agents/runtime/council/responses/prompt-master-mini.json` (2026-05-17) — analysis behind template adoption and the 5-safe-dogma rejection <!-- council-ref-allowed: ADR decision trace -->

package/.agent-src/skills/quality-tools/SKILL.md

@@ -8,8 +8,18 @@ execution:
   handler: shell
   allowed_tools: []
 recommended_for_user_types: [developer]
-
-
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # quality-tools

package/.agent-src/skills/react-native-setup/SKILL.md

@@ -3,6 +3,18 @@ name: react-native-setup
 description: "Use when setting up React Native or Expo dev environments — Xcode, Android Studio, CocoaPods, EAS, Metro, New Architecture — even when the user just says 'my RN build won't start'."
 source: package
 domain: devops
+workspaces:
+  - engineering
+packs:
+  - react
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # react-native-setup

package/.agent-src/skills/react-shadcn-ui/SKILL.md

@@ -3,6 +3,18 @@ name: react-shadcn-ui
 description: "Use when building React UI on shadcn/ui primitives + Tailwind — the apply/review/polish skill dispatched by `directives/ui/*` for the `react-shadcn` stack."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - react
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # react-shadcn-ui