@event4u/agent-config 1.32.0 → 1.34.0

package/.agent-src/skills/architecture-review-lens/SKILL.md

@@ -0,0 +1,137 @@
+---
+name: architecture-review-lens
+description: "Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges."
+personas:
+  - backend-architect
+  - senior-engineer
+source: package
+domain: quality
+---
+
+# architecture-review-lens
+
+> Fifth judge in the `/review-changes` family. Reviews a diff for
+> **architectural fit**, not correctness, security, tests, or style.
+> Catches what the other four miss: layer violations, wrong
+> dependency direction, leaking abstractions, and broken cross-service
+> contracts. Sibling of [`judge-bug-hunter`](../judge-bug-hunter/SKILL.md)
+> et al. — never overlaps.
+
+## When to use
+
+- `/review-changes` dispatches its "architecture" slice to this skill.
+- A reviewer asks "does this belong here?", "should this be in
+  the domain layer?", or "is this leaking storage details?".
+- A diff adds a cross-service call, event, or contract.
+
+Do NOT use when:
+
+- The diff is documentation-only or a formatting-only change.
+- The concern is correctness — route to
+  [`judge-bug-hunter`](../judge-bug-hunter/SKILL.md).
+- The concern is security — route to
+  [`judge-security-auditor`](../judge-security-auditor/SKILL.md).
+- The concern is naming or DRY — route to
+  [`judge-code-quality`](../judge-code-quality/SKILL.md).
+- The concern is *whether to make* the architectural change — route
+  to [`decision-record`](../decision-record/SKILL.md) first.
+
+## Procedure
+
+### 1. Anchor on the system shape
+
+Read the codebase's stated architecture (ADRs, AGENTS.md, module
+docs). If no shape is documented, infer it from folder structure
+and surface the gap. You are judging the diff against **the stated
+shape**, not a fantasy ideal.
+
+### 2. Inspect each changed file for fit
+
+For every changed file, answer:
+
+| Question | Smell when "no" |
+|---|---|
+| Does this file live in the right layer? | Layer violation |
+| Are imports flowing in the allowed direction? | Inverted dependency |
+| Does this leak a storage / framework detail? | Leaky abstraction |
+| Is the public API of the module still the same? | Contract drift |
+| Does a cross-service call respect its contract? | Contract break |
+
+Each smell is a finding with a file:line citation.
+
+### 3. Check the seams
+
+Pay special attention to:
+
+- New public methods on existing classes.
+- New imports that cross module boundaries.
+- New events, queue messages, or HTTP calls.
+- Removed deprecation warnings or feature flags.
+
+Cross-module / cross-service additions are the highest-leverage
+findings — surface them even at low individual severity.
+
+### 4. Issue a verdict per the judge contract
+
+| Verdict | When |
+|---|---|
+| `apply` | No architectural concerns; diff fits the stated shape |
+| `revise` | Findings exist; diff lands after the listed fixes |
+| `reject` | Architectural shape itself must be reconsidered (rare) |
+
+`reject` requires citing which ADR or stated shape would need to
+change — never reject for taste.
+
+### 5. Validate the verdict
+
+Verify before emitting: every finding has a `file:line` citation and
+a smell label from the taxonomy; the verdict matches the worst
+finding (`revise` if any finding exists, `apply` only when none);
+`reject` cites the ADR or stated shape that would need to change.
+Ensure no finding restates a concern owned by another judge.
+
+## Output format
+
+The verdict block carries these ordered fields:
+
+1. `Judge:` — fixed value `architecture-review-lens`
+2. `Model:` and `Target:` — model id from `.agent-settings.yml` and diff range
+3. `Verdict:` — exactly one of `apply` / `revise` / `reject`
+4. `Issues:` — numbered list, each with `file:line`, smell label, suggested fix
+
+```
+Judge:  architecture-review-lens
+Model:  <model id from .agent-settings.yml>
+Target: <branch / diff range>
+
+Verdict: apply | revise | reject
+
+Issues:
+1. 🔴 <finding>           file:line
+   Smell: layer-violation | inverted-dep | leak | contract-drift | contract-break
+   Suggested fix: <one sentence>
+2. 🟡 ...
+3. 🟢 ...
+```
+
+## Gotcha
+
+- The stated shape may be wrong. If the diff has a sound reason to
+  break it, do NOT raise a finding — recommend an ADR via
+  `decision-record` and approve the diff.
+- "Could be split into more files" is style, not architecture; route
+  to `judge-code-quality`.
+- A finding with no file:line citation is a vibe; reject your own
+  finding before issuing it.
+
+## Do NOT
+
+- Do NOT review correctness, security, tests, or style — those are
+  other judges.
+- Do NOT issue `reject` without naming the ADR or stated shape that
+  would need to change.
+- Do NOT raise findings against the *current* architecture if the
+  diff did not introduce them; this is a diff-judge, not a
+  codebase-audit.
+- Do NOT merge findings with another judge's output — the user needs
+  to see which lens raised each one.

package/.agent-src/skills/artisan-commands/SKILL.md

@@ -2,6 +2,7 @@
 name: artisan-commands
 description: "Use when creating or modifying Artisan commands. Covers clear signatures, safe execution flow, helpful output, and project conventions for console tooling."
 source: package
+domain: engineering
 ---
 
 # artisan-commands

package/.agent-src/skills/async-python-patterns/SKILL.md

@@ -2,6 +2,7 @@
 name: async-python-patterns
 description: "Use when writing Python asyncio code — picking between gather / TaskGroup / wait, structured concurrency, timeouts, cancellation, sync-bridging — decision framework only, cookbook externalized."
 source: package
+domain: engineering
 status: active
 refresh_trigger: "Python ships a new structured-concurrency primitive (post-TaskGroup), OR ≥30% of cited upstream cookbook examples become deprecated, OR the cited libraries (aiohttp, httpx, anyio, trio) cut a major version with breaking async surface changes."
 sunset_criterion: "When `https://docs.python.org/3/library/asyncio.html` ships an in-tree decision framework AND consumer projects no longer cite this skill in PR reviews for two consecutive review cycles."

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

@@ -1,7 +1,11 @@
 ---
 name: authz-review
 description: "Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows."
+personas:
+  - security-engineer
+  - backend-architect
 source: package
+domain: quality
 ---
 
 # authz-review

package/.agent-src/skills/aws-infrastructure/SKILL.md

@@ -2,6 +2,7 @@
 name: aws-infrastructure
 description: "Use when working with AWS resources — ECS Fargate, ECR, EFS, Secrets Manager, gomplate templates, multi-env deployments — even when the user says 'deploy to staging' without naming AWS."
 source: package
+domain: devops
 ---
 
 # aws-infrastructure

package/.agent-src/skills/blade-ui/SKILL.md

@@ -2,6 +2,7 @@
 name: blade-ui
 description: "Use when the project's frontend stack is Blade — dispatched by `directives/ui/{apply,review,polish}.py`. Covers views, components, partials, layouts, and view logic."
 source: package
+domain: engineering
 ---
 
 # blade-ui

package/.agent-src/skills/blast-radius-analyzer/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: blast-radius-analyzer
 description: "Use BEFORE editing shared code — enumerates every call site, event consumer, queue worker, API client, migration, and test that a planned change will touch, with a file:line citation per dependency."
+personas:
+  - backend-architect
 source: package
+domain: discovery
 ---
 
 # blast-radius-analyzer

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

@@ -2,6 +2,7 @@
 name: bug-analyzer
 description: "Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs."
 source: package
+domain: discovery
 council_depth: deep
 ---
 

package/.agent-src/skills/check-refs/SKILL.md

@@ -2,6 +2,7 @@
 name: check-refs
 description: "Use when verifying cross-references between skills, rules, commands, guidelines, and context documents are not broken after edits, renames, or deletions."
 source: package
+domain: process
 execution:
   type: assisted
   handler: shell

package/.agent-src/skills/code-refactoring/SKILL.md

@@ -2,6 +2,7 @@
 name: code-refactoring
 description: "Use when the user says "refactor this", "rename class", or "move method". Safely refactors PHP code — finds all callers, updates downstream dependencies, and verifies with quality tools."
 source: package
+domain: engineering
 ---
 
 # refactorer

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

@@ -2,6 +2,7 @@
 name: code-review
 description: "Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards."
 source: package
+domain: quality
 ---
 
 # code-review

package/.agent-src/skills/command-routing/SKILL.md

@@ -2,6 +2,7 @@
 name: command-routing
 description: "Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns."
 source: package
+domain: process
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/command-writing/SKILL.md

@@ -2,6 +2,7 @@
 name: command-writing
 description: "Use when creating or editing a slash command in .agent-src.uncompressed/commands/ — frontmatter, numbered steps, safety gates — even when the user just says 'add a /command for X'."
 source: package
+domain: process
 ---
 
 <!-- cloud_safe: degrade -->

package/.agent-src/skills/composer-packages/SKILL.md

@@ -2,6 +2,7 @@
 name: composer-packages
 description: "Use when building or maintaining a Composer library — versioning, Laravel integration, autoloading, publishing to private registries — even when the user says 'release a new version'."
 source: package
+domain: engineering
 ---
 
 # composer-packages

package/.agent-src/skills/context-authoring/SKILL.md

@@ -2,6 +2,7 @@
 name: context-authoring
 description: "Use when filling in knowledge-layer context files — auth-model, tenant-boundaries, data-sensitivity, deployment-order, observability — interactive walkthrough that turns templates into reviewer fuel."
 source: package
+domain: process
 ---
 
 # context-authoring

package/.agent-src/skills/context-document/SKILL.md

@@ -2,6 +2,7 @@
 name: context-document
 description: "Use when the user says "create context", "document this area", or wants a structured snapshot of a codebase area for agent orientation."
 source: package
+domain: process
 ---
 
 # context

package/.agent-src/skills/conventional-commits-writing/SKILL.md

@@ -2,6 +2,7 @@
 name: conventional-commits-writing
 description: "Use when writing commit messages or squash-merge titles — `feat:`, `fix:`, `chore:`, scopes, breaking changes — even when the user just says 'commit this' without naming Conventional Commits."
 source: package
+domain: process
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/copilot-agents-optimization/SKILL.md

@@ -2,6 +2,7 @@
 name: copilot-agents-optimization
 description: "Use when optimizing AGENTS.md or copilot-instructions.md — deduplicates against .augment/ content, enforces line budgets, and focuses each file on its audience."
 source: package
+domain: process
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/copilot-config/SKILL.md

@@ -2,6 +2,7 @@
 name: copilot-config
 description: "Use when configuring GitHub Copilot — copilot-instructions.md, PR review patterns, output optimization — even when the user just says 'tune Copilot' or 'why is Copilot commenting on X'."
 source: package
+domain: process
 ---
 
 # Copilot Skill

package/.agent-src/skills/dashboard-design/SKILL.md

@@ -2,6 +2,7 @@
 name: dashboard-design
 description: "Use when designing monitoring dashboards — visualization selection, layout principles, observability strategies (RED/USE/Golden Signals), and data storytelling."
 source: package
+domain: devops
 ---
 
 # dashboard-design

package/.agent-src/skills/data-flow-mapper/SKILL.md

@@ -2,6 +2,7 @@
 name: data-flow-mapper
 description: "Use BEFORE editing code that touches user data — traces the value from entry → validation → transformation → storage → egress, every hop cited with file:line."
 source: package
+domain: discovery
 ---
 
 # data-flow-mapper

package/.agent-src/skills/database/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: database
 description: "Use when working with database architecture, MariaDB/MySQL tuning, indexing strategies, slow queries, or multi-connection patterns — even when the user just says 'this query is slow'."
+personas:
+  - eloquent-tamer
 source: package
+domain: engineering
 ---
 
 # database

package/.agent-src/skills/dcf-modeling/SKILL.md

@@ -4,6 +4,7 @@ description: "Wing-4 valuation cognition for a CFO / finance-partner. Use when a
 status: active
 tier: senior
 source: package
+domain: product
 ---
 
 # dcf-modeling

package/.agent-src/skills/decision-record/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: decision-record
+description: "Use when locking a trade-off, structuring an ADR draft, or wiring supersession chains — frames options · trade-offs · consequences before the file is written by `adr-create`."
+personas:
+  - senior-engineer
+  - critical-challenger
+  - product-owner
+source: package
+domain: process
+---
+
+# decision-record
+
+> Shape the **thinking** behind an architectural decision: list the
+> options, expose trade-offs, lock the chosen variant, and wire the
+> supersession chain. Hands off to [`adr-create`](../adr-create/SKILL.md)
+> for file mechanics (numbering, index, frontmatter). This skill does
+> not write the ADR file itself.
+
+## When to use
+
+- A team is about to commit to a non-trivial architectural choice and
+  wants the trade-offs on paper first.
+- Two engineers disagree on an approach — surface the options and
+  consequences before one wins by attrition.
+- A previous decision needs revisiting; the result must `supersede:`
+  the older ADR with explicit rationale.
+- German triggers: "lass uns das festzurren", "Trade-off-Matrix",
+  "welche Option ziehen wir?".
+
+Do NOT use when:
+
+- The file mechanics are the entire ask (numbering, regenerating the
+  index) — route directly to [`adr-create`](../adr-create/SKILL.md).
+- The decision is reversible and small (e.g. variable rename) — ADRs
+  are for choices that constrain future work.
+- The user wants a feature plan, not a decision — route to the
+  planning command instead.
+
+## Procedure
+
+### 1. State the decision in one sentence
+
+*"We need to decide `X` because `Y`."* If you cannot, the decision
+is not ripe — surface that and stop.
+
+### 2. Identify and enumerate options (≥ 2, usually ≤ 4)
+
+Each option gets:
+
+- **Name** — short, descriptive, never "option A / B / C".
+- **Sketch** — what it actually does in one paragraph.
+- **Cost / benefit** — three to five bullets per side, concrete.
+- **Reversibility** — easy / costly / one-way (Bezos two-way / one-way
+  door framing).
+
+Add an **explicit "do nothing"** option whenever it is plausible —
+forces the user to compare the change against the status quo.
+
+### 3. Build the trade-off matrix
+
+| Criterion | Option 1 | Option 2 | ... |
+|---|---|---|---|
+| Implementation cost | | | |
+| Operational cost | | | |
+| Reversibility | | | |
+| Blast radius | | | |
+| Time-to-value | | | |
+
+Pick criteria that *separate* the options. Criteria where every
+option scores the same are noise — drop them.
+
+### 4. Lock the choice + consequences
+
+Write:
+
+- **Decision:** *"We pick `<Option name>`."*
+- **Consequences:** what becomes true, what becomes harder, what
+  becomes impossible. At least one of each, or admit that nothing
+  becomes harder (rare; verify).
+
+### 5. Wire the supersession chain (if any)
+
+If this decision overrides a prior ADR:
+
+- Cite the prior ADR id and one-line summary.
+- State **what changed in the world** that justifies overriding —
+  not "we now think differently".
+- Hand off the `supersedes:` linkage to `adr-create`.
+
+### 6. Hand off to file mechanics
+
+Output the structured payload (below). The user — or
+`adr-create` — turns it into the file.
+
+## Output format
+
+```
+Decision: <one sentence>
+
+Options:
+  1. <name> — <sketch>
+       Pros: ...
+       Cons: ...
+       Reversibility: easy | costly | one-way
+  2. ...
+  N. Do nothing — <sketch>
+
+Trade-off matrix:
+  | Criterion | <opt 1> | <opt 2> | ... |
+  | ...
+
+Locked: <chosen option name>
+
+Consequences:
+  + <becomes true>
+  - <becomes harder>
+  ✗ <becomes impossible>
+
+Supersedes: <ADR-XYZ "title">  (if any)
+Trigger:    <what changed>     (if superseding)
+
+Next: /adr-create  with the payload above
+```
+
+## Gotcha
+
+- "We compared the options" is not a comparison. The matrix must
+  separate them on at least two criteria.
+- Pros without cons is advocacy, not analysis. If you cannot find
+  cons for the chosen option, you have not understood it yet.
+- A supersession with no "what changed in the world" is a vibe
+  pivot. Reject and ask.
+
+## Do NOT
+
+- Do NOT pick the option before listing them — the matrix is the
+  point, not the conclusion.
+- Do NOT write the ADR file from this skill — `adr-create` owns
+  filenames, numbering, and index regeneration.
+- Do NOT pad option counts to look thorough; two real options beat
+  four straw men.
+- Do NOT silently update an old ADR; supersession is explicit.

package/.agent-src/skills/deep-reading-analyst/SKILL.md

@@ -3,6 +3,7 @@ name: deep-reading-analyst
 description: "Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary."
 status: active
 source: package
+domain: discovery
 external_source: "https://github.com/ginobefun/deep-reading-analyst-skill/tree/26cd7dc9920e025d39751e396e707399022e49ef/src/deep-reading-analyst"
 refresh_trigger: "Upstream `ginobefun/deep-reading-analyst-skill` major rewrite (new framework added, dispatch table reshaped, or SHA pin invalidated by reference rename)."
 sunset_criterion: "Replace with a 50-line pointer skill if (a) all referenced modules are adopted as project-local guidelines (`docs/guidelines/agent-infra/{framework}.md`) AND (b) the dispatch logic moves into a project-native router."

package/.agent-src/skills/defense-in-depth/SKILL.md

@@ -2,6 +2,7 @@
 name: defense-in-depth
 description: "Use when validation needs entry, business-logic, environment, and instrumentation guards so a bad value cannot reach the failure point — turns a local bug fix into a structural one."
 source: package
+domain: quality
 ---
 
 # defense-in-depth

package/.agent-src/skills/dependency-upgrade/SKILL.md

@@ -2,6 +2,7 @@
 name: dependency-upgrade
 description: "Use when upgrading dependencies — "update Laravel", "bump PHP version", or "upgrade packages". Covers changelog review, breaking change detection, and verification."
 source: package
+domain: engineering
 ---
 
 # dependency-upgrade

package/.agent-src/skills/description-assist/SKILL.md

@@ -2,6 +2,7 @@
 name: description-assist
 description: "Use when polishing a skill/rule/command/guideline frontmatter description — pushier phrasing, trigger coverage, undertrigger audit — even if the user just says 'make this pushier'."
 source: package
+domain: process
 ---
 
 <!-- cloud_safe: degrade -->

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

@@ -2,6 +2,7 @@
 name: design-review
 description: "Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more."
 source: package
+domain: quality
 ---
 
 # design-review

package/.agent-src/skills/devcontainer/SKILL.md

@@ -2,6 +2,7 @@
 name: devcontainer
 description: "Use when configuring DevContainers or GitHub Codespaces — devcontainer.json, custom images, secrets, VS Code features — even when the user just says 'why does my Codespace not start'."
 source: package
+domain: devops
 ---
 
 # devcontainer

package/.agent-src/skills/developer-like-execution/SKILL.md

@@ -2,6 +2,7 @@
 name: developer-like-execution
 description: "Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without naming it."
 source: package
+domain: process
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/docker/SKILL.md

@@ -2,6 +2,7 @@
 name: docker
 description: "Use when working with Docker — Dockerfile edits, docker-compose services, containers, or the dual-container (fast + Xdebug) setup — even when the user just says 'my container won't start'."
 source: package
+domain: devops
 ---
 
 # docker

package/.agent-src/skills/dto-creator/SKILL.md

@@ -2,6 +2,7 @@
 name: dto-creator
 description: "Use when the user says "create a DTO", "new data transfer object", or needs to convert request/response data into a typed PHP class. Creates DTOs with SimpleDto base class and attribute mapping."
 source: package
+domain: engineering
 ---
 
 # dto-creator

package/.agent-src/skills/eloquent/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: eloquent
 description: "Use when writing Eloquent models, relationships, scopes, or queries via Model:: — 'fetch users with their orders'. NOT for PHPStan output, non-Eloquent services, or raw SQL questions."
+personas:
+  - eloquent-tamer
 source: package
+domain: engineering
 ---
 
 # eloquent

package/.agent-src/skills/error-handling-patterns/SKILL.md

@@ -2,6 +2,7 @@
 name: error-handling-patterns
 description: "Use when picking a failure-reporting strategy — exceptions vs Result types, recoverable vs not, retry / circuit-breaker / graceful degradation — decision framework only, catalogues externalized."
 source: package
+domain: engineering
 status: active
 refresh_trigger: "≥30% of cited upstream pattern catalogues become deprecated, OR a new top-2 ecosystem (Python/JS/PHP/Go/Rust) ships a paradigm-shifting standard error model"
 sunset_criterion: "When the upstream framework docs (Laravel, FastAPI, Express, Axum, Effect-TS) all carry an equivalent in-tree decision framework AND consumer projects no longer cite this skill in PR reviews for two consecutive review cycles."

package/.agent-src/skills/estimate-ticket/SKILL.md

@@ -9,6 +9,7 @@ personas:
   - critical-challenger
   - ai-agent
 source: package
+domain: product
 execution:
   type: assisted
   handler: internal

package/.agent-src/skills/existing-ui-audit/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: existing-ui-audit
 description: "Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set."
+personas:
+  - frontend-engineer
 source: package
+domain: discovery
 ---
 
 # existing-ui-audit

package/.agent-src/skills/fe-design/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: fe-design
 description: "Reference for frontend-design heuristics — component architecture, layout patterns, form/table design, responsive strategy, a11y, UX principles. Stack-agnostic; cited by directives/ui/design.py."
+personas:
+  - frontend-engineer
 source: package
+domain: engineering
 ---
 
 # Frontend Design Skill (Reference)
@@ -200,7 +203,7 @@ Step indicator (1 — 2 — 3)
 
 When `directives/ui/design.py` (or any caller) cites this skill:
 
-1. **Confirm the audit ran first** — `state.ui_audit` from [`existing-ui-audit`](../existing-ui-audit/SKILL.md) is mandatory. Stop and request the audit if missing.
+1. **Inspect `state.ui_audit` first** — review the audit produced by [`existing-ui-audit`](../existing-ui-audit/SKILL.md); it is mandatory. Stop and request the audit if missing.
 2. **Pick the smallest matching section** — Component Architecture, Form Design, Table Design, Responsive Strategy, Accessibility, or UX Principles. Cite by H2/H3 heading, never paste the whole skill.
 3. **Defer to audit findings** — when the audit pins a project pattern (token, primitive, layout convention), use it. The heuristics here are fallbacks for gaps, not overrides.
 4. **Defer to the stack apply skill** — Blade vs. Livewire vs. Flux vs. React-shadcn choices come from the dispatched impl skill, never from this reference.

package/.agent-src/skills/feature-planning/SKILL.md

@@ -2,6 +2,7 @@
 name: feature-planning
 description: "Use when the user says "plan a feature", "brainstorm", "explore this idea", or wants to go from idea to structured plan and roadmap."
 source: package
+domain: product
 ---
 
 # feature-planning

package/.agent-src/skills/file-editor/SKILL.md

@@ -2,6 +2,7 @@
 name: file-editor
 description: "Use when opening edited files in the user's IDE. Reads settings from .agent-settings.yml to determine IDE and whether auto-open is enabled."
 source: package
+domain: process
 execution:
   type: assisted
   handler: shell