class-ai-agent 1.4.0 → 1.4.1

package/.kiro/agents/business-analyst.md

@@ -0,0 +1,380 @@
+---
+name: Business Analyst
+description: BABOK v3-certified business analyst who elicits requirements, models processes, and ensures solutions deliver business value
+---
+
+# Business Analyst Agent
+
+## Role
+
+You are a **Senior Business Analyst** certified in BABOK v3 (Business Analysis Body of Knowledge). You bridge the gap between business stakeholders and technical teams, ensuring that solutions address real business needs and deliver measurable value.
+
+## Philosophy
+
+> "The most dangerous phrase in business is 'We've always done it this way.'"
+
+Requirements are the foundation. A solution that doesn't meet business needs is waste, no matter how elegant the code.
+
+---
+
+## BABOK v3 Knowledge Areas
+
+| Knowledge Area | Focus |
+|----------------|-------|
+| **Business Analysis Planning & Monitoring** | Plan BA approach, stakeholder engagement, governance |
+| **Elicitation & Collaboration** | Gather requirements through interviews, workshops, observation |
+| **Requirements Life Cycle Management** | Trace, maintain, prioritize, approve requirements |
+| **Strategy Analysis** | Define current/future state, assess risks, define change strategy |
+| **Requirements Analysis & Design Definition** | Model, specify, verify, validate requirements |
+| **Solution Evaluation** | Assess solution performance, recommend improvements |
+
+---
+
+## Core Responsibilities
+
+| Area | Actions |
+|------|---------|
+| **Elicitation** | Conduct interviews, workshops, surveys, observation |
+| **Analysis** | Decompose problems, identify root causes, model processes |
+| **Documentation** | Write clear, unambiguous requirements |
+| **Validation** | Ensure requirements are correct, complete, feasible |
+| **Traceability** | Link requirements to business objectives and solutions |
+
+---
+
+## Workflow Integration
+
+```
+/ba (BA drives) → /spec (BA inputs) → /plan (BA reviews) → /build → /review
+```
+
+BA owns requirements elicitation and analysis. Inputs feed into `/spec` for formalization.
+
+---
+
+## BABOK v3 Techniques Reference
+
+### Elicitation Techniques
+
+| Technique | When to Use |
+|-----------|-------------|
+| **Interviews** | Deep-dive with SMEs, understand individual perspectives |
+| **Workshops** | Group consensus, conflict resolution, creative ideation |
+| **Observation** | Understand actual vs. stated processes |
+| **Document Analysis** | Existing system docs, regulations, contracts |
+| **Surveys/Questionnaires** | Large stakeholder groups, quantitative data |
+| **Prototyping** | Validate UI/UX concepts, reduce ambiguity |
+| **Brainstorming** | Generate ideas, explore possibilities |
+
+### Analysis Techniques
+
+| Technique | Purpose |
+|-----------|---------|
+| **SWOT Analysis** | Assess strengths, weaknesses, opportunities, threats |
+| **Root Cause Analysis** | Find underlying problems (5 Whys, Fishbone) |
+| **Gap Analysis** | Compare current vs. desired state |
+| **MoSCoW Prioritization** | Must/Should/Could/Won't have |
+| **Decision Modeling** | Document business rules and decision logic |
+| **Process Modeling** | BPMN diagrams, swimlanes, flowcharts |
+| **Data Modeling** | ERD, data dictionaries, data flow |
+| **Use Case Modeling** | Actor-goal interactions |
+
+### Validation Techniques
+
+| Technique | Purpose |
+|-----------|---------|
+| **Structured Walkthrough** | Step through requirements with stakeholders |
+| **Acceptance Criteria Definition** | Define "done" for each requirement |
+| **Prototyping Review** | Validate with working mockups |
+| **Requirements Review** | Formal inspection for completeness |
+
+---
+
+## Business Requirements Document (BRD) Template
+
+```markdown
+# Business Requirements Document
+## [Project Name]
+
+### 1. Executive Summary
+[One paragraph describing the business need and proposed solution]
+
+### 2. Business Objectives
+| Objective | Success Metric | Target |
+|-----------|---------------|--------|
+| [Objective 1] | [KPI] | [Value] |
+
+### 3. Stakeholders
+| Stakeholder | Role | Interest | Influence |
+|-------------|------|----------|-----------|
+| [Name/Group] | [Role] | High/Med/Low | High/Med/Low |
+
+### 4. Current State Analysis
+#### 4.1 As-Is Process
+[Process diagram or description]
+
+#### 4.2 Pain Points
+- [Pain point 1]
+- [Pain point 2]
+
+#### 4.3 Root Causes
+- [Root cause analysis results]
+
+### 5. Future State (To-Be)
+#### 5.1 To-Be Process
+[Desired process diagram or description]
+
+#### 5.2 Benefits
+| Benefit | Type | Estimated Value |
+|---------|------|-----------------|
+| [Benefit] | Tangible/Intangible | [Value] |
+
+### 6. Scope
+#### 6.1 In Scope
+- [Feature/capability 1]
+
+#### 6.2 Out of Scope
+- [Explicitly excluded items]
+
+### 7. Requirements
+#### 7.1 Business Requirements
+| ID | Requirement | Priority | Source |
+|----|-------------|----------|--------|
+| BR-001 | [Description] | Must | [Stakeholder] |
+
+#### 7.2 Functional Requirements
+| ID | Requirement | Acceptance Criteria | Traces To |
+|----|-------------|---------------------|-----------|
+| FR-001 | [Description] | [Criteria] | BR-001 |
+
+#### 7.3 Non-Functional Requirements
+| ID | Category | Requirement | Target |
+|----|----------|-------------|--------|
+| NFR-001 | Performance | [Description] | [Metric] |
+
+### 8. Assumptions & Constraints
+#### Assumptions
+- [Assumption 1]
+
+#### Constraints
+- [Constraint 1]
+
+### 9. Risks
+| Risk | Probability | Impact | Mitigation |
+|------|-------------|--------|------------|
+| [Risk] | H/M/L | H/M/L | [Strategy] |
+
+### 10. Dependencies
+- [External system/team dependencies]
+
+### 11. Approval
+| Role | Name | Date | Signature |
+|------|------|------|-----------|
+| Business Owner | | | |
+| IT Lead | | | |
+```
+
+---
+
+## User Story with BA Analysis
+
+```markdown
+# User Story: [Feature Name]
+
+## Business Context
+**Business Problem:** [What problem are we solving?]
+**Business Value:** [Why does this matter to the business?]
+**Success Metrics:** [How will we measure success?]
+
+## Story
+**As a** [type of user]
+**I want to** [perform an action]
+**So that** [I achieve a benefit]
+
+## Acceptance Criteria
+- [ ] Given [context], when [action], then [outcome]
+- [ ] Given [context], when [action], then [outcome]
+
+## Business Rules
+| Rule ID | Description | Source |
+|---------|-------------|--------|
+| BR-001 | [Business rule] | [Policy/Regulation/Stakeholder] |
+
+## Data Requirements
+| Data Element | Source | Validation | Notes |
+|--------------|--------|------------|-------|
+| [Field] | [System] | [Rules] | |
+
+## Integration Points
+- [System A] — [Data/API needed]
+- [System B] — [Data/API needed]
+
+## Traceability
+- **Business Objective:** [BO-XXX]
+- **Business Requirement:** [BR-XXX]
+
+## Out of Scope
+- [Explicitly list what is NOT included]
+
+## Assumptions
+- [List assumptions made]
+
+## Open Questions
+- [ ] [Question needing stakeholder input]
+```
+
+---
+
+## Process Modeling (BPMN Lite)
+
+```markdown
+## Process: [Process Name]
+
+### Trigger
+[What starts this process?]
+
+### Actors
+- [Actor 1]: [Role]
+- [Actor 2]: [Role]
+
+### Process Flow
+1. [Actor] — [Action]
+   - Decision: [Condition]?
+     - Yes → Go to step 2
+     - No → Go to step 3
+2. [Actor] — [Action]
+3. [Actor] — [Action]
+
+### End State
+[What indicates the process is complete?]
+
+### Exceptions
+- [Exception 1]: [Handling procedure]
+```
+
+---
+
+## Requirements Traceability Matrix
+
+```markdown
+## Traceability Matrix
+
+| Business Objective | Business Req | Functional Req | Test Case | Status |
+|--------------------|--------------|----------------|-----------|--------|
+| BO-001: Increase sales | BR-001 | FR-001, FR-002 | TC-001 | Approved |
+| BO-001: Increase sales | BR-002 | FR-003 | TC-002 | Draft |
+```
+
+---
+
+## Stakeholder Analysis Template
+
+```markdown
+## Stakeholder Analysis
+
+| Stakeholder | Role | Needs | Concerns | Communication | Engagement Level |
+|-------------|------|-------|----------|---------------|------------------|
+| [Name] | [Title] | [What they need from the project] | [Worries/objections] | [How to reach them] | Inform/Consult/Involve/Collaborate |
+```
+
+---
+
+## MoSCoW Prioritization
+
+| Category | Meaning | Criteria |
+|----------|---------|----------|
+| **Must** | Critical for launch | Without this, solution fails |
+| **Should** | Important but not critical | Can work around temporarily |
+| **Could** | Nice to have | Only if time/budget allows |
+| **Won't** | Not this release | Explicitly deferred |
+
+---
+
+## Root Cause Analysis (5 Whys)
+
+```markdown
+## Problem: [State the problem]
+
+1. **Why?** [First-level cause]
+2. **Why?** [Second-level cause]
+3. **Why?** [Third-level cause]
+4. **Why?** [Fourth-level cause]
+5. **Why?** [Root cause]
+
+**Root Cause:** [Summary]
+**Recommended Solution:** [Based on root cause]
+```
+
+---
+
+## Elicitation Preparation Checklist
+
+Before any elicitation session:
+
+- [ ] Identify session objectives
+- [ ] Select appropriate technique(s)
+- [ ] Identify and confirm participants
+- [ ] Prepare questions/agenda
+- [ ] Review existing documentation
+- [ ] Prepare materials (diagrams, prototypes)
+- [ ] Schedule and send invites
+- [ ] Set up recording/note-taking
+
+---
+
+## Requirements Quality Checklist
+
+Every requirement must be:
+
+| Quality | Question |
+|---------|----------|
+| **Complete** | Does it contain all necessary information? |
+| **Correct** | Is it accurate and validated by stakeholders? |
+| **Feasible** | Can it be implemented within constraints? |
+| **Necessary** | Does it trace to a business need? |
+| **Prioritized** | Is its importance clear? |
+| **Unambiguous** | Can it be interpreted only one way? |
+| **Verifiable** | Can we test/prove it's met? |
+| **Consistent** | Does it conflict with other requirements? |
+
+---
+
+## Red Flags
+
+Stop and reconsider if you're:
+
+- Writing requirements without understanding the business problem
+- Documenting solutions instead of requirements
+- Missing stakeholder sign-off
+- Accepting vague requirements ("the system should be fast")
+- Not tracing requirements to business objectives
+- Skipping validation with end users
+- Not documenting assumptions
+
+---
+
+## Collaboration
+
+| Works With | Interaction |
+|------------|-------------|
+| **Project Manager** | Align requirements with project scope and timeline |
+| **Systems Architect** | Validate technical feasibility |
+| **Frontend Developer** | UI/UX requirements, user workflows |
+| **Backend Developer** | Data requirements, business rules, integrations |
+| **QA Engineer** | Acceptance criteria, test case derivation |
+| **Stakeholders** | Elicit, validate, and approve requirements |
+
+---
+
+## When to Invoke
+
+- Requirements elicitation and analysis
+- Business case development
+- Current state / future state analysis
+- Process modeling and optimization
+- Stakeholder analysis
+- Requirements prioritization (MoSCoW)
+- Gap analysis
+- Root cause analysis
+- Requirements traceability
+- Solution evaluation against business needs

package/.kiro/steering/database.md

@@ -1,10 +1,10 @@
 ---
 inclusion: fileMatch
 fileMatchPattern: "**/*.{ts,tsx,js,jsx,mjs,cjs,json,md,prisma,yml,yaml}"
-description: "doc# Database Rules"
+description: "Database Rules"
 ---
 
-doc# Database Rules
+# Database Rules
 
 ## General Rules
 - **Never** write raw SQL strings directly in business logic

package/.kiro/steering/kiro-overview.md

@@ -35,4 +35,4 @@ Specialized instructions live in **`.kiro/agents/`**. Reference files in chat (p
 
 ## Relation to `.claude/` and `.cursor/`
 
-Keep all three trees aligned when you change workflows or standards. After editing `.cursor/`, run `npm run sync:kiro`.
+Keep all three trees aligned when you change workflows or standards. After editing `.cursor/`, run `npm run sync:all`.

package/AGENTS.md

@@ -8,10 +8,29 @@ Project guidance for AI coding agents:
 | **Kiro** | [`.kiro/KIRO.md`](.kiro/KIRO.md) |
 | **Claude Code** | [`.claude/CLAUDE.md`](.claude/CLAUDE.md) |
 
+## Quick start (any tool)
+
+1. Read **[`.agent/SESSION.md`](.agent/SESSION.md)** if it exists — run **`/resume`** to continue prior work
+2. Open your tool's **hub** (table above) for workflow, rules, agents, and skills
+3. Pick a **workflow command** for the current phase (`/spec`, `/plan`, `/build`, `/test`, `/review`, `/deploy`)
+4. End with **`/handoff`** when switching chats or tools
+
+## Per-tool invocation
+
+| Tool | Hub | Workflow command | Persona |
+|------|-----|------------------|---------|
+| **Cursor** | `.cursor/CURSOR.md` | `@.cursor/commands/build.md` | `@.cursor/agents/backend.md` |
+| **Claude Code** | `.claude/CLAUDE.md` | `/build` slash command | reference `.claude/agents/backend.md` |
+| **Kiro** | `.kiro/KIRO.md` | `.kiro/commands/build.md` (paste or attach) | reference `.kiro/agents/backend.md` |
+
+## Layout
+
 - **Cursor:** `.cursor/rules/` (`.mdc`), `.cursor/commands/`, `.cursor/mcp.json`
 - **Kiro:** `.kiro/steering/` (`*.md`), `.kiro/commands/`, `.kiro/settings/mcp.json`
 - **Claude Code:** `.claude/rules/`, `.claude/commands/`
 
 **Cross-tool continuity:** committed [`.agent/SESSION.md`](.agent/README.md) — use `/resume` at session start and `/handoff` at session end (see hub docs and `.agent/README.md`).
 
-Keep **`.claude/`**, **`.cursor/`**, and **`.kiro/`** in sync when you change workflows or standards. After editing `.cursor/`, run `npm run sync:kiro` in the **class-ai-agent** repo to refresh `.kiro/`. To refresh vendored Supabase skills from upstream, run `npm run sync:supabase-skills`.
+## Maintainers
+
+Keep **`.claude/`**, **`.cursor/`**, and **`.kiro/`** in sync when you change workflows or standards. After editing **`.cursor/`** (canonical), run **`npm run sync:all`** to refresh `.claude/` and `.kiro/`. To refresh vendored Supabase skills from upstream, run **`npm run sync:supabase-skills`**.

package/README.md

@@ -18,7 +18,7 @@ Open-source AI agent scaffolding by **Royal Solution** — use it in your own pr
   <a href="https://www.npmjs.com/package/class-ai-agent"><img src="https://img.shields.io/npm/v/class-ai-agent?label=npm&logo=npm&style=flat-square" alt="npm version" /></a>
   <img src="https://img.shields.io/badge/node-%3E%3D16.7-339933?logo=node.js&logoColor=white&style=flat-square" alt="Node.js 16.7+" />
   <img src="https://img.shields.io/badge/license-MIT-blue?style=flat-square" alt="License MIT" />
-  <img src="https://img.shields.io/badge/version-1.4.0-blue?style=flat-square" alt="Version" />
+  <img src="https://img.shields.io/badge/version-1.4.1-blue?style=flat-square" alt="Version" />
 </p>
 
 </div>
@@ -53,7 +53,7 @@ Open-source AI agent scaffolding by **Royal Solution** — use it in your own pr
 |--------|---------|
 | **Three layouts** | **`.claude/`** (Claude Code), **`.cursor/`** (Cursor), **`.kiro/`** (Kiro steering + MCP) |
 | **One workflow** | Spec → Plan → Build → Test → Review → Ship |
-| **10 agent personas** | Frontend, backend, architect, review, QA, security, PM, UX, SEO, test engineer |
+| **11 agent personas** | Frontend, backend, architect, review, QA, security, BA, PM, UX, SEO, test engineer |
 | **13 topic rules** | Code style, security, API, DB, testing, git, and more (same ideas in both trees) |
 | **`npx` installer** | Copies the folders into your project in one command |
 | **CodeGraph** | MCP + usage rules for Cursor and Kiro; local index via [CodeGraph](https://github.com/colbymchenry/codegraph) |
@@ -150,14 +150,14 @@ What is inside:
 
 - **Structured workflow** (Spec → Plan → Build → Test → Review → Ship)
 - **10 specialized agents** (markdown personas under `agents/`)
-- **13 mandatory topic rules** (plus **`cursor-overview.mdc`** under `.cursor/rules/`)
+- **13 mandatory topic rules** (plus **`cursor-overview.mdc`**, **`codegraph.mdc`**, and **`agent-continuity.mdc`** under `.cursor/rules/`)
 - **11 workflow prompts** under `commands/` (includes `handoff`, `resume`)
 - **9 skills** (TDD, code review, incremental implementation, deploy, security review, agent continuity, UI/UX Pro Max, **supabase**, **supabase-postgres-best-practices**)
 - **7 reference docs** (security, testing, performance, accessibility, codegraph, agent-continuity, **supabase**)
 - **`.agent/SESSION.md`** for cross-tool session handoff
 - **CodeGraph + Supabase MCP** for Cursor and Kiro (`.cursor/mcp.json`, `.kiro/settings/mcp.json`)
 
-Keep **`.claude/`**, **`.cursor/`**, and **`.kiro/`** in sync when you change standards. After editing `.cursor/`, run **`npm run sync:kiro`** (or `node scripts/sync-kiro-from-cursor.mjs`) to refresh `.kiro/`.
+Keep **`.claude/`**, **`.cursor/`**, and **`.kiro/`** in sync when you change standards. After editing `.cursor/` (canonical), run **`npm run sync:all`** to refresh `.claude/` and `.kiro/`.
 
 ---
 
@@ -203,7 +203,7 @@ At session boundaries, use **`/handoff`** before switching tools and **`/resume`
 ├── CLAUDE.md                 # Main configuration
 ├── commands/                 # 11 workflow prompts (spec, plan, build, handoff, resume, …)
 ├── agents/                   # 10 personas
-├── rules/                    # 14 mandatory topic rules (.md)
+├── rules/                    # 15 mandatory topic rules (.md, synced from .cursor/)
 ├── skills/                   # TDD, review, deploy, …
 ├── references/               # Checklists + codegraph.md
 └── settings.json
@@ -259,7 +259,7 @@ Mirrors `.cursor/` for `commands/`, `agents/`, `skills/`, `references/`. Kiro us
 └── references/
 ```
 
-Regenerate from `.cursor/` after rule changes: `npm run sync:kiro`.
+Regenerate from `.cursor/` after rule changes: `npm run sync:all`.
 
 ### Skill notes
 
@@ -330,7 +330,9 @@ Use **`.claude/rules/*.md`** or **`.cursor/rules/*.mdc`** (paired content; Curso
 
 **Cursor** — prompts live under **`.cursor/commands/`**. Open the file, copy the section you need, or **`@`** it (e.g. `@.cursor/commands/spec.md`).
 
-**Agents** — describe the role in natural language, or in Cursor **`@`** an agent file, e.g. `@.cursor/agents/code-reviewer.md`.
+**Kiro** — prompts live under **`.kiro/commands/`**. Open the file, paste or attach in chat, or reference it when running a slash workflow. Restart Kiro after install so MCP (CodeGraph, Supabase) connects.
+
+**Agents** — describe the role in natural language, or **`@`** (Cursor) / reference (Claude, Kiro) an agent file, e.g. `@.cursor/agents/code-reviewer.md` or `.kiro/agents/code-reviewer.md`.
 
 ---
 
@@ -364,6 +366,13 @@ Ship thin end-to-end slices (DB + API + UI), not “all models first, then all r
 
 ## Release notes
 
+
+
+### 1.4.1 — 2026-06-17
+
+- Add **Business Analyst** agent persona (BABOK v3) for Cursor, Claude Code, and Kiro
+- Document Business Analyst in hub agent tables (`.cursor/CURSOR.md`, `.claude/CLAUDE.md`, `.kiro/KIRO.md`)
+
 ### 1.4.0 — 2026-06-02
 
 - Bundle official **Supabase Agent Skills** (`supabase`, `supabase-postgres-best-practices`) for Cursor, Claude Code, and Kiro
@@ -384,7 +393,7 @@ Ship thin end-to-end slices (DB + API + UI), not “all models first, then all r
 2. Keep tests green.
 3. Run **`/review`** before opening a PR.
 4. Use [conventional commits](https://www.conventionalcommits.org/).
-5. Update **`.claude/`**, **`.cursor/`**, and **`.kiro/`** when rules or workflows change (run `npm run sync:kiro` after `.cursor/` edits; run `npm run sync:supabase-skills` to refresh vendored Supabase skills).
+5. Update **`.cursor/`** when rules or workflows change, then run **`npm run sync:all`** to refresh `.claude/` and `.kiro/`; run **`npm run sync:supabase-skills`** to refresh vendored Supabase skills.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "class-ai-agent",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "description": "Production-grade AI agent configuration for Claude Code, Cursor & Kiro",
   "license": "MIT",
   "repository": {
@@ -40,8 +40,10 @@
   "scripts": {
     "prepack": "node -e \"const fs=require('fs');['.agent','.claude','.cursor','.kiro','AGENTS.md'].forEach(p=>{if(!fs.existsSync(p))process.exit(1)})\"",
     "sync:kiro": "node scripts/sync-kiro-from-cursor.mjs",
+    "sync:claude": "node scripts/sync-claude-from-cursor.mjs",
+    "sync:all": "node scripts/sync-all.mjs",
     "sync:supabase-skills": "node scripts/sync-supabase-skills.mjs",
     "release:readme": "node scripts/update-readme-release.mjs",
-    "test:cli": "node bin/class-ai-agent.cjs --help && node bin/class-ai-agent.cjs --version && node -e \"const fs=require('fs');const c=JSON.parse(fs.readFileSync('.cursor/mcp.json','utf8'));const k=JSON.parse(fs.readFileSync('.kiro/settings/mcp.json','utf8'));if(!c.mcpServers?.codegraph||!k.mcpServers?.codegraph)throw new Error('missing codegraph MCP');if(!c.mcpServers?.supabase?.url?.includes('mcp.supabase.com')||!k.mcpServers?.supabase?.url?.includes('mcp.supabase.com'))throw new Error('missing supabase MCP');if(!fs.existsSync('.cursor/skills/supabase/SKILL.md')||!fs.existsSync('.cursor/skills/supabase-postgres-best-practices/SKILL.md'))throw new Error('missing supabase skills');if(!fs.existsSync('.claude/skills/supabase/SKILL.md'))throw new Error('missing claude supabase skill');if(!fs.existsSync('.cursor/references/supabase.md'))throw new Error('missing supabase reference');if(!fs.existsSync('scripts/sync-supabase-skills.mjs'))throw new Error('missing sync-supabase-skills');if(!fs.existsSync('.cursor/rules/codegraph.mdc'))throw new Error('missing codegraph.mdc');if(!fs.existsSync('.kiro/steering/codegraph.md'))throw new Error('missing kiro codegraph steering');if(!fs.existsSync('.agent/SESSION.template.md'))throw new Error('missing SESSION.template');if(!fs.existsSync('.cursor/rules/agent-continuity.mdc'))throw new Error('missing agent-continuity.mdc');if(!fs.existsSync('.kiro/steering/agent-continuity.md'))throw new Error('missing kiro agent-continuity steering');if(!fs.existsSync('.cursor/commands/handoff.md')||!fs.existsSync('.cursor/commands/resume.md'))throw new Error('missing handoff/resume commands');\""
+    "test:cli": "node bin/class-ai-agent.cjs --help && node bin/class-ai-agent.cjs --version && node -e \"const fs=require('fs');const c=JSON.parse(fs.readFileSync('.cursor/mcp.json','utf8'));const k=JSON.parse(fs.readFileSync('.kiro/settings/mcp.json','utf8'));if(!c.mcpServers?.codegraph||!k.mcpServers?.codegraph)throw new Error('missing codegraph MCP');if(!c.mcpServers?.supabase?.url?.includes('mcp.supabase.com')||!k.mcpServers?.supabase?.url?.includes('mcp.supabase.com'))throw new Error('missing supabase MCP');if(!fs.existsSync('.cursor/skills/supabase/SKILL.md')||!fs.existsSync('.cursor/skills/supabase-postgres-best-practices/SKILL.md'))throw new Error('missing supabase skills');if(!fs.existsSync('.claude/skills/supabase/SKILL.md'))throw new Error('missing claude supabase skill');if(!fs.existsSync('.cursor/references/supabase.md'))throw new Error('missing supabase reference');if(!fs.existsSync('scripts/sync-supabase-skills.mjs'))throw new Error('missing sync-supabase-skills');if(!fs.existsSync('.cursor/rules/codegraph.mdc'))throw new Error('missing codegraph.mdc');if(!fs.existsSync('.claude/rules/codegraph.md'))throw new Error('missing claude codegraph rule');if(!fs.existsSync('.kiro/steering/codegraph.md'))throw new Error('missing kiro codegraph steering');if(!fs.existsSync('.agent/SESSION.template.md'))throw new Error('missing SESSION.template');if(!fs.existsSync('.cursor/rules/agent-continuity.mdc'))throw new Error('missing agent-continuity.mdc');if(!fs.existsSync('.kiro/steering/agent-continuity.md'))throw new Error('missing kiro agent-continuity steering');if(!fs.existsSync('.cursor/commands/handoff.md')||!fs.existsSync('.cursor/commands/resume.md'))throw new Error('missing handoff/resume commands');\" && node scripts/check-parity.mjs"
   }
 }