opencastle 0.19.0 → 0.21.0

package/src/orchestrator/agents/release-manager.agent.md

@@ -6,7 +6,7 @@ tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'web/fetch', 'rea
 user-invocable: false
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Release Manager
 
@@ -21,7 +21,7 @@ You are a release manager responsible for pre-release verification, changelog ge
 
 ## Skills
 
-Resolve all skills (slots and direct) via [skill-matrix.json](.github/customizations/agents/skill-matrix.json).
+Resolve all skills (slots and direct) via [skill-matrix.json](.opencastle/agents/skill-matrix.json).
 
 ## Release Process
 

package/src/orchestrator/agents/researcher.agent.md

@@ -6,7 +6,7 @@ tools: ['search/codebase', 'search/textSearch', 'search/fileSearch', 'search/usa
 user-invocable: false
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Researcher
 
@@ -14,7 +14,7 @@ You are a codebase exploration specialist. Your job is to **find information, ma
 
 ## Skills
 
-Resolve all skills (slots and direct) via [skill-matrix.json](.github/customizations/agents/skill-matrix.json).
+Resolve all skills (slots and direct) via [skill-matrix.json](.opencastle/agents/skill-matrix.json).
 
 ## Critical Rules
 
@@ -69,8 +69,8 @@ Given a feature request, answer:
 Given a bug report, answer:
 - Where does the relevant code live? (entry points → data flow)
 - What does the git history show? (recent changes that might have caused it)
-- Are there related known issues in `.github/customizations/KNOWN-ISSUES.md`?
-- Are there related lessons in `.github/customizations/LESSONS-LEARNED.md`?
+- Are there related known issues in `.opencastle/KNOWN-ISSUES.md`?
+- Are there related lessons in `.opencastle/LESSONS-LEARNED.md`?
 - What test coverage exists for the affected area?
 
 ### 3. Pattern Audit

package/src/orchestrator/agents/reviewer.agent.md

@@ -6,7 +6,7 @@ user-invocable: false
 tools: [read/readFile, search/codebase, search/fileSearch, search/textSearch, search/listDirectory, read/problems]
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Reviewer
 

package/src/orchestrator/agents/security-expert.agent.md

@@ -6,7 +6,7 @@ tools: ["search/changes", "search/codebase", "edit/editFiles", "web/fetch", "vsc
 user-invocable: false
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Security Expert
 
@@ -24,7 +24,7 @@ You are a security expert specializing in authentication, authorization, securit
 
 ## Skills
 
-Resolve all skills (slots and direct) via [skill-matrix.json](.github/customizations/agents/skill-matrix.json).
+Resolve all skills (slots and direct) via [skill-matrix.json](.opencastle/agents/skill-matrix.json).
 
 ## Guidelines
 

package/src/orchestrator/agents/seo-specialist.agent.md

@@ -6,7 +6,7 @@ tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'web/fetch', 'rea
 user-invocable: false
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # SEO Specialist
 
@@ -21,7 +21,7 @@ You are an SEO specialist focused on technical SEO implementation — meta tags,
 
 ## Skills
 
-Resolve all skills (slots and direct) via [skill-matrix.json](.github/customizations/agents/skill-matrix.json).
+Resolve all skills (slots and direct) via [skill-matrix.json](.opencastle/agents/skill-matrix.json).
 
 ## Guidelines
 

package/src/orchestrator/agents/session-guard.agent.md

@@ -30,9 +30,9 @@ Run ALL checks. Report each as ✅ or ❌.
 
 ### 1. Delegation Records
 
-For each delegation in the session summary, verify a matching record exists in `.github/customizations/logs/events.ndjson` (type=delegation).
+For each delegation in the session summary, verify a matching record exists in `.opencastle/logs/events.ndjson` (type=delegation).
 
-**How:** `grep '"type":"delegation"' .github/customizations/logs/events.ndjson | tail -20` and match agent + task against the summary.
+**How:** `grep '"type":"delegation"' .opencastle/logs/events.ndjson | tail -20` and match agent + task against the summary.
 
 **Fix:** Load the **observability-logging** skill and run the delegation record command (includes a verify step).
 
@@ -40,29 +40,29 @@ Also verify each delegation record includes `session_id` (branch name). Records
 
 ### 2. Session Record
 
-Verify a session record exists in `.github/customizations/logs/events.ndjson` (type=session) for the current task.
+Verify a session record exists in `.opencastle/logs/events.ndjson` (type=session) for the current task.
 
-**How:** `grep '"type":"session"' .github/customizations/logs/events.ndjson | tail -5` and match task description.
+**How:** `grep '"type":"session"' .opencastle/logs/events.ndjson | tail -5` and match task description.
 
 **Fix:** Load the **observability-logging** skill and run the session record command (includes a verify step).
 
 ### 3. Lessons Captured
 
-If the session summary indicates retries occurred, verify new entries exist in `.github/customizations/LESSONS-LEARNED.md`.
+If the session summary indicates retries occurred, verify new entries exist in `.opencastle/LESSONS-LEARNED.md`.
 
-**How:** `grep -c "^### LES-" .github/customizations/LESSONS-LEARNED.md` — compare count with expected.
+**How:** `grep -c "^### LES-" .opencastle/LESSONS-LEARNED.md` — compare count with expected.
 
 ### 4. Discovered Issues Tracked
 
 If the session summary lists discovered issues, verify they appear in:
-- `.github/customizations/KNOWN-ISSUES.md`, OR
+- `.opencastle/KNOWN-ISSUES.md`, OR
 - A task tracker ticket referenced in the summary
 
 ### 5. Review & Panel Records
 
-If the session summary mentions fast reviews or panel reviews, verify matching records exist in `.github/customizations/logs/events.ndjson` (type=review and/or type=panel).
+If the session summary mentions fast reviews or panel reviews, verify matching records exist in `.opencastle/logs/events.ndjson` (type=review and/or type=panel).
 
-**How:** `grep '"type":"review"' .github/customizations/logs/events.ndjson | tail -10` and/or `grep '"type":"panel"' .github/customizations/logs/events.ndjson | tail -5`.
+**How:** `grep '"type":"review"' .opencastle/logs/events.ndjson | tail -10` and/or `grep '"type":"panel"' .opencastle/logs/events.ndjson | tail -5`.
 
 **Fix:** Load the **observability-logging** skill and run the review/panel record command as applicable (includes a verify step).
 
@@ -82,7 +82,7 @@ If the session involved running a convoy (check for `.opencastle/convoy.db` or r
 
 **Verify convoy tasks logged:**
 - Each completed convoy task should have a corresponding event in the NDJSON log
-- Check: `grep '"type":"session"' .github/customizations/logs/events.ndjson | tail -10`
+- Check: `grep '"type":"session"' .opencastle/logs/events.ndjson | tail -10`
 
 **Fix:** If convoy export is missing, the engine should have auto-exported. Manual export: run `opencastle run --status` to verify the convoy completed.
 

package/src/orchestrator/agents/team-lead.agent.md

@@ -28,7 +28,7 @@ handoffs:
     prompt: 'Use the resolve-pr-comments prompt to resolve the GitHub PR review comments on this PR:'
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Team Lead (OpenCastle)
 
@@ -55,6 +55,7 @@ Load on-demand skills **only when their phase is reached** — not upfront.
 | **agent-hooks** | Step 3 — delegation prompt templates for specialist agents |
 | **task-management** | Step 2 — tracker conventions, issue naming, labels, priorities |
 | **decomposition** | Step 2–3 — dependency resolution, delegation spec templates, prompt examples |
+| **agent-routing** | Step 2 — task-to-agent routing rules, multi-agent decomposition patterns, anti-patterns |
 | **orchestration-protocols** | Step 4+ — steering, background agents, parallel research, health-checks, escalation |
 | **context-map** | Step 2, if 5+ files affected — structured file impact maps |
 | **validation-gates** | Step 4 — deterministic checks, browser testing, regression |
@@ -89,6 +90,10 @@ Delegate via `runSubagent` (inline) or background sessions.
 
 > **⚠️ Always reference agents by their exact `name` when delegating.** Write "Use the Developer agent to..." or "Use the Researcher agent to..." in your delegation prompt. This ensures VS Code routes the sub-agent to the correct custom agent with its assigned model and tools. If you don't name the agent, the sub-agent inherits the Team Lead's Premium model — wasting expensive requests on Economy/Standard tasks.
 
+## Task-to-Agent Routing
+
+> **⛔ Developer is the LAST resort, not the default.** Load the **agent-routing** skill at Step 2 and scan its routing table before assigning any subtask. Only use Developer when no specialist matches. Always decompose multi-domain tasks across agent boundaries (e.g., code + copy = Developer + Copywriter).
+
 ## Delegation
 
 ### Sub-Agents (Inline) — `runSubagent`
@@ -104,7 +109,7 @@ When calling `runSubagent`, always specify which custom agent to use by name: *"
 
 **After each sub-agent returns**, log the delegation record before doing anything else (before review, before verification). This is a **⛔ hard gate** — do NOT proceed to review or any other action until the delegation is logged. Use the **observability-logging** skill's delegation record command (`--mechanism sub-agent`).
 
-> **`model` and `tier` must come from the agent registry** — not the Team Lead's own model. Look up the agent in [agent-registry.md](../customizations/agents/agent-registry.md) and use their assigned model and tier. For example, delegating to Developer → `"model":"claude-sonnet-4-6","tier":"quality"`, not the Team Lead's `claude-opus-4-6`.
+> **`model` and `tier` must come from the agent registry** — not the Team Lead's own model. Look up the agent in [agent-registry.md](../.opencastle/agents/agent-registry.md) and use their assigned model and tier. For example, delegating to Developer → `"model":"claude-sonnet-4-6","tier":"quality"`, not the Team Lead's `claude-opus-4-6`.
 
 ### Background Agents — Delegate Session
 
@@ -259,7 +264,7 @@ See [shared-delivery-phase.md](../agent-workflows/shared-delivery-phase.md) for
 
 1. Verify all issues Done or Cancelled
 2. Final build/lint/test across affected projects
-3. Update roadmap (`.github/customizations/project/roadmap.md`)
+3. Update roadmap (`.opencastle/project/roadmap.md`)
 4. Commit to feature branch with issue IDs — Team Lead creates the branch, sub-agents work on it directly, background agents use isolated worktrees
 5. Push and open PR (`GH_PAGER=cat gh pr create ...`). **Do NOT merge.**
 6. Link PR in tracker issue

package/src/orchestrator/agents/testing-expert.agent.md

@@ -6,7 +6,7 @@ tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'web/fetch', 'rea
 user-invocable: false
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Testing Expert
 
@@ -14,7 +14,7 @@ You are an expert tester who validates UI changes using browser automation and w
 
 ## Skills
 
-Resolve all skills (slots and direct) via [skill-matrix.json](.github/customizations/agents/skill-matrix.json).
+Resolve all skills (slots and direct) via [skill-matrix.json](.opencastle/agents/skill-matrix.json).
 
 ## Context Management
 

package/src/orchestrator/agents/ui-ux-expert.agent.md

@@ -6,7 +6,7 @@ tools: ['search/changes', 'search/codebase', 'edit/editFiles', 'web/fetch', 'vsc
 user-invocable: false
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # UI/UX Expert
 
@@ -20,7 +20,7 @@ You are an expert UI/UX developer specializing in building accessible, visually
 
 ## Skills
 
-Resolve all skills (slots and direct) via [skill-matrix.json](.github/customizations/agents/skill-matrix.json).
+Resolve all skills (slots and direct) via [skill-matrix.json](.opencastle/agents/skill-matrix.json).
 
 ## Guidelines
 

package/src/orchestrator/copilot-instructions.md

@@ -1,4 +1,4 @@
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Copilot Instructions
 

package/src/orchestrator/customizations/AGENT-PERFORMANCE.md

@@ -6,44 +6,44 @@ Tracks agent success rates across panel reviews and delegated tasks to inform mo
 ## Data Sources
 
 Performance data is collected automatically via NDJSON session logs:
-- **All events:** `.github/customizations/logs/events.ndjson` — unified log for all event types (sessions, delegations, reviews, panels, disputes), appended via `opencastle log`
+- **All events:** `.opencastle/logs/events.ndjson` — unified log for all event types (sessions, delegations, reviews, panels, disputes), appended via `opencastle log`
 - **Dashboard:** Run `npx opencastle dashboard` to visualize agent performance
 
 ## Quick Queries
 
 ```bash
 # Sessions per agent
-jq -r 'select(.type == "session") | .agent' .github/customizations/logs/events.ndjson | sort | uniq -c | sort -rn
+jq -r 'select(.type == "session") | .agent' .opencastle/logs/events.ndjson | sort | uniq -c | sort -rn
 
 # Success rate by agent
-jq -r 'select(.type == "session") | [.agent, .outcome] | @tsv' .github/customizations/logs/events.ndjson | sort | uniq -c
+jq -r 'select(.type == "session") | [.agent, .outcome] | @tsv' .opencastle/logs/events.ndjson | sort | uniq -c
 
 # Delegation tier distribution
-jq -r 'select(.type == "delegation") | .tier' .github/customizations/logs/events.ndjson | sort | uniq -c
+jq -r 'select(.type == "delegation") | .tier' .opencastle/logs/events.ndjson | sort | uniq -c
 
 # Failed delegations
-jq 'select(.type == "delegation" and .outcome == "failed")' .github/customizations/logs/events.ndjson
+jq 'select(.type == "delegation" and .outcome == "failed")' .opencastle/logs/events.ndjson
 ```
 
 ## Panel Review Performance
 
-Panel review data is collected automatically in `.github/customizations/logs/events.ndjson` with `type: "panel"` (appended by the panel runner after each review — see step 7 in the panel majority vote skill).
+Panel review data is collected automatically in `.opencastle/logs/events.ndjson` with `type: "panel"` (appended by the panel runner after each review — see step 7 in the panel majority vote skill).
 
 ```bash
 # Total panel reviews
-jq 'select(.type == "panel")' .github/customizations/logs/events.ndjson | wc -l
+jq 'select(.type == "panel")' .opencastle/logs/events.ndjson | wc -l
 
 # Pass vs block rate
-jq -r 'select(.type == "panel") | .verdict' .github/customizations/logs/events.ndjson | sort | uniq -c
+jq -r 'select(.type == "panel") | .verdict' .opencastle/logs/events.ndjson | sort | uniq -c
 
 # Reviews by panel key
-jq -r 'select(.type == "panel") | .panel_key' .github/customizations/logs/events.ndjson | sort | uniq -c | sort -rn
+jq -r 'select(.type == "panel") | .panel_key' .opencastle/logs/events.ndjson | sort | uniq -c | sort -rn
 
 # Reviews that required retries (attempt > 1)
-jq 'select(.type == "panel" and .attempt > 1)' .github/customizations/logs/events.ndjson
+jq 'select(.type == "panel" and .attempt > 1)' .opencastle/logs/events.ndjson
 
 # Average SHOULD-FIX items per review
-jq -s '[.[] | select(.type == "panel")] | if length > 0 then (map(.should_fix) | add) / length else 0 end' .github/customizations/logs/events.ndjson
+jq -s '[.[] | select(.type == "panel")] | if length > 0 then (map(.should_fix) | add) / length else 0 end' .opencastle/logs/events.ndjson
 ```
 
 ## Usage

package/src/orchestrator/customizations/DISPUTES.md

@@ -85,8 +85,8 @@ Which option the Team Lead recommends and why. Include specific next steps:
 #### Artifacts
 
 Links to evidence for human review:
-- Panel report: `.github/customizations/logs/panel/[panel-key].md`
-- Review log entries: `.github/customizations/logs/events.ndjson` (filter by `type: "review"` and issue)
+- Panel report: `.opencastle/logs/panel/[panel-key].md`
+- Review log entries: `.opencastle/logs/events.ndjson` (filter by `type: "review"` and issue)
 - Changed files: [list of files in the last attempt]
 - DLQ entry (if any): `DLQ-XXX`
 ```

package/src/orchestrator/customizations/README.md

@@ -6,7 +6,7 @@ Project-specific configuration for the AI agent framework. Everything in this fo
 
 Skills and instructions contain generic methodology (how to write migrations, how to test in a browser, how to run a panel review). This folder holds the concrete values those skills operate on — project IDs, table schemas, team UUIDs, endpoint inventories, and similar configuration that changes per project.
 
-Skills reference these files with relative links like `../../customizations/stack/api-config.md`, so agents automatically load project context when they load a skill.
+Skills reference these files with relative links like `../../.opencastle/stack/api-config.md`, so agents automatically load project context when they load a skill.
 
 ## Contents
 

package/src/orchestrator/customizations/logs/README.md

@@ -175,7 +175,7 @@ Run `opencastle log --help` for full options.
   "attempt": 1,
   "tracker_issue": "PRJ-57",
   "artifacts_count": 14,
-  "report_path": ".github/customizations/logs/panel/instruction-refactoring.md"
+  "report_path": ".opencastle/logs/panel/instruction-refactoring.md"
 }
 ```
 

package/src/orchestrator/customizations/project/docs-structure.md

@@ -4,19 +4,19 @@
 
 Project-specific documentation layout referenced by the `documentation-standards` skill.
 
-Documentation files live in the `.github/customizations/` directory alongside other project-specific configuration. Key documentation files:
+Documentation files live in the `.opencastle/` directory alongside other project-specific configuration. Key documentation files:
 
-- `.github/customizations/KNOWN-ISSUES.md` — Tracked issues, limitations, and accepted risks
-- `.github/customizations/project/roadmap.md` — Project roadmap and feature status
-- `.github/customizations/project/decisions.md` — Architecture Decision Records
-- `.github/customizations/LESSONS-LEARNED.md` — Agent knowledge base of retries and workarounds
+- `.opencastle/KNOWN-ISSUES.md` — Tracked issues, limitations, and accepted risks
+- `.opencastle/project/roadmap.md` — Project roadmap and feature status
+- `.opencastle/project/decisions.md` — Architecture Decision Records
+- `.opencastle/LESSONS-LEARNED.md` — Agent knowledge base of retries and workarounds
 
 ## Directory Tree
 
 <!-- Map your project's documentation directory here if one exists -->
 
 ```
-.github/customizations/
+.opencastle/
 ├── KNOWN-ISSUES.md            — Tracked issues and limitations
 ├── LESSONS-LEARNED.md         — Agent knowledge base
 └── project/

package/src/orchestrator/instructions/ai-optimization.instructions.md

@@ -3,7 +3,7 @@ description: 'AI assistant optimization patterns for efficient context usage and
 applyTo: '**'
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # AI Optimization
 

package/src/orchestrator/instructions/general.instructions.md

@@ -2,7 +2,7 @@
 applyTo: '**'
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Coding Standards
 
@@ -13,7 +13,7 @@ applyTo: '**'
 3. **Leave code better than you found it** — fix adjacent issues when the cost is low.
 4. **Fail visibly** — surface errors clearly; never swallow exceptions silently.
 5. **Verify, don't trust** — confirm outcomes with tools (tests, lint, build) rather than assuming success.
-6. **Log every session** — append observability records to `.github/customizations/logs/` before yielding to the user. No exceptions. Load the **observability-logging** skill for details.
+6. **Log every session** — append observability records to `.opencastle/logs/` before yielding to the user. No exceptions. Load the **observability-logging** skill for details.
 
 ## Instruction Priority Hierarchy
 
@@ -34,7 +34,7 @@ applyTo: '**'
 
 ## Technology Standards
 
-Load the corresponding skill for detailed conventions before writing code in that domain. These are **not optional**. See `.github/customizations/agents/skill-matrix.json` for the full domain-to-skill mapping.
+Load the corresponding skill for detailed conventions before writing code in that domain. These are **not optional**. See `.opencastle/agents/skill-matrix.json` for the full domain-to-skill mapping.
 
 | Domain | Skill |
 |--------|-------|
@@ -90,7 +90,7 @@ See [ai-optimization.instructions.md](ai-optimization.instructions.md) for batch
 
 ## Project Context
 
-For project-specific context (apps, libraries, tech stack, ports, URLs), see [project.instructions.md](../customizations/project.instructions.md).
+For project-specific context (apps, libraries, tech stack, ports, URLs), see [project.instructions.md](../.opencastle/project.instructions.md).
 
 ## Git Workflow
 
@@ -108,13 +108,13 @@ When you encounter a bug unrelated to the current task: check if already tracked
 > Do NOT respond to the user until you have appended the required log records.
 > A session without log records is a failed session — regardless of code quality.
 
-**Every agent MUST log every session** to `.github/customizations/logs/events.ndjson`. No exceptions. No threshold. No "too small to log." Load the **observability-logging** skill for CLI commands, record schemas, and the full logging checklist.
+**Every agent MUST log every session** to `.opencastle/logs/events.ndjson`. No exceptions. No threshold. No "too small to log." Load the **observability-logging** skill for CLI commands, record schemas, and the full logging checklist.
 
 ## Self-Improvement Protocol
 
 > **⛔ HARD GATE — Lessons are the team's collective memory. Skipping them causes repeated failures.**
 
-1. **Before starting work:** Read `.github/customizations/LESSONS-LEARNED.md` — apply relevant lessons proactively. This is NOT optional.
+1. **Before starting work:** Read `.opencastle/LESSONS-LEARNED.md` — apply relevant lessons proactively. This is NOT optional.
 2. **During execution:** If you retry with a different approach and it works, use the **self-improvement** skill to add a lesson immediately.
 3. **Update source files:** If the lesson reveals a gap in instruction/skill files, update those files too.
 

package/src/orchestrator/plugins/astro/SKILL.md

@@ -3,7 +3,7 @@ name: astro-framework
 description: "Astro framework best practices for content-driven sites, islands architecture, routing, integrations, and project structure. Use when creating or modifying Astro pages, layouts, components, or content collections."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Astro Framework
 

package/src/orchestrator/plugins/chrome-devtools/SKILL.md

@@ -3,11 +3,11 @@ name: browser-testing
 description: "Chrome DevTools MCP automation patterns for validating UI changes in real browsers. Use when performing E2E browser testing, validating visual changes, testing user interactions, or debugging UI issues with Chrome DevTools."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Browser Testing with Chrome DevTools MCP
 
-Generic browser testing methodology using Chrome DevTools MCP. For project-specific test app, selectors, suites, and breakpoint config, see [testing-config.md](../../customizations/stack/testing-config.md).
+Generic browser testing methodology using Chrome DevTools MCP. For project-specific test app, selectors, suites, and breakpoint config, see [testing-config.md](../../.opencastle/stack/testing-config.md).
 
 ## Purpose
 
@@ -21,7 +21,7 @@ After any UI change, validate in a real browser:
 
 ## Pre-Test Build Verification
 
-**CRITICAL: Always build before browser testing.** Testing stale code wastes time. See [testing-config.md](../../customizations/stack/testing-config.md) for the specific build and serve commands.
+**CRITICAL: Always build before browser testing.** Testing stale code wastes time. See [testing-config.md](../../.opencastle/stack/testing-config.md) for the specific build and serve commands.
 
 ## Chrome MCP Tools Reference
 
@@ -85,7 +85,7 @@ mcp_chrome-devtoo_performance_analyze_insight({ insightSetId: 'set_id', insightN
 
 ### 1. Setup
 
-Start the dev server (see [testing-config.md](../../customizations/stack/testing-config.md) for app and port).
+Start the dev server (see [testing-config.md](../../.opencastle/stack/testing-config.md) for app and port).
 
 ### 2. Initial State
 

package/src/orchestrator/plugins/contentful/SKILL.md

@@ -3,11 +3,11 @@ name: contentful-cms
 description: "Contentful CMS development patterns, GraphQL/REST API usage, content modeling, and migration best practices. Use when working with Contentful content types, entries, assets, or the Management API."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Contentful CMS
 
-Generic Contentful CMS development methodology. For project-specific configuration, content types, and API keys, see [cms-config.md](../../customizations/stack/cms-config.md).
+Generic Contentful CMS development methodology. For project-specific configuration, content types, and API keys, see [cms-config.md](../../.opencastle/stack/cms-config.md).
 
 ## Critical Development Rules
 

package/src/orchestrator/plugins/convex/SKILL.md

@@ -3,11 +3,11 @@ name: convex-database
 description: "Convex reactive database patterns, schema design, real-time queries, mutations, actions, and deployment best practices. Use when designing Convex schemas, writing queries/mutations, or managing the Convex backend."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Convex Database
 
-Generic Convex development methodology. For project-specific schema, functions, and deployment details, see [database-config.md](../../customizations/stack/database-config.md).
+Generic Convex development methodology. For project-specific schema, functions, and deployment details, see [database-config.md](../../.opencastle/stack/database-config.md).
 
 ## Critical Development Rules
 

package/src/orchestrator/plugins/cypress/SKILL.md

@@ -3,11 +3,11 @@ name: cypress-testing
 description: "Cypress E2E and component testing patterns, commands, selectors, and CI configuration. Use when writing E2E tests, component tests, or configuring Cypress in CI pipelines."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Cypress Testing
 
-Cypress-specific E2E and component testing patterns. For project-specific test configuration and breakpoints, see [testing-config.md](../../customizations/stack/testing-config.md).
+Cypress-specific E2E and component testing patterns. For project-specific test configuration and breakpoints, see [testing-config.md](../../.opencastle/stack/testing-config.md).
 
 ## Commands
 

package/src/orchestrator/plugins/figma/SKILL.md

@@ -3,7 +3,7 @@ name: figma-design
 description: "Figma design-to-code workflows, design token extraction, component inspection, and asset export. Use when translating Figma designs into code, extracting design tokens, or referencing component specs."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Figma Design
 

package/src/orchestrator/plugins/jira/SKILL.md

@@ -3,11 +3,11 @@ name: jira-management
 description: "Jira board conventions for tracking feature work — issue naming, labels, priorities, status workflow, and session continuity via Atlassian Rovo MCP. Use when decomposing features into tasks or resuming interrupted sessions."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Task Management with Jira
 
-Conventions for tracking feature work on Jira via the Atlassian Rovo MCP server. For project-specific project keys, workflow state IDs, and board configuration, see [tracker-config.md](../../customizations/project/tracker-config.md).
+Conventions for tracking feature work on Jira via the Atlassian Rovo MCP server. For project-specific project keys, workflow state IDs, and board configuration, see [tracker-config.md](../../.opencastle/project/tracker-config.md).
 
 ## Atlassian Rovo MCP Server
 
@@ -167,4 +167,4 @@ project = PROJ AND sprint in openSprints() ORDER BY priority DESC
 project = PROJ AND priority = Highest AND status != Done
 ```
 
-Replace `PROJ` with the actual project key from [tracker-config.md](../../customizations/project/tracker-config.md).
+Replace `PROJ` with the actual project key from [tracker-config.md](../../.opencastle/project/tracker-config.md).

package/src/orchestrator/plugins/linear/SKILL.md

@@ -3,11 +3,11 @@ name: linear-task-management
 description: "Linear board conventions for tracking feature work — issue naming, labels, priorities, status workflow, and session continuity. Use when decomposing features into tasks or resuming interrupted sessions."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Task Management with Linear
 
-Conventions for tracking feature work on the Linear board via MCP tools. For project-specific team ID, workflow state UUIDs, and label UUIDs, see [tracker-config.md](../../customizations/project/tracker-config.md).
+Conventions for tracking feature work on the Linear board via MCP tools. For project-specific team ID, workflow state UUIDs, and label UUIDs, see [tracker-config.md](../../.opencastle/project/tracker-config.md).
 
 ## Discovered Issues (Bug Tickets)
 

package/src/orchestrator/plugins/netlify/SKILL.md

@@ -3,11 +3,11 @@ name: netlify-deployment
 description: "Netlify deployment workflows, serverless functions, edge functions, environment management, and build configuration. Use when deploying to Netlify, writing serverless/edge functions, or troubleshooting builds."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Netlify Deployment
 
-Netlify-specific deployment patterns and conventions. For project-specific deployment architecture, environment variables, and key files, see [deployment-config.md](../../customizations/stack/deployment-config.md).
+Netlify-specific deployment patterns and conventions. For project-specific deployment architecture, environment variables, and key files, see [deployment-config.md](../../.opencastle/stack/deployment-config.md).
 
 ## Deployment Model
 

package/src/orchestrator/plugins/nextjs/SKILL.md

@@ -3,7 +3,7 @@ name: nextjs-framework
 description: "Next.js framework best practices covering App Router, server/client components, data fetching, caching, rendering strategies, middleware, configuration, and deployment. Use when creating or modifying Next.js pages, layouts, route handlers, Server Actions, or project configuration."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Next.js Framework
 

package/src/orchestrator/plugins/nx/SKILL.md

@@ -3,7 +3,7 @@ name: nx-workspace
 description: "NX monorepo commands, conventions, code generation, and task running patterns. Use when running builds, tests, linting, code generation, or any development commands."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # NX Workspace
 

package/src/orchestrator/plugins/playwright/SKILL.md

@@ -3,11 +3,11 @@ name: playwright-testing
 description: "Playwright E2E testing patterns, cross-browser configuration, page objects, and CI setup. Use when writing E2E tests, visual regression tests, or configuring Playwright in CI pipelines."
 ---
 
-<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .github/customizations/ directory instead. -->
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
 
 # Playwright Testing
 
-Playwright-specific E2E testing patterns. For project-specific test configuration and breakpoints, see [testing-config.md](../../customizations/stack/testing-config.md).
+Playwright-specific E2E testing patterns. For project-specific test configuration and breakpoints, see [testing-config.md](../../.opencastle/stack/testing-config.md).
 
 ## Commands