opencastle 0.1.0 → 0.2.0

package/src/orchestrator/prompts/brainstorm.prompt.md

@@ -3,6 +3,8 @@ description: 'Collaborative brainstorm to explore requirements, approaches, and
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Brainstorm
 
 You are the Team Lead. Before planning or writing any code, run a structured brainstorm to explore the request described below. The goal is to **surface assumptions, alternative approaches, and trade-offs** before locking in a plan.

package/src/orchestrator/prompts/bug-fix.prompt.md

@@ -3,6 +3,8 @@ description: 'Investigate and fix a reported bug with proper triage, root cause
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Fix Bug
 
 You are the Team Lead. Investigate and fix the bug described below. Bugs are real defects that affect users — treat them seriously with proper triage, tracking, and verification.

package/src/orchestrator/prompts/create-skill.prompt.md

@@ -3,6 +3,8 @@ description: 'Scaffold a new skill directory with proper frontmatter, structure,
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Create Skill
 
 Scaffold a new skill for the AI agent configuration. Skills encode domain-specific knowledge that agents load on demand.

package/src/orchestrator/prompts/generate-task-spec.prompt.md

@@ -3,6 +3,8 @@ description: 'Generate a valid opencastle.tasks.yml spec file for autonomous ove
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Generate Task Spec for Autonomous Run
 
 You are the Team Lead. The user wants to run `opencastle run` to execute a batch of tasks autonomously (e.g., overnight). Your job is to produce a valid `opencastle.tasks.yml` file they can feed to the CLI.

package/src/orchestrator/prompts/implement-feature.prompt.md

@@ -3,6 +3,8 @@ description: 'Instruct the Team Lead to implement a specific task from the post-
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Implement Roadmap Task
 
 You are the Team Lead. Implement the roadmap task described below following this strict workflow. The task comes from `docs/ROADMAP-POST-MVP.md`.

package/src/orchestrator/prompts/metrics-report.prompt.md

@@ -3,6 +3,8 @@ description: 'Collect and report metrics from agent logs, GitHub PRs, Linear iss
 agent: Researcher
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Metrics Report
 
 Generate a comprehensive metrics dashboard from all project data sources.

package/src/orchestrator/prompts/quick-refinement.prompt.md

@@ -3,6 +3,8 @@ description: 'Handle follow-up refinements after a roadmap task — bug fixes, U
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Follow-Up Refinement
 
 You are the Team Lead. Handle the follow-up refinement described below. This is a **post-task adjustment** — a bug fix, UI tweak, or polish item that came up after reviewing a completed roadmap task. It does NOT require Linear tracking.

package/src/orchestrator/prompts/resolve-pr-comments.prompt.md

@@ -3,6 +3,8 @@ description: 'Resolve GitHub PR review comments by reading them, grouping by fil
 agent: Team Lead
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Resolve PR Comments
 
 You are the Team Lead. A pull request has review comments that need to be resolved. Read the comments, group them by file, and delegate fixes efficiently.

package/src/orchestrator/skills/accessibility-standards/SKILL.md

@@ -3,6 +3,8 @@ name: accessibility-standards
 description: "WCAG 2.2 Level AA accessibility patterns for React/HTML/CSS. Use when creating or modifying UI components, forms, navigation, tables, images, or any user-facing elements. Covers keyboard navigation, screen reader semantics, low vision contrast, voice access, and inclusive language."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Accessibility Standards
 
 Code must conform to [WCAG 2.2 Level AA](https://www.w3.org/TR/WCAG22/). Go beyond minimal conformance wherever possible.

package/src/orchestrator/skills/agent-hooks/SKILL.md

@@ -3,6 +3,8 @@ name: agent-hooks
 description: "Lifecycle hooks for AI agent sessions — reusable actions that run at specific points (session start, session end, pre-delegation, post-delegation). Defines what to do at each lifecycle event so agents behave consistently."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Agent Lifecycle Hooks
 
 Hooks are **standardized actions** that agents execute at specific points during their lifecycle. They enforce consistency across sessions and prevent common oversights (missing lessons, forgotten checkpoints, untracked issues).

package/src/orchestrator/skills/agent-memory/SKILL.md

@@ -3,6 +3,8 @@ name: agent-memory
 description: "Agent expertise tracking and cross-session knowledge graph. Use when delegating tasks to track agent strengths/weaknesses, or when building context about file relationships and patterns."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Agent Memory Protocol
 
 ## Purpose

package/src/orchestrator/skills/api-patterns/SKILL.md

@@ -3,6 +3,8 @@ name: api-patterns
 description: "API design patterns for route handlers, Server Actions, Zod validation, and external API integration. Use when creating API routes, Server Actions, or integrating external services."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # API Patterns
 
 Generic API design patterns for Next.js App Router projects. For project-specific endpoints, actions, and external API inventory, see [api-config.md](../../customizations/stack/api-config.md).

package/src/orchestrator/skills/browser-testing/SKILL.md

@@ -3,6 +3,8 @@ 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 customizations/ 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).
@@ -123,48 +125,34 @@ mcp_chrome-devtoo_list_console_messages()
 
 ### 6. Responsive Breakpoint Testing (MANDATORY)
 
-**Every UI change MUST be tested at all three breakpoints.** Do not test at desktop only — most layout bugs surface at mobile or tablet widths. See [testing-config.md](../../customizations/stack/testing-config.md) for project-specific breakpoint values.
+**Every UI change MUST be tested at all responsive breakpoints.** Do not test at desktop only — most layout bugs surface at smaller viewports. Define your breakpoints in your project's testing config (e.g., `testing-config.md`).
 
 #### How to Resize
 
 ```javascript
-// Mobile (iPhone-like)
-mcp_chrome-devtoo_resize_page({ width: 375, height: 812 })
-
-// Tablet (iPad-like)
-mcp_chrome-devtoo_resize_page({ width: 768, height: 1024 })
-
-// Desktop (standard)
-mcp_chrome-devtoo_resize_page({ width: 1440, height: 900 })
+// Example breakpoints — adjust to your project's testing config
+mcp_chrome-devtoo_resize_page({ width: 375, height: 812 })   // Mobile
+mcp_chrome-devtoo_resize_page({ width: 768, height: 1024 })  // Tablet
+mcp_chrome-devtoo_resize_page({ width: 1440, height: 900 })  // Desktop
 ```
 
 #### Per-Breakpoint Verification
 
-At **each** viewport size, verify:
+#### Per-Breakpoint Verification
 
-**Mobile (375 x 812):**
-- [ ] Sidebar/filter panel hidden — accessible via drawer/hamburger
-- [ ] Cards stack vertically, no horizontal overflow
-- [ ] Text truncates or wraps cleanly — no overflow or overlap
-- [ ] Touch targets >= 44px
-- [ ] Badges, tags, and pills wrap without horizontal scroll
-- [ ] Map/list toggle works
+At **each** breakpoint, check:
 
-**Tablet (768 x 1024):**
-- [ ] Layout adapts — may show 2-column grid or collapsed sidebar
-- [ ] Interactive elements have adequate spacing
+- [ ] Layout adapts correctly — no horizontal overflow
+- [ ] Text truncates or wraps cleanly — no overlap
+- [ ] Interactive elements have adequate spacing and touch targets
+- [ ] Navigation and panels collapse/expand as expected
 - [ ] Images and cards resize proportionally
 
-**Desktop (1440 x 900):**
-- [ ] Full layout visible — sidebar + content columns
-- [ ] Filter sidebar, content area, and any panels properly aligned
-- [ ] No excessive whitespace or stretched elements
-
 #### Responsive Testing Anti-Patterns
 
 | Anti-Pattern | Correct Approach |
 |---|---|
-| Testing only at desktop width | Test at all 3 breakpoints (Mobile -> Tablet -> Desktop) |
+| Testing only at desktop width | Test at all project-defined breakpoints |
 | Skipping resize because "it uses Tailwind" | Tailwind classes can be wrong — always verify visually |
 | Only checking layout, not interactions | Test filter drawers, dropdowns, and modals at each size |
 | Taking 3 screenshots (one per breakpoint) | Use `evaluate_script()` to check layout; save screenshots for failures |

package/src/orchestrator/skills/code-commenting/SKILL.md

@@ -3,6 +3,8 @@ name: code-commenting
 description: "Guidelines for writing self-explanatory code with minimal comments. Covers when to comment (WHY not WHAT), anti-patterns to avoid, annotation tags, and public API documentation. Use when writing or reviewing code comments."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Self-explanatory Code Commenting
 
 ## Core Principle

package/src/orchestrator/skills/contentful-cms/SKILL.md

@@ -3,6 +3,8 @@ 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 customizations/ 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).

package/src/orchestrator/skills/context-map/SKILL.md

@@ -3,6 +3,8 @@ name: context-map
 description: "Generate a structured file impact map before making changes. Identifies all files that will be affected, their relationships, and cascade effects — improving file partitioning for parallel work and reducing unexpected side effects."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Skill: Context Map
 
 Generate a structured **file impact map** before any code changes begin. This map identifies all files that will be touched, their relationships, and cascade effects — directly improving the Team Lead's file partitioning for parallel agents.

package/src/orchestrator/skills/convex-database/SKILL.md

@@ -3,6 +3,8 @@ 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 customizations/ 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).

package/src/orchestrator/skills/data-engineering/SKILL.md

@@ -3,6 +3,8 @@ name: data-engineering
 description: "Data pipeline ETL workflows, web scraping with Puppeteer, NDJSON processing, and CMS data import. Use when building scrapers, processing data, running CLI tools, or importing to a CMS."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Data Engineering
 
 Generic data pipeline patterns and scraping methodology. For project-specific pipeline architecture, sources, CLI commands, and data status, see [data-pipeline-config.md](../../customizations/stack/data-pipeline-config.md).

package/src/orchestrator/skills/deployment-infrastructure/SKILL.md

@@ -3,6 +3,8 @@ name: deployment-infrastructure
 description: "Deployment architecture, environment variables, cron jobs, security headers, and caching patterns. Use when configuring deployments, managing environment variables, setting up cron jobs, or troubleshooting build/deployment issues."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Deployment Infrastructure
 
 All deployment configuration is project-specific. See [deployment-config.md](../../customizations/stack/deployment-config.md) for the full architecture, environment variables, cron jobs, caching headers, and key files.

package/src/orchestrator/skills/documentation-standards/SKILL.md

@@ -3,6 +3,8 @@ name: documentation-standards
 description: "Documentation templates, structure, and standards for project docs, roadmaps, ADRs, and known issues. Use when writing or updating documentation files."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Documentation Standards
 
 Generic documentation templates and writing standards. For project-specific directory structure and practices, see [docs-structure.md](../../customizations/project/docs-structure.md).

package/src/orchestrator/skills/fast-review/SKILL.md

@@ -1,3 +1,5 @@
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 ````skill
 ---
 name: fast-review

package/src/orchestrator/skills/frontend-design/SKILL.md

@@ -4,6 +4,8 @@ description: "Create distinctive, production-grade frontend interfaces with high
 license: Complete terms in LICENSE.txt
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
 
 The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.

package/src/orchestrator/skills/jira-management/SKILL.md

@@ -3,6 +3,8 @@ 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 customizations/ 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 [jira-config.md](../../customizations/project/jira-config.md).

package/src/orchestrator/skills/memory-merger/SKILL.md

@@ -3,6 +3,8 @@ name: memory-merger
 description: "Protocol for graduating mature lessons from LESSONS-LEARNED.md into permanent instruction and skill files. Closes the self-improvement loop by codifying validated knowledge at the source level."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Skill: Memory Merger
 
 This skill automates the final step of the self-improvement cycle: promoting validated lessons into the instruction and skill files where they have structural, permanent impact.

package/src/orchestrator/skills/nextjs-patterns/SKILL.md

@@ -3,6 +3,8 @@ name: nextjs-patterns
 description: "Next.js App Router best practices for server/client components, routing, API routes, and project structure. Use when creating or modifying Next.js pages, layouts, route handlers, or Server Actions."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Next.js Patterns (2025)
 
 ## Project Structure

package/src/orchestrator/skills/nx-workspace/SKILL.md

@@ -3,6 +3,8 @@ 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 customizations/ directory instead. -->
+
 # NX Workspace
 
 ## Commands

package/src/orchestrator/skills/panel-majority-vote/SKILL.md

@@ -3,6 +3,8 @@ name: panel-majority-vote
 description: "Run 3 isolated reviewer sub-agents against the same question and decide PASS/BLOCK by majority vote (2/3 wins). Use when deterministic verification is insufficient."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Skill: Panel majority vote (3 reviewers)
 
 Use this skill when deterministic verification is unavailable and you need a panel to decide PASS/BLOCK for a single question against a declared artifact scope.

package/src/orchestrator/skills/panel-majority-vote/panel-report.template.md

@@ -1,3 +1,5 @@
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Panel Report
 
 ## Context

package/src/orchestrator/skills/performance-optimization/SKILL.md

@@ -3,6 +3,8 @@ name: performance-optimization
 description: "Frontend and backend performance optimization patterns including rendering, asset optimization, JavaScript performance, caching, profiling, and code review checklist. Use when optimizing components, reviewing code for performance, or analyzing bundle size and Core Web Vitals."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Performance Optimization
 
 ## General Principles

package/src/orchestrator/skills/react-development/SKILL.md

@@ -3,6 +3,8 @@ name: react-development
 description: "React development standards for functional components, hooks, TypeScript integration, state management, styling with CSS Modules/Sass, and testing patterns. Use when creating or modifying React components, custom hooks, or component tests."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # React Development Standards
 
 Modern React patterns following the official React documentation at https://react.dev.

package/src/orchestrator/skills/sanity-cms/SKILL.md

@@ -3,6 +3,8 @@ name: sanity-cms
 description: "Sanity CMS development rules, GROQ query patterns, and content management best practices. Use when working with Sanity schemas, writing GROQ queries, modifying content models, or managing CMS configuration."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Sanity CMS
 
 Generic Sanity CMS development methodology. For project-specific configuration, schemas, plugins, document types, and GROQ examples, see [sanity-config.md](../../customizations/stack/sanity-config.md).

package/src/orchestrator/skills/security-hardening/SKILL.md

@@ -3,6 +3,8 @@ name: security-hardening
 description: "Security architecture including authentication, authorization, RLS policies, security headers, CSP, input validation, API security, and OAuth patterns. Use when implementing auth flows, writing RLS policies, configuring security headers, validating inputs, or auditing security."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Security Hardening
 
 ## Security Architecture

package/src/orchestrator/skills/self-improvement/SKILL.md

@@ -3,6 +3,8 @@ name: self-improvement
 description: "Protocol for reading and updating the lessons-learned knowledge base. MUST be followed by ALL agents — read lessons before work, write lessons after retries. This makes the agent team self-improving across sessions."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Self-Improvement Protocol
 
 This skill defines how agents learn from mistakes and share knowledge so the same pitfalls are never repeated.

package/src/orchestrator/skills/seo-patterns/SKILL.md

@@ -3,6 +3,8 @@ name: seo-patterns
 description: "Technical SEO patterns for meta tags, structured data, sitemaps, URL strategy, and rendering. Use when optimizing pages for search engines or implementing SEO features."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # SEO Patterns
 
 ## Meta Tags & Open Graph

package/src/orchestrator/skills/session-checkpoints/SKILL.md

@@ -3,6 +3,8 @@ name: session-checkpoints
 description: "Protocol for saving and restoring session state across agent sessions. Enables replay, fork, and resume of interrupted work — inspired by Sandcastle Run Time Machine."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Skill: Session Checkpoints
 
 Use this skill when working on multi-session features or when a session may be interrupted. Checkpoints allow any future session to resume work without re-analyzing the entire codebase.

package/src/orchestrator/skills/slack-notifications/SKILL.md

@@ -3,6 +3,8 @@ name: slack-notifications
 description: "Slack MCP integration for agent-to-human notifications and bi-directional communication. Use when agents need to post progress updates, request approvals, or read user responses via Slack channels and threads."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Slack Notifications
 
 Agent communication patterns via the Slack MCP server. Enables agents to post progress updates, request human approvals, and read responses — all through Slack channels and threads.

package/src/orchestrator/skills/strapi-cms/SKILL.md

@@ -3,6 +3,8 @@ name: strapi-cms
 description: "Strapi CMS development patterns, REST/GraphQL API usage, content type building, plugin development, and deployment best practices. Use when working with Strapi content types, controllers, services, or plugins."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Strapi CMS
 
 Generic Strapi CMS development methodology. For project-specific configuration, content types, and deployment details, see [cms-config.md](../../customizations/stack/cms-config.md).

package/src/orchestrator/skills/supabase-database/SKILL.md

@@ -3,6 +3,8 @@ name: supabase-database
 description: "Supabase database migration rules, RLS policy patterns, and auth integration best practices. Use when designing database tables, writing migrations, configuring RLS policies, implementing auth, or managing user roles."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Supabase Database
 
 Generic Supabase development methodology. For project-specific schema, roles, migration history, auth flow, and key files, see [supabase-config.md](../../customizations/stack/supabase-config.md).

package/src/orchestrator/skills/task-management/SKILL.md

@@ -3,6 +3,8 @@ name: 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 customizations/ 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 [linear-config.md](../../customizations/project/linear-config.md).

package/src/orchestrator/skills/team-lead-reference/SKILL.md

@@ -3,6 +3,8 @@ name: team-lead-reference
 description: "Reference data for Team Lead orchestration — model routing, pre-delegation checks, cost tracking template, and DLQ format. Load when starting a delegation session."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Team Lead Reference
 
 For the specialist agent registry and model assignments, see [agent-registry.md](../../customizations/agents/agent-registry.md).

package/src/orchestrator/skills/teams-notifications/SKILL.md

@@ -3,6 +3,8 @@ name: teams-notifications
 description: "Microsoft Teams MCP integration for agent-to-human notifications and bi-directional communication. Use when agents need to post progress updates, request approvals, or read user responses via Teams channels and chats."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Teams Notifications
 
 Agent communication patterns via the Microsoft Teams MCP server (Microsoft Agent 365). Enables agents to post progress updates, request human approvals, and read responses — all through Teams channels and chats.

package/src/orchestrator/skills/testing-workflow/SKILL.md

@@ -3,6 +3,8 @@ name: testing-workflow
 description: "Comprehensive testing workflow including test planning, unit/integration/E2E testing patterns, coverage requirements, and common testing mistakes. Use when writing tests, planning test strategies, or validating feature completeness."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Testing Workflow
 
 ## Core Principles
@@ -60,7 +62,7 @@ Before implementing any feature, create a plan covering:
 
 ### 6. Responsive Breakpoint Tests (MANDATORY for UI changes)
 
-**Every UI feature must be tested at all three breakpoints** (Mobile 375px, Tablet 768px, Desktop 1440px). Most layout bugs only surface at mobile or tablet widths.
+**Every UI feature must be tested at all responsive breakpoints** defined in your project's testing config. Most layout bugs only surface at smaller viewports.
 
 > **Detailed breakpoint definitions, resize commands, and per-breakpoint checklists:** See the **browser-testing** skill. The **validation-gates** skill (Gate 3) defines the mandatory testing protocol.
 
@@ -119,7 +121,7 @@ After completing any feature:
 - [ ] Verified data changes match expectations
 - [ ] Checked edge cases
 - [ ] Confirmed empty states display correctly
-- [ ] **Tested at Mobile (375px), Tablet (768px), and Desktop (1440px) breakpoints**
+- [ ] **Tested at all project-defined responsive breakpoints**
 - [ ] **No horizontal overflow or layout breakage at any breakpoint**
 - [ ] Taken screenshots of key scenarios
 - [ ] Verified URL parameters are correct

package/src/orchestrator/skills/validation-gates/SKILL.md

@@ -3,6 +3,8 @@ name: validation-gates
 description: "Shared validation gates for all orchestration workflows — deterministic checks, browser testing, cache management, regression checks. Referenced by prompt templates to maintain single source of truth."
 ---
 
+<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the customizations/ directory instead. -->
+
 # Validation Gates
 
 Canonical reference for validation gates shared across all orchestration workflows. Prompt templates reference this skill to avoid duplication.
@@ -56,11 +58,11 @@ Run these commands before starting the dev server for browser testing.
 2. **Navigate to affected pages** — Verify the new feature renders correctly
 3. **Verify SPECIFIC features** — Check every feature listed in the acceptance criteria. If the criteria say "icons, groups, and AND/OR toggle", you must see all three in the browser
 4. **Test interactions** — Click buttons, fill forms, toggle filters, submit data
-5. **Test responsive** — Resize to mobile (375px), tablet (768px), desktop (1440px)
+5. **Test responsive** — Resize to each breakpoint defined in your project's testing config
 6. **Test edge cases** — Empty states, error states, loading states, long content
 7. **Screenshot evidence (REQUIRED)** — Take screenshots of key states. These are mandatory proof
 
-> **Anti-pattern:** Testing only at desktop width and assuming Tailwind classes work. They can be wrong — always verify at all three breakpoints.
+> **Anti-pattern:** Testing only at desktop width and assuming responsive classes work. They can be wrong — always verify at all defined breakpoints.
 
 Load the **browser-testing** skill for Chrome MCP commands, breakpoint details, and reporting format.
 

package/dist/cli/diff.d.ts

@@ -1,3 +0,0 @@
-import type { CliContext } from './types.js';
-export default function diff({ pkgRoot }: CliContext): Promise<void>;
-//# sourceMappingURL=diff.d.ts.map

package/dist/cli/diff.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"diff.d.ts","sourceRoot":"","sources":["../../src/cli/diff.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,YAAY,CAAA;AAE5C,wBAA8B,IAAI,CAAC,EAAE,OAAO,EAAE,EAAE,UAAU,GAAG,OAAO,CAAC,IAAI,CAAC,CAsCzE"}

package/dist/cli/diff.js

@@ -1,27 +0,0 @@
-import { resolve } from 'node:path';
-import { readFile } from 'node:fs/promises';
-import { readManifest } from './manifest.js';
-export default async function diff({ pkgRoot }) {
-    const projectRoot = process.cwd();
-    const manifest = await readManifest(projectRoot);
-    if (!manifest) {
-        console.error('  ✗ No OpenCastle installation found. Run "npx opencastle init" first.');
-        process.exit(1);
-    }
-    const pkg = JSON.parse(await readFile(resolve(pkgRoot, 'package.json'), 'utf8'));
-    if (manifest.version === pkg.version) {
-        console.log(`  No changes — installed version matches package version (v${pkg.version}).`);
-        return;
-    }
-    console.log(`\n  🏰 OpenCastle diff: v${manifest.version} → v${pkg.version}\n`);
-    console.log('  Framework files that would be updated:\n');
-    for (const path of manifest.managedPaths?.framework ?? []) {
-        console.log(`    ↻ ${path}`);
-    }
-    console.log('\n  Customization files that would be preserved:\n');
-    for (const path of manifest.managedPaths?.customizable ?? []) {
-        console.log(`    ✓ ${path}`);
-    }
-    console.log(`\n  Run "npx opencastle update" to apply.\n`);
-}
-//# sourceMappingURL=diff.js.map

package/dist/cli/diff.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"diff.js","sourceRoot":"","sources":["../../src/cli/diff.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAA;AACnC,OAAO,EAAE,QAAQ,EAAE,MAAM,kBAAkB,CAAA;AAC3C,OAAO,EAAE,YAAY,EAAE,MAAM,eAAe,CAAA;AAG5C,MAAM,CAAC,OAAO,CAAC,KAAK,UAAU,IAAI,CAAC,EAAE,OAAO,EAAc;IACxD,MAAM,WAAW,GAAG,OAAO,CAAC,GAAG,EAAE,CAAA;IAEjC,MAAM,QAAQ,GAAG,MAAM,YAAY,CAAC,WAAW,CAAC,CAAA;IAChD,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd,OAAO,CAAC,KAAK,CACX,wEAAwE,CACzE,CAAA;QACD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAA;IACjB,CAAC;IAED,MAAM,GAAG,GAAG,IAAI,CAAC,KAAK,CACpB,MAAM,QAAQ,CAAC,OAAO,CAAC,OAAO,EAAE,cAAc,CAAC,EAAE,MAAM,CAAC,CAClC,CAAA;IAExB,IAAI,QAAQ,CAAC,OAAO,KAAK,GAAG,CAAC,OAAO,EAAE,CAAC;QACrC,OAAO,CAAC,GAAG,CACT,8DAA8D,GAAG,CAAC,OAAO,IAAI,CAC9E,CAAA;QACD,OAAM;IACR,CAAC;IAED,OAAO,CAAC,GAAG,CACT,4BAA4B,QAAQ,CAAC,OAAO,OAAO,GAAG,CAAC,OAAO,IAAI,CACnE,CAAA;IACD,OAAO,CAAC,GAAG,CAAC,4CAA4C,CAAC,CAAA;IAEzD,KAAK,MAAM,IAAI,IAAI,QAAQ,CAAC,YAAY,EAAE,SAAS,IAAI,EAAE,EAAE,CAAC;QAC1D,OAAO,CAAC,GAAG,CAAC,SAAS,IAAI,EAAE,CAAC,CAAA;IAC9B,CAAC;IAED,OAAO,CAAC,GAAG,CAAC,oDAAoD,CAAC,CAAA;IAEjE,KAAK,MAAM,IAAI,IAAI,QAAQ,CAAC,YAAY,EAAE,YAAY,IAAI,EAAE,EAAE,CAAC;QAC7D,OAAO,CAAC,GAAG,CAAC,SAAS,IAAI,EAAE,CAAC,CAAA;IAC9B,CAAC;IAED,OAAO,CAAC,GAAG,CAAC,6CAA6C,CAAC,CAAA;AAC5D,CAAC"}

package/src/cli/diff.ts

@@ -1,44 +0,0 @@
-import { resolve } from 'node:path'
-import { readFile } from 'node:fs/promises'
-import { readManifest } from './manifest.js'
-import type { CliContext } from './types.js'
-
-export default async function diff({ pkgRoot }: CliContext): Promise<void> {
-  const projectRoot = process.cwd()
-
-  const manifest = await readManifest(projectRoot)
-  if (!manifest) {
-    console.error(
-      '  ✗ No OpenCastle installation found. Run "npx opencastle init" first.'
-    )
-    process.exit(1)
-  }
-
-  const pkg = JSON.parse(
-    await readFile(resolve(pkgRoot, 'package.json'), 'utf8')
-  ) as { version: string }
-
-  if (manifest.version === pkg.version) {
-    console.log(
-      `  No changes — installed version matches package version (v${pkg.version}).`
-    )
-    return
-  }
-
-  console.log(
-    `\n  🏰 OpenCastle diff: v${manifest.version} → v${pkg.version}\n`
-  )
-  console.log('  Framework files that would be updated:\n')
-
-  for (const path of manifest.managedPaths?.framework ?? []) {
-    console.log(`    ↻ ${path}`)
-  }
-
-  console.log('\n  Customization files that would be preserved:\n')
-
-  for (const path of manifest.managedPaths?.customizable ?? []) {
-    console.log(`    ✓ ${path}`)
-  }
-
-  console.log(`\n  Run "npx opencastle update" to apply.\n`)
-}