@event4u/agent-config 9.7.0 → 9.9.0

package/docs/flows.md

@@ -1,67 +0,0 @@
-# Flows — the user-work journeys
-
-A **Flow** names a multi-command *user-work journey*, the connective tissue
-between the curated command surface and the day-to-day developer journey. It
-answers **"what am I trying to *do*?"** — not "which command do I type?".
-
-The layered model:
-
-```
-Profile → Pack → Flow → Command → Skill → Rule
-```
-
-The user-facing developer story is **discovery → implementation → review →
-delivery**. Each flow below lists its **entry commands** (the daily front
-doors), its **canonical path** (the typical command sequence), and the
-**skills** it composes end-to-end. Source of truth:
-[`src/flows/<flow>.yaml`](../src/flows/) (schema + lint:
-[`flow.schema.json`](../src/scripts/schemas/flow.schema.json),
-[`lint_flows.py`](../src/scripts/lint_flows.py); data-model in
-[`ADR-055`](decisions/ADR-055-flow-layer-data-model.md)).
-
-## 🔍 Discovery — *what should we build, and how*
-
-Explore, plan, estimate, refine, and investigate **before** building.
-
-- **Entry commands:** `/feature:plan` · `/bug-investigate` · `/research`
-- **Canonical path:** `/feature:explore` → `/feature:plan` → `/estimate-ticket` → `/refine-ticket`
-- **Skills:** `feature-planning` · `estimate-ticket` · `refine-ticket` · `project-analysis-core` · `validate-feature-fit`
-
-## 🔨 Implementation — *build it*
-
-Drive a prompt, ticket, or feature end-to-end through plan → implement → verify.
-
-- **Entry commands:** `/work` · `/implement-ticket` · `/feature:dev` · `/bug-fix`
-- **Canonical path:** `/work` → `/review changes` → `/fix quality` → `/commit`
-- **Skills:** `test-driven-development` · `code-review` · `systematic-debugging` · `git-workflow`
-
-## 🔎 Review — *check it*
-
-Self-review, judge, quality-fix, and threat-model a change before it ships.
-
-- **Entry commands:** `/review-changes` · `/judge`
-- **Canonical path:** `/review changes` → `/judge` → `/fix quality` → `/threat-model`
-- **Skills:** `code-review` · `adversarial-review` · `quality-tools` · `threat-modeling` · `receiving-code-review`
-
-## 🚢 Delivery — *ship it*
-
-Commit in logical chunks, open the PR, answer review comments, prepare the
-branch for review.
-
-- **Entry commands:** `/commit` · `/pr:create` · `/prepare-for-review`
-- **Canonical path:** `/commit` → `/pr:create` → `/fix:pr-comments`
-- **Skills:** `conventional-commits-writing` · `git-workflow` · `requesting-code-review`
-
-## Why `agent-admin` is not a flow
-
-`agent-admin` (memory · analytics · governance · config) describes **system
-administration**, not user *work*. The four flows above describe what a user
-*does*; `agent-admin` describes how the platform is *operated* — almost entirely
-skills plus a couple of state-queries. It stays out of the flow set by
-construction.
-
-## See also
-
-- [`profiles.md`](profiles.md) — the six entry profiles that select which packs (and so which flows) surface.
-- [`catalog.md`](catalog.md) — the full command / skill / rule / guideline surface.
-- [`src/flows/README.md`](../src/flows/README.md) — the flow schema and the source stubs.

package/docs/getting-started-by-role.md

@@ -1,190 +0,0 @@
-# Getting started — by role
-
-> Pick the entry that matches what you do day-to-day. Each section names the three skills you will reach for first and shows whether MCP (no terminal) or CLI (terminal) is the simpler install path for that role.
-
-`agent-config` ships 278 skills, 105 governed rules, and 190 commands. You do not need all of them. Each role below filters to the slice that pays back in week one; the rest stays available and shows up on demand when a task references it.
-
-> **Taglines at a glance →** [`docs/role-experiences.md`](role-experiences.md) — the one-line pitch per role experience, in one table.
-
-> **Quickstart for every role.** Run `npx -y @event4u/agent-config init` — the browser wizard auto-launches and walks you through role, ready-made setup, and identity. Headless install path lives at [`docs/wizard.md`](wizard.md#headless--ci--no-browser). The wizard writes `.agent-settings.yml`, `.augment/`, and `.claude/` atomically; nothing leaves your disk.
-
-> **Eval-gated messaging note.** Until `task bench --corpus non-dev` reports `selection_accuracy >= 0.60` (step-12 Phase 1 exit), this page is documentation, not marketing. The skills listed below are the candidates the corpus tests against; their description quality is what the eval validates.
-
-> **Deployment posture.** Single-user workspace today (one machine, one user — `npx @event4u/agent-config init`). Small team today (3–10 people) via shared `agents/overrides/` Git repo + shared NAS for knowledge — recipe: [`docs/deploy/small-team-recipe.md`](deploy/small-team-recipe.md). Organization mode (SSO · central policy · team context · internal connectors) is **not started** — tracked under [`agents/roadmaps/stubs/`](../agents/roadmaps/stubs/README.md) with explicit gating (recruited customer + funded audit + maintainer ADR). Rationale: [`docs/deploy/team-deployment-posture.md`](deploy/team-deployment-posture.md).
-
----
-
-## Creator (writer, marketer, indie content shop)
-
-> **Tailored role experience available →** [`agents/roles/content-creator/`](../agents/roles/content-creator/index.md) — three first tasks, priority-ordered skill shortlist, prompt scaffolds. Status `draft` until recruit-session 02 lands.
-
-**You want this if:** you draft blog posts, marketing emails, launch copy, or release announcements and want a writing assistant that holds a defined brand voice across surfaces. You need brand-voice discipline more than code-quality enforcement. You will spend most of your time in Claude Desktop / ChatGPT, not in a terminal.
-
-- [`voice-and-tone-design`](../dist/agent-src/skills/voice-and-tone-design/SKILL.md) — define and audit brand voice (voice attributes, tone-by-context matrix).
-- [`messaging-architecture`](../dist/agent-src/skills/messaging-architecture/SKILL.md) — primary message + supporting proofs + audience-by-message matrix.
-- [`editorial-calendar`](../dist/agent-src/skills/editorial-calendar/SKILL.md) — evergreen vs campaign vs reactive cadence across channels.
-
-### AI Video Pipeline
-
-Cinematic-blueprint approach: the agent expands your script into a 12-block scene plan, locks a character identity, then drives the rendering provider you have chosen. Provider-agnostic and dry-run-by-default.
-
-- [`/video:from-script`](../dist/agent-src/commands/video/from-script.md) — end-to-end pipeline: script → character-locked image → motion+audio prompt → provider render → stitched clip.
-- [`/video:storyboard`](../dist/agent-src/commands/video/storyboard.md) — expand a one-line idea into the 12-block Cinematic Scene Blueprint (provider-agnostic).
-- [`/video:scene`](../dist/agent-src/commands/video/scene.md) — render a single scene from an existing blueprint against the configured provider adapter.
-- [`/video:stitch`](../dist/agent-src/commands/video/stitch.md) — assemble rendered scenes into the final clip via ffmpeg.
-- [`character-consistency`](../dist/agent-src/skills/character-consistency/SKILL.md) — lock identity tokens (silhouette, palette, wardrobe, prop) so a character stays visually identical across scenes.
-
-`AIV_DRYRUN=true` is the mandatory default — no provider call, no spend until you opt in.
-
-**Worked example — one-line idea to stitched cut, four commands:**
-
-1. `/video:from-script "kurzes Werbevideo für ein Galabau-Projekt"` — agent expands the one-line idea into a 12-block blueprint, locks the character identity, and prints the provider-tuned prompt set.
-2. `/video:storyboard` — review the 12-block scene plan before any provider call; edit blocks inline (camera, lighting, blocking, motion) until the storyboard reads as intended.
-3. `/video:scene` — render one scene at a time against the configured provider adapter; iterate on the motion + audio prompt without paying for the full clip.
-4. `/video:stitch` — assemble the rendered scenes into the final clip via ffmpeg, with the character-lock JSON enforcing identity across cuts.
-
-**Try the first win →** [`pack-ai-video/FIRST_WIN.md`](../src/domains/ai-video/FIRST_WIN.md) — one-line idea to a provider-tuned motion prompt in ~12 minutes.
-
-> **What this is not:** the package does **not** host a video model. It orchestrates prompts against the provider you select (Veo, Kling, Sora, Runway, …). Trust level is set by the provider's adapter lifecycle tier — see [`provider-lifecycle-discipline`](../dist/agent-src/rules/provider-lifecycle-discipline.md). You pay the provider directly, the package never sees your API key.
-
-**Install path:** **MCP recommended.** Claude Desktop is the lowest-friction entry; no terminal required. See [`docs/mcp.md`](mcp.md). CLI install works too if you already use a code editor.
-
----
-
-## Founder (early-stage operator wearing every hat)
-
-**You want this if:** you switch between investor pitch, hiring decision, product spec, and unit-economics modeling in the same week. You need cross-domain skills that respect your time budget, not depth-first specialists. Decisions need to be defensible to a board.
-
-- [`runway-cognition`](../dist/agent-src/skills/runway-cognition/SKILL.md) — cash runway, burn shape, fundraise triggers, cut-vs-grow.
-- [`unit-economics-modeling`](../dist/agent-src/skills/unit-economics-modeling/SKILL.md) — CAC, LTV, payback, contribution margin per customer.
-- [`fundraising-narrative`](../dist/agent-src/skills/fundraising-narrative/SKILL.md) — why-now / why-us / why-this framing, market-size reasoning.
-
-**Try the first win →** [`pack-founder-strategy/FIRST_WIN.md`](../src/packs/founder-strategy/FIRST_WIN.md) — investor question reshaped into a defensible memo in ~10 minutes.
-
-**Install path:** **MCP for advisor work, CLI when you touch code.** Claude Desktop covers strategy / finance / narrative; CLI is needed only when you sit in the repo with the dev team.
-
----
-
-## Developer (the original audience)
-
-**You want this if:** you write code daily — Laravel, Symfony, Next.js, Node, or stack-agnostic — and want testing / quality / git / CI guardrails baked into the agent's behavior. You will use commands like `/work`, `/commit`, `/create-pr`, `/quality-fix` constantly.
-
-- [`laravel`](../dist/agent-src/skills/laravel/SKILL.md) — Laravel-flavored PHP (Eloquent, Artisan, FormRequests, jobs, policies). See [`docs/getting-started-laravel.md`](getting-started-laravel.md) for the deep dive.
-- [`nextjs-patterns`](../dist/agent-src/skills/nextjs-patterns/SKILL.md) — App Router, Server Components, Server Actions, caching.
-- [`quality-tools`](../dist/agent-src/skills/quality-tools/SKILL.md) — PHPStan, Rector, ECS error triage and fix loop.
-
-Cross-model review of the real diff (**team mode**, default off) is documented in [Getting Started § Team mode](getting-started.md#team-mode--cross-model-review-default-off).
-
-**Install path:** **CLI.** Run `npx @event4u/agent-config init --tools=claude-code,cursor` in the project root. MCP works too but loses git / file-system tooling that the IDE-integrated path gives you.
-
----
-
-## Consultant (advisor, freelance, fractional)
-
-> **Tailored role experience available →** [`agents/roles/consultant/`](../agents/roles/consultant/index.md) — three first tasks (client-brief refinement, investor memo, deck outline), priority-ordered skill shortlist. Status `draft` until recruit-session 03 lands.
-
-**You want this if:** you sell discovery, positioning, competitive analysis, or roadmap audits. Output is briefs and slide content for a client, not code. You need defensible methodology behind every deliverable.
-
-- [`discovery-interview`](../dist/agent-src/skills/discovery-interview/SKILL.md) — switch-event JTBD guides, bias audit, falsifiable hypothesis.
-- [`competitive-moat-analysis`](../dist/agent-src/skills/competitive-moat-analysis/SKILL.md) — moat reasoning, where-to-play / where-not-to-play.
-- [`stakeholder-tradeoff`](../dist/agent-src/skills/stakeholder-tradeoff/SKILL.md) — per-lens framing, trade-off matrix with cost per choice.
-
-**Install path:** **MCP recommended.** Most consulting work is doc + slide drafting; the terminal adds friction without payback. Switch to CLI only if you also write code for the client.
-
----
-
-## Sales rep (B2B individual contributor)
-
-> **Tailored role experience available →** [`agents/roles/sales/`](../agents/roles/sales/index.md) — three first tasks (answer customer · draft offer · prep discovery call), 5 named prompts, priority-ordered skill shortlist. Status `draft` until a sales-shaped recruit-session lands.
-
-**You want this if:** you sell — usually with the deal half in your head and half in scattered notes from the last three meetings. You spend your day answering customer questions, drafting offers, and prepping discovery calls under time pressure.
-
-- [`voice-and-tone-design`](../dist/agent-src/skills/voice-and-tone-design/SKILL.md) — lock the deal voice across buyer / procurement / exec sponsor.
-- [`customer-research`](../dist/agent-src/skills/customer-research/SKILL.md) — frame the buyer's likely concern from LinkedIn / website / inbound context.
-- [`competitive-positioning`](../dist/agent-src/skills/competitive-positioning/SKILL.md) — surface the ours-vs-theirs delta when the buyer names a competitor.
-
-**Install path:** **MCP recommended.** Claude Desktop opens, the package shows up as a tool, no terminal. See [`docs/mcp.md`](mcp.md).
-
----
-
-## Support agent (customer success / technical support)
-
-> **Tailored role experience available →** [`agents/roles/support/`](../agents/roles/support/index.md) — three first tasks (summarise ticket · draft reply · escalation analysis), 5 named prompts, priority-ordered skill shortlist. Status `draft` until a support-shaped recruit-session lands.
-
-**You want this if:** you answer tickets — usually under SLA, often as the only person on a thread that turned into eight back-and-forth messages over two weeks. You want an assistant that summarises threads before you reply and flags escalation risks early.
-
-- [`voc-extract`](../dist/agent-src/skills/voc-extract/SKILL.md) — pulls verbatim customer language from threads for downstream triage.
-- [`voice-and-tone-design`](../dist/agent-src/skills/voice-and-tone-design/SKILL.md) — lock the support voice so every customer thread reads as one team.
-- [`churn-prevention`](../dist/agent-src/skills/churn-prevention/SKILL.md) — when the escalation-risk analysis flags churn-signal language.
-
-**Install path:** **MCP recommended.** Support workflows live in the ticketing tool + chat; Claude Desktop is the natural home.
-
----
-
-## Team leader (engineering manager, function lead, fractional)
-
-> **Tailored role experience available →** [`agents/roles/leadership/`](../agents/roles/leadership/index.md) — three first tasks (weekly status · risk-analysis memo · decision record), 5 named prompts, priority-ordered skill shortlist. Status `draft` until a leadership-shaped recruit-session lands.
-
-**You want this if:** you run a team or a function. Each week you write the same three things: a status summary, a risk memo before a decision, and a decision record after. You want an assistant that turns fuzzy notes into structured documents — without inventing certainty you do not have.
-
-- [`decision-record`](../dist/agent-src/skills/decision-record/SKILL.md) — ADR-shaped output the team's record system already understands.
-- [`scenario-modeling`](../dist/agent-src/skills/scenario-modeling/SKILL.md) — best / base / downside frame when the risk memo demands a sweep.
-- [`stakeholder-tradeoff`](../dist/agent-src/skills/stakeholder-tradeoff/SKILL.md) — when the call has product / ops / exec sponsor pulling in different directions.
-
-**Install path:** **MCP recommended.** Leadership writing is doc-heavy; Claude Desktop is the natural home.
-
----
-
-## Galabau owner (Garten- und Landschaftsbau, small-business operator)
-
-> **Tailored role experience available →** [`agents/roles/galabau/`](../agents/roles/galabau/index.md) — three first tasks (offer drafting, customer-email reply, project-brief refinement), priority-ordered skill shortlist. Status `draft` until recruit-session 01 lands.
-
-**You want this if:** you run or co-run a small Garten-und-Landschaftsbau shop and draft customer offers, customer emails, and project briefs every week — usually after the on-site day is done. You want a writing assistant that knows your tone, holds it across customers, and turns a one-paragraph project sketch into a structured document you can send the next morning.
-
-- [`refine-prompt`](../dist/agent-src/skills/refine-prompt/SKILL.md) — tighten fuzzy customer briefs before any drafting so the agent does not invent scope.
-- [`voice-and-tone-design`](../dist/agent-src/skills/voice-and-tone-design/SKILL.md) — lock the shop tone so offers and emails read consistent across customers.
-- [`doc-coauthoring`](../dist/agent-src/skills/doc-coauthoring/SKILL.md) — section-by-section drafting for longer offers; never one giant generation.
-
-**Install path:** **MCP recommended.** Claude Desktop opens, the package shows up as a tool, no terminal required. See [`docs/mcp.md`](mcp.md). CLI install is the right path only if you also sit in this repo with code-shaped work.
-
----
-
-## Go-To-Market (sales, marketing ops, RevOps)
-
-**You want this if:** you own pipeline shape, forecast accuracy, launch sequencing, or post-launch comms. You need deal-level rigor (MEDDIC, exit criteria) and narrative skills (release comms, messaging) in the same agent.
-
-- [`pipeline-strategy`](../dist/agent-src/skills/pipeline-strategy/SKILL.md) — stage exit criteria, per-cell conversion, leak diagnosis.
-- [`deal-qualification-meddic`](../dist/agent-src/skills/deal-qualification-meddic/SKILL.md) — MEDDIC slots with evidence, inversion test, disqualification heuristic.
-- [`release-comms`](../dist/agent-src/skills/release-comms/SKILL.md) — value-not-feature framing, audience-segmented surfaces.
-
-Use the AI Video skills (see [Creator → AI Video Pipeline](#ai-video-pipeline)) when you need a launch asset, not a documentary — 8-second hero clips, social cutdowns, or feature-announcement teasers.
-
-**Try the first win →** [`pack-gtm-sales/FIRST_WIN.md`](../src/packs/gtm-sales/FIRST_WIN.md) — single deal to a MEDDIC scorecard with inversion test in ~7 minutes.
-
-**Install path:** **MCP recommended.** GTM artifacts are documents, decks, and Notion pages; Claude Desktop is the natural home.
-
----
-
-## Finance / Ops (CFO, controller, ops lead, founder-finance)
-
-**You want this if:** you build forecasts, model scenarios, and review data-handling for compliance. You need the agent to keep accounting / regulatory framing straight, not invent numbers.
-
-- [`forecasting`](../dist/agent-src/skills/forecasting/SKILL.md) — top-down vs bottom-up shape, confidence bands, retro-loop.
-- [`scenario-modeling`](../dist/agent-src/skills/scenario-modeling/SKILL.md) — base / upside / downside, three-statement modeling, sensitivity.
-- [`privacy-review`](../dist/agent-src/skills/privacy-review/SKILL.md) — GDPR / CCPA / HIPAA fit, cross-border transfer, breach-impact triage.
-
-Outputs are flagged for human-accountant review by default — the agent surfaces a trust banner on every forecast / scenario reply so downstream readers see the human-in-the-loop expectation. See [`finance-safety-floor`](../dist/agent-src/rules/finance-safety-floor.md).
-
-**Try the first win →** [`pack-finance-basic/FIRST_WIN.md`](../src/packs/finance-basic/FIRST_WIN.md) — runway question to a base/upside/downside narrative with trust banner in ~8 minutes. People-leaders running 1:1s: [`pack-ops-people/FIRST_WIN.md`](../src/packs/ops-people/FIRST_WIN.md) — 1:1 cadence audit to a concrete recommendation in ~6 minutes.
-
-**Install path:** **MCP recommended.** Finance / ops workflows are spreadsheet- and document-heavy; the CLI buys nothing here unless you also export models into a code repo.
-
----
-
-## What is the same regardless of role
-
-A short universal-skills allowlist (`git`, `refine-ticket`, `proofread`, `threat-model`, etc.) loads in every profile. The list will live at `docs/contracts/universal-skills.md` once step-12 Phase 3 lands; until then the package loads all skills and the host agent's semantic search picks what the prompt needs.
-
-## What this page does not promise
-
-This page lists **candidate** skill / role pairings. Whether each skill's `description:` is sharp enough for the agent to retrieve it without manual hint is exactly what `tests/eval/corpus-non-dev.yaml` tests. If a prompt in your role above falls flat, that is a skill-description bug — file an issue or open a PR with a sharper description, do not work around it by naming the skill manually.

package/docs/getting-started-laravel.md

@@ -1,72 +0,0 @@
-# Getting started — Laravel
-
-> Laravel is the deepest reference stack in the package today. This page collects the Laravel-specific guidance previously embedded in the root README. The relocation is part of step-12 Phase 2; the root README continues to surface Laravel under the dev role until the Phase 6 identity rewrite lands.
-
-## Why Laravel is the reference stack
-
-Laravel ships with the broadest, battle-tested skill coverage in the package — Pest, PHPStan, Rector, Eloquent, Livewire / Flux, Horizon, Pulse, Reverb, Pennant. That coverage exists because the package was originally extracted from a Laravel monorepo (Galawork). Symfony and Next.js are the second tier (`symfony-workflow`, `nextjs-patterns`); other stacks ship as they are battle-tested, not second-class.
-
-## Laravel-flavored skills
-
-| Skill | What it covers |
-|---|---|
-| [`laravel`](../dist/agent-src/skills/laravel/SKILL.md) | Eloquent, Artisan controllers, FormRequests, jobs, events, policies, providers |
-| [`eloquent`](../dist/agent-src/skills/eloquent/SKILL.md) | Models, relationships, scopes, query patterns |
-| [`artisan-commands`](../dist/agent-src/skills/artisan-commands/SKILL.md) | Console command structure, signatures, safe execution |
-| [`jobs-events`](../dist/agent-src/skills/jobs-events/SKILL.md) | Queued workflows, listeners, retry / failure handling |
-| [`laravel-validation`](../dist/agent-src/skills/laravel-validation/SKILL.md) | Form Requests, rules, custom rule objects |
-| [`laravel-middleware`](../dist/agent-src/skills/laravel-middleware/SKILL.md) | Request / response filtering, groups, priority |
-| [`laravel-notifications`](../dist/agent-src/skills/laravel-notifications/SKILL.md) | Mail, Slack, database, custom channels |
-| [`laravel-mail`](../dist/agent-src/skills/laravel-mail/SKILL.md) | Mailables, Markdown templates, queued sending |
-| [`laravel-scheduling`](../dist/agent-src/skills/laravel-scheduling/SKILL.md) | Cron expressions, overlap prevention, maintenance mode |
-| [`laravel-horizon`](../dist/agent-src/skills/laravel-horizon/SKILL.md) | Worker supervision, job metrics, balancing strategies |
-| [`laravel-pulse`](../dist/agent-src/skills/laravel-pulse/SKILL.md) | Real-time dashboard, custom recorders, performance insights |
-| [`laravel-reverb`](../dist/agent-src/skills/laravel-reverb/SKILL.md) | First-party WebSocket server, Pusher protocol compatibility |
-| [`laravel-pennant`](../dist/agent-src/skills/laravel-pennant/SKILL.md) | Feature flags, gradual rollouts, A/B testing |
-
-## Quality pipeline
-
-The Laravel quality pipeline runs PHPStan + Rector + ECS, with Pest as the test runner:
-
-- [`quality-tools`](../dist/agent-src/skills/quality-tools/SKILL.md) — PHPStan output triage, Rector apply, ECS fix.
-- [`pest-testing`](../dist/agent-src/skills/pest-testing/SKILL.md) — Pest test authoring patterns.
-- [`/fix quality`](../dist/agent-src/commands/fix/quality.md) — runs the full pipeline and fixes reported errors.
-
-## Docker and dev environment
-
-- [`docker`](../dist/agent-src/skills/docker/SKILL.md) — Dockerfile, compose, dual-container (fast + Xdebug) setup.
-- [`php-debugging`](../dist/agent-src/skills/php-debugging/SKILL.md) — Xdebug breakpoints, dual-container, header-based routing.
-- [`traefik`](../dist/agent-src/skills/traefik/SKILL.md) — local reverse proxy, real domains on 127.0.0.1, mkcert HTTPS.
-
-## Multi-tenancy and database
-
-- [`multi-tenancy`](../dist/agent-src/skills/multi-tenancy/SKILL.md) — customer DB switching, FQDN routing, tenant isolation.
-- [`database`](../dist/agent-src/skills/database/SKILL.md) — MariaDB / MySQL tuning, indexing, multi-connection patterns.
-- [`sql-writing`](../dist/agent-src/skills/sql-writing/SKILL.md) — raw SQL, parameterization, raw migrations.
-
-## Project analysis
-
-- [`project-analysis-laravel`](../dist/agent-src/skills/project-analysis-laravel/SKILL.md) — boot flow, request lifecycle, container usage, async systems, Laravel-specific failure patterns.
-
-## Install for a Laravel project
-
-```bash
-cd path/to/your/laravel/app
-npx @event4u/agent-config init --tools=claude-code,cursor
-```
-
-The installer detects `composer.json` + `artisan` + the Laravel framework dependency, enables stack-aware skills, and writes `.agent-settings.yml` with sensible defaults. The first `/onboard` run captures your name, preferred IDE, and cost profile.
-
-## Other PHP stacks
-
-| Stack | Coverage |
-|---|---|
-| **Symfony** | [`symfony-workflow`](../dist/agent-src/skills/symfony-workflow/SKILL.md) — DI, Doctrine, Messenger, voters, Twig; [`project-analysis-symfony`](../dist/agent-src/skills/project-analysis-symfony/SKILL.md) |
-| **Zend / Laminas** | [`project-analysis-zend-laminas`](../dist/agent-src/skills/project-analysis-zend-laminas/SKILL.md) + shared PHP coder / quality skills |
-| **Framework-free PHP** | [`php-coder`](../dist/agent-src/skills/php-coder/SKILL.md) — modern idioms, SOLID refactors, type hints without framework lock-in |
-
-## See also
-
-- [`docs/getting-started-by-role.md`](getting-started-by-role.md) — pick the entry that matches your day-to-day.
-- [`docs/getting-started.md`](getting-started.md) — generic three-step quickstart.
-- [`docs/installation.md`](installation.md) — detailed install variants (npx, curl, global npm).

package/docs/getting-started-local-stdio.md

@@ -1,77 +0,0 @@
-# Getting Started — local stdio MCP (end-users)
-
-> You installed (or want to install) `@event4u/agent-config` and want your
-> AI client to see its skills, commands, rules, and guidelines — **locally,
-> with no server to deploy and no account**. This page is for you. If you are
-> a *contributor* hacking on the package itself, see
-> [`mcp-server.md`](mcp-server.md) instead.
-
-The turnkey path is one command — **`agent-config mcp-server`** — wired into
-your MCP client. It serves the bundled content over stdio: **read-only**,
-fully local, offline, no Cloudflare account, no repo clone.
-
-## 1. Install
-
-```bash
-npm install -g @event4u/agent-config
-agent-config --version    # confirms the binary is on your PATH
-```
-
-No global install? Every config below also works with
-`"command": "npx", "args": ["-y", "@event4u/agent-config", "mcp-server"]`.
-
-## 2. Point your client at it
-
-Copy the snippet for your client from
-[`setup/mcp-client-config.md § Local stdio (turnkey)`](setup/mcp-client-config.md#local-stdio-turnkey--no-worker-no-account).
-The shape is the same everywhere — a **command**, not a URL:
-
-```json
-{
-  "mcpServers": {
-    "agent-config": { "command": "agent-config", "args": ["mcp-server"] }
-  }
-}
-```
-
-Claude Desktop, Claude Code, Cursor, and Zed snippets are all in that section.
-Restart / reload the client after editing its config.
-
-## 3. Verify
-
-Drive the server by hand — it speaks newline-delimited JSON-RPC on stdio:
-
-```bash
-printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' \
-  | agent-config mcp-server
-# → {"jsonrpc":"2.0","id":1,"result":{"serverInfo":{"name":"agent-config-mcp",…}}}
-```
-
-In your client you should then see `agent-config` listed, exposing:
-
-- **prompts** — skills (`skill.<name>`) and commands (`command.<name>`),
-- **resources** — rules (`rule://<name>`) and guidelines (`guideline://<name>`).
-
-## What you get — and what you don't
-
-- **Read-only content.** The local server serves the governance content as MCP
-  prompts + resources. It does **not** execute anything: `tools/list` is empty
-  and `tools/call` returns a `not_implemented` envelope. That is by design — see
-  [`decisions/ADR-085-mcp-stdio-end-user-distribution-shape.md`](decisions/ADR-085-mcp-stdio-end-user-distribution-shape.md).
-- **No network, no account.** Nothing leaves your machine. (If you instead want
-  a shared team endpoint reachable from anywhere, that is the *self-hosted
-  Worker* path — see [§ Two ways to connect](setup/mcp-client-config.md#two-ways-to-connect--pick-one).)
-
-## Troubleshooting
-
-| Symptom | Cause / fix |
-|---|---|
-| `command not found: agent-config` | The global install isn't on PATH. Use the `npx` form, or fix your npm global bin path. |
-| Client shows the server but no prompts/resources | The package is installed but unbuilt content is missing — reinstall `@event4u/agent-config`; the server refuses to serve an empty surface and prints why on **stderr**. |
-| Garbled / "invalid JSON" in the client | Something is writing to **stdout**. The server keeps stdout pure JSON-RPC and prints its readiness note on stderr — if you wrapped it in a script, make sure that wrapper doesn't echo to stdout. |
-
-## See also
-
-- [`setup/mcp-client-config.md`](setup/mcp-client-config.md) — all client snippets (local + remote).
-- [`decisions/ADR-085-mcp-stdio-end-user-distribution-shape.md`](decisions/ADR-085-mcp-stdio-end-user-distribution-shape.md) — why local stdio is read-only.
-- [`mcp-server.md`](mcp-server.md) — the contributor (clone + Python kernel) path.