opencastle 0.1.0 → 0.3.0

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`)
-}