@fission-ai/openspec 0.1.0 → 0.2.0

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2024 OpenSpec Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

package/README.md

@@ -1,119 +1,283 @@
+<p align="center">
+  <a href="https://github.com/Fission-AI/OpenSpec">
+    <picture>
+      <source srcset="assets/openspec_pixel_dark.svg" media="(prefers-color-scheme: dark)">
+      <source srcset="assets/openspec_pixel_light.svg" media="(prefers-color-scheme: light)">
+      <img src="assets/openspec_pixel_light.svg" alt="OpenSpec logo" height="64">
+    </picture>
+  </a>
+  
+</p>
+<p align="center">Spec-driven development for AI coding assistants.</p>
+<p align="center">
+  <a href="https://github.com/Fission-AI/OpenSpec/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/Fission-AI/OpenSpec/actions/workflows/ci.yml/badge.svg" /></a>
+  <a href="https://www.npmjs.com/package/@fission-ai/openspec"><img alt="npm version" src="https://img.shields.io/npm/v/@fission-ai/openspec?style=flat-square" /></a>
+  <a href="https://nodejs.org/"><img alt="node version" src="https://img.shields.io/node/v/@fission-ai/openspec?style=flat-square" /></a>
+  <a href="./LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" /></a>
+  <a href="https://conventionalcommits.org"><img alt="Conventional Commits" src="https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg?style=flat-square" /></a>
+</p>
+
+<p align="center">
+  <img src="assets/openspec_dashboard.png" alt="OpenSpec dashboard preview" width="90%">
+</p>
+
+<p align="center">
+  Follow <a href="https://x.com/0xTab">@0xTab on X</a> for updates.
+</p>
+
 # OpenSpec
 
-A specification-driven development system for maintaining living documentation alongside your code.
+**Supported AI Tools:** ✅ Claude Code | 🔜 Cursor (coming soon) | ✅ AGENTS.md instructions
+
+Create **alignment** between humans and AI coding assistants through spec-driven development. **No API keys required.**
+
+OpenSpec ensures you and your AI assistant agree on what to build before any code is written. By discussing and refining specifications first, you bring determinism to AI code generation, getting exactly what you want, not what the AI thinks you might want.
+
+## Why OpenSpec?
+
+**The Problem:** AI coding assistants are powerful but unpredictable. Without clear specifications, they generate code based on assumptions, often missing requirements or adding unwanted features. Teams waste time in review cycles because humans and AI aren't aligned on what to build.
+
+**The Solution:** OpenSpec creates alignment BEFORE code is written:
+- **Human-AI Alignment** - You and your AI agree on specifications before implementation
+- **Deterministic, Predictable Output** - Clear specs lead to reliable, repeatable code generation
+- **Team Alignment via Spec Reviews** - Everyone reviews intentions, not code surprises
+- **Clear Feature Scope** - Know exactly what you're building—and what you're not
+- **Progress Tracking** - See what's proposed, in progress, or completed at a glance
+- **Living Documentation** - Specs evolve with your code as a natural byproduct
+- **Universal Tool Support** - Works with any AI assistant (Claude Code, Cursor, and more)
+- **No API Keys Required** - Integrates through context rules, not external services
+
+## How It Works
+
+```
+┌─────────────┐       ┌─────────────┐       ┌──────────────┐
+│    SPECS    │       │   CHANGES   │       │   ARCHIVE    │
+│   (Truth)   │◀──────│ (Proposals) │──────▶│ (Completed)  │
+└─────────────┘       └─────────────┘       └──────────────┘
+      ▲                      │                      │
+      │                      ▼                      │
+      │               ┌─────────────┐               │
+      └───────────────│    CODE     │◀──────────────┘
+                      └─────────────┘
+
+1. SPECS define current capabilities (what IS built)
+2. CHANGES propose modifications using deltas (what SHOULD change)  
+3. CODE implements the changes following tasks
+4. ARCHIVE preserves completed changes after deployment
+```
 
 ## Installation
 
+### Prerequisites
+
+- Node.js >= 20.19.0
+
+### Install OpenSpec
+
+Install globally:
+
 ```bash
-npm install -g openspec
+npm install -g @fission-ai/openspec
 ```
 
-## Quick Start
+## Getting Started
+
+### 1. Initialize OpenSpec in Your Project
 
 ```bash
-# Initialize OpenSpec in your project
+# Navigate to your project
+cd my-project
+
+# Initialize OpenSpec
 openspec init
 
-# Update existing OpenSpec instructions (team-friendly)
-openspec update
+# Select your AI tool (more coming soon!):
+# "Which AI tool do you use?"
+#   > Claude Code
+#     Cursor (coming soon)
+
+# This creates:
+# openspec/
+#   ├── specs/       # Current specifications (truth)
+#   ├── changes/     # Proposed changes
+#   └── AGENTS.md    # AI instructions for your tool
+```
+
+### 2. Create Your First Change
+
+Jump straight into creating a change proposal with your AI assistant (works with Claude Code, Cursor, or any AI tool):
+
+```markdown
+// Quick win - Add a simple new feature:
+You: "I want to add a user profile API endpoint.
+      Please create an OpenSpec change proposal for this."
 
-# List specs or changes
-openspec spec list        # specs (IDs by default; use --long for details)
-openspec change list      # changes (IDs by default; use --long for details)
+AI: "I'll create an OpenSpec change proposal for the user profile API..."
+    *Creates openspec/changes/add-user-profile-api/ with:*
+    - proposal.md (why this feature is needed)
+    - tasks.md (implementation checklist)
+    - design.md (API design decisions)
+    - specs/user-profile/spec.md (new requirements)
 
-# Show differences between specs and proposed changes
-openspec diff [change-name]
+You: "The proposal looks good. Let's implement it."
 
-# Archive completed changes
-openspec archive [change-name]
+AI: "Following the tasks in openspec/changes/add-user-profile-api/tasks.md:
+     Task 1.1: Create user profile model..."
+    *Implements each task systematically*
 ```
 
-## Commands
+### 3. Track Your Work
 
-### `openspec init`
+```bash
+# View active changes (what's being worked on)
+openspec list
 
-Initializes OpenSpec in your project by creating:
-- `openspec/` directory structure
-- `openspec/README.md` with OpenSpec instructions
-- AI tool configuration files (based on your selection)
+# Validate your changes are properly formatted
+openspec validate add-2fa --strict
 
-### `openspec update`
+# After deployment, archive the completed change
+openspec archive add-2fa
+# This moves the change to archive/ and updates specs/
+```
 
-Updates OpenSpec instructions to the latest version. This command is **team-friendly** and only updates files that already exist:
+## Common Commands
 
-- Always updates `openspec/README.md` with the latest OpenSpec instructions
-- **Only updates existing AI tool configuration files** (e.g., CLAUDE.md, CURSOR.md)
-- **Never creates new AI tool configuration files**
-- Preserves content outside of OpenSpec markers in AI tool files
+```bash
+# Most used:
+openspec list              # See what changes you're working on
+openspec archive <change>  # Mark a change as complete after deployment
 
-This allows team members to use different AI tools without conflicts. Each developer can maintain their preferred AI tool configuration file, and `openspec update` will respect their choice.
+# Also useful:
+openspec validate <change> # Check formatting before committing
+openspec show <change>     # View change details
+```
 
-### `openspec spec`
+## Example: How AI Creates OpenSpec Files
 
-Manage and view specifications.
+When you ask your AI assistant to "add two-factor authentication", it creates:
 
-Examples:
-- `openspec spec show <spec-id>`
-  - Text mode: prints raw `spec.md` content
-  - JSON mode (`--json`): returns minimal, stable shape
-    - Filters are JSON-only: `--requirements`, `--no-scenarios`, `-r/--requirement <1-based>`
-- `openspec spec list`
-  - Prints IDs only by default
-  - Use `--long` to include `title` and `[requirements N]`
-- `openspec spec validate <spec-id>`
-  - Text: human-readable summary to stdout/stderr
-  - `--json` for structured report
+```
+openspec/
+├── specs/
+│   └── auth/
+│       └── spec.md           # Current auth spec (if exists)
+└── changes/
+    └── add-2fa/              # AI creates this entire structure
+        ├── proposal.md       # Why and what changes
+        ├── tasks.md          # Implementation checklist
+        ├── design.md         # Technical decisions (optional)
+        └── specs/
+            └── auth/
+                └── spec.md   # Delta showing additions
+```
 
-### `openspec change`
+### AI-Generated Spec (created in `openspec/specs/auth/spec.md`):
 
-Manage and view change proposals.
+```markdown
+# Auth Specification
 
-Examples:
-- `openspec change show <change-id>`
-  - Text mode: prints raw `proposal.md` content
-  - JSON mode (`--json`): `{ id, title, deltaCount, deltas }`
-  - Filtering is JSON-only: `--deltas-only` (alias: `--requirements-only`, deprecated)
-- `openspec change list`
-  - Prints IDs only by default
-  - Use `--long` to include `title` and counts `[deltas N] [tasks x/y]`
-- `openspec change validate <change-id>`
-  - Text: human-readable result
-  - `--json` for structured report
+## Purpose
+Authentication and session management.
 
-### `openspec diff [change-name]`
+## Requirements
+### Requirement: User Authentication
+The system SHALL issue a JWT on successful login.
 
-Shows the differences between current specs and proposed changes:
-- Displays a unified diff format
-- Helps review what will change before implementation
-- Useful for pull request reviews
+#### Scenario: Valid credentials
+- WHEN a user submits valid credentials
+- THEN a JWT is returned
+```
+
+### AI-Generated Change Delta (created in `openspec/changes/add-2fa/specs/auth/spec.md`):
 
-### `openspec archive [change-name]`
+```markdown
+# Delta for Auth
 
-Archives a completed change:
-- Moves change from `openspec/changes/` to `openspec/changes/archive/`
-- Adds a date prefix to the archived change
-- Updates specs to reflect the new state
-- Use `--skip-specs` to archive without updating specs (for abandoned changes)
+## ADDED Requirements
+### Requirement: Two-Factor Authentication
+The system MUST require a second factor during login.
 
-## Team Collaboration
+#### Scenario: OTP required
+- WHEN a user submits valid credentials
+- THEN an OTP challenge is required
+```
 
-OpenSpec is designed for team collaboration:
+### AI-Generated Tasks (created in `openspec/changes/add-2fa/tasks.md`):
 
-1. **AI Tool Flexibility**: Each team member can use their preferred AI assistant (Claude, Cursor, etc.)
-2. **Non-Invasive Updates**: The `update` command only modifies existing files, never forcing tools on team members
-3. **Specification Sharing**: The `openspec/` directory contains shared specifications that all team members work from
-4. **Change Tracking**: Proposed changes are visible to all team members for review before implementation
+```markdown
+## 1. Database Setup
+- [ ] 1.1 Add OTP secret column to users table
+- [ ] 1.2 Create OTP verification logs table
+
+## 2. Backend Implementation  
+- [ ] 2.1 Add OTP generation endpoint
+- [ ] 2.2 Modify login flow to require OTP
+- [ ] 2.3 Add OTP verification endpoint
+
+## 3. Frontend Updates
+- [ ] 3.1 Create OTP input component
+- [ ] 3.2 Update login flow UI
+```
+
+**Important:** You don't create these files manually. Your AI assistant generates them based on your requirements and the existing codebase.
+
+## Understanding OpenSpec Files
+
+### Delta Format
+
+Deltas are "patches" that show how specs change:
+
+- **`## ADDED Requirements`** - New capabilities
+- **`## MODIFIED Requirements`** - Changed behavior (include complete updated text)
+- **`## REMOVED Requirements`** - Deprecated features
+
+**Format requirements:**
+- Use `### Requirement: <name>` for headers
+- Every requirement needs at least one `#### Scenario:` block
+- Use SHALL/MUST in requirement text
 
-## Contributing
 
-See `openspec/specs/` for the current system specifications and `openspec/changes/` for pending improvements.
+## Why OpenSpec Works
 
-## Notes
+OpenSpec creates **alignment** between you and your AI coding assistant:
+
+1. **You describe** what you want to build
+2. **AI creates specs** before writing any code
+3. **You review and adjust** the specifications
+4. **AI implements** exactly what was specified
+5. **Everyone understands** what's being built through clear specs
+
+**True Interoperability:** OpenSpec is designed to be universal. No API keys, no vendor lock-in. It works by adding context rules to ANY AI coding tool - whether you use Claude Code today, switch to Cursor tomorrow, or adopt the next breakthrough AI assistant. Your specs remain portable and your workflow stays consistent.
+
+
+## How OpenSpec Compares
+
+### vs. Kiro.dev
+OpenSpec groups all changes for a feature in one place (`openspec/changes/feature-name/`), making it easy to track what needs to be done. Kiro spreads changes across multiple spec folders, making feature tracking harder.
+
+### vs. No Specs
+Without specs, AI coding assistants generate code based on vague prompts, often missing requirements or adding unwanted features. OpenSpec ensures alignment before any code is written.
+
+## Team Adoption
+
+### Getting Started with Your Team
+
+1. **Initialize OpenSpec** - Run `openspec init` in your project
+2. **Start with new features** - Use OpenSpec for your next change proposal
+3. **Build incrementally** - Each new feature adds to your spec library
+4. **Future capability** - We're working on tools to generate specs from existing code
+
+**Tool Freedom:** Your team can use different AI assistants. One developer might use Claude Code while another uses Cursor - OpenSpec keeps everyone aligned through shared specifications. Run `openspec update` to configure for any supported tool without affecting others.
+
+
+## Contributing
 
-- The legacy `openspec list` command is deprecated. Use `openspec spec list` and `openspec change list`.
-- Text output is raw-first (no formatting or filtering). Prefer `--json` for tooling-friendly output.
-- Global `--no-color` disables ANSI colors and respects `NO_COLOR`.
+- Install dependencies: `npm install`
+- Build: `npm run build`
+- Test: `npm test`
+- Develop CLI locally: `npm run dev` or `npm run dev:cli`
+- Conventional commits (one-line): `type(scope): subject`
 
 ## License
 
-MIT
+MIT

package/dist/cli/index.js

@@ -5,9 +5,9 @@ import path from 'path';
 import { promises as fs } from 'fs';
 import { InitCommand } from '../core/init.js';
 import { UpdateCommand } from '../core/update.js';
-import { DiffCommand } from '../core/diff.js';
 import { ListCommand } from '../core/list.js';
 import { ArchiveCommand } from '../core/archive.js';
+import { ViewCommand } from '../core/view.js';
 import { registerSpecCommand } from '../commands/spec.js';
 import { ChangeCommand } from '../commands/change.js';
 import { ValidateCommand } from '../commands/validate.js';
@@ -78,12 +78,15 @@ program
     }
 });
 program
-    .command('diff [change-name]')
-    .description('Show differences between proposed spec changes and current specs (includes validation warnings)')
-    .action(async (changeName) => {
+    .command('list')
+    .description('List items (changes by default). Use --specs to list specs.')
+    .option('--specs', 'List specs instead of changes')
+    .option('--changes', 'List changes explicitly (default)')
+    .action(async (options) => {
     try {
-        const diffCommand = new DiffCommand();
-        await diffCommand.execute(changeName);
+        const listCommand = new ListCommand();
+        const mode = options?.specs ? 'specs' : 'changes';
+        await listCommand.execute('.', mode);
     }
     catch (error) {
         console.log(); // Empty line for spacing
@@ -92,15 +95,12 @@ program
     }
 });
 program
-    .command('list')
-    .description('List items (changes by default). Use --specs to list specs.')
-    .option('--specs', 'List specs instead of changes')
-    .option('--changes', 'List changes explicitly (default)')
-    .action(async (options) => {
+    .command('view')
+    .description('Display an interactive dashboard of specs and changes')
+    .action(async () => {
     try {
-        const listCommand = new ListCommand();
-        const mode = options?.specs ? 'specs' : 'changes';
-        await listCommand.execute('.', mode);
+        const viewCommand = new ViewCommand();
+        await viewCommand.execute('.');
     }
     catch (error) {
         console.log(); // Empty line for spacing

package/dist/core/config.js

@@ -5,7 +5,7 @@ export const OPENSPEC_MARKERS = {
 };
 export const AI_TOOLS = [
     { name: 'Claude Code', value: 'claude', available: true },
-    { name: 'Cursor', value: 'cursor', available: false },
+    { name: 'Cursor', value: 'cursor', available: true },
     { name: 'Aider', value: 'aider', available: false },
     { name: 'Continue', value: 'continue', available: false }
 ];

package/dist/core/configurators/slash/base.d.ts

@@ -0,0 +1,17 @@
+import { SlashCommandId } from '../../templates/index.js';
+export interface SlashCommandTarget {
+    id: SlashCommandId;
+    path: string;
+    kind: 'slash';
+}
+export declare abstract class SlashCommandConfigurator {
+    abstract readonly toolId: string;
+    abstract readonly isAvailable: boolean;
+    getTargets(): SlashCommandTarget[];
+    generateAll(projectPath: string, _openspecDir: string): Promise<string[]>;
+    updateExisting(projectPath: string, _openspecDir: string): Promise<string[]>;
+    protected abstract getRelativePath(id: SlashCommandId): string;
+    protected abstract getFrontmatter(id: SlashCommandId): string | undefined;
+    private updateBody;
+}
+//# sourceMappingURL=base.d.ts.map

package/dist/core/configurators/slash/base.js

@@ -0,0 +1,61 @@
+import path from 'path';
+import { FileSystemUtils } from '../../../utils/file-system.js';
+import { TemplateManager } from '../../templates/index.js';
+import { OPENSPEC_MARKERS } from '../../config.js';
+const ALL_COMMANDS = ['proposal', 'apply', 'archive'];
+export class SlashCommandConfigurator {
+    getTargets() {
+        return ALL_COMMANDS.map((id) => ({
+            id,
+            path: this.getRelativePath(id),
+            kind: 'slash'
+        }));
+    }
+    async generateAll(projectPath, _openspecDir) {
+        const createdOrUpdated = [];
+        for (const target of this.getTargets()) {
+            const body = TemplateManager.getSlashCommandBody(target.id).trim();
+            const filePath = path.join(projectPath, target.path);
+            if (await FileSystemUtils.fileExists(filePath)) {
+                await this.updateBody(filePath, body);
+            }
+            else {
+                const frontmatter = this.getFrontmatter(target.id);
+                const sections = [];
+                if (frontmatter) {
+                    sections.push(frontmatter.trim());
+                }
+                sections.push(`${OPENSPEC_MARKERS.start}\n${body}\n${OPENSPEC_MARKERS.end}`);
+                const content = sections.join('\n') + '\n';
+                await FileSystemUtils.writeFile(filePath, content);
+            }
+            createdOrUpdated.push(target.path);
+        }
+        return createdOrUpdated;
+    }
+    async updateExisting(projectPath, _openspecDir) {
+        const updated = [];
+        for (const target of this.getTargets()) {
+            const filePath = path.join(projectPath, target.path);
+            if (await FileSystemUtils.fileExists(filePath)) {
+                const body = TemplateManager.getSlashCommandBody(target.id).trim();
+                await this.updateBody(filePath, body);
+                updated.push(target.path);
+            }
+        }
+        return updated;
+    }
+    async updateBody(filePath, body) {
+        const content = await FileSystemUtils.readFile(filePath);
+        const startIndex = content.indexOf(OPENSPEC_MARKERS.start);
+        const endIndex = content.indexOf(OPENSPEC_MARKERS.end);
+        if (startIndex === -1 || endIndex === -1 || endIndex <= startIndex) {
+            throw new Error(`Missing OpenSpec markers in ${filePath}`);
+        }
+        const before = content.slice(0, startIndex + OPENSPEC_MARKERS.start.length);
+        const after = content.slice(endIndex);
+        const updatedContent = `${before}\n${body}\n${after}`;
+        await FileSystemUtils.writeFile(filePath, updatedContent);
+    }
+}
+//# sourceMappingURL=base.js.map

package/dist/core/configurators/slash/claude.d.ts

@@ -0,0 +1,9 @@
+import { SlashCommandConfigurator } from './base.js';
+import { SlashCommandId } from '../../templates/index.js';
+export declare class ClaudeSlashCommandConfigurator extends SlashCommandConfigurator {
+    readonly toolId = "claude";
+    readonly isAvailable = true;
+    protected getRelativePath(id: SlashCommandId): string;
+    protected getFrontmatter(id: SlashCommandId): string;
+}
+//# sourceMappingURL=claude.d.ts.map

package/dist/core/configurators/slash/claude.js

@@ -0,0 +1,37 @@
+import { SlashCommandConfigurator } from './base.js';
+const FILE_PATHS = {
+    proposal: '.claude/commands/openspec/proposal.md',
+    apply: '.claude/commands/openspec/apply.md',
+    archive: '.claude/commands/openspec/archive.md'
+};
+const FRONTMATTER = {
+    proposal: `---
+name: OpenSpec: Proposal
+description: Scaffold a new OpenSpec change and validate strictly.
+category: OpenSpec
+tags: [openspec, change]
+---`,
+    apply: `---
+name: OpenSpec: Apply
+description: Implement an approved OpenSpec change and keep tasks in sync.
+category: OpenSpec
+tags: [openspec, apply]
+---`,
+    archive: `---
+name: OpenSpec: Archive
+description: Archive a deployed OpenSpec change and update specs.
+category: OpenSpec
+tags: [openspec, archive]
+---`
+};
+export class ClaudeSlashCommandConfigurator extends SlashCommandConfigurator {
+    toolId = 'claude';
+    isAvailable = true;
+    getRelativePath(id) {
+        return FILE_PATHS[id];
+    }
+    getFrontmatter(id) {
+        return FRONTMATTER[id];
+    }
+}
+//# sourceMappingURL=claude.js.map

package/dist/core/configurators/slash/cursor.d.ts

@@ -0,0 +1,9 @@
+import { SlashCommandConfigurator } from './base.js';
+import { SlashCommandId } from '../../templates/index.js';
+export declare class CursorSlashCommandConfigurator extends SlashCommandConfigurator {
+    readonly toolId = "cursor";
+    readonly isAvailable = true;
+    protected getRelativePath(id: SlashCommandId): string;
+    protected getFrontmatter(id: SlashCommandId): string;
+}
+//# sourceMappingURL=cursor.d.ts.map

package/dist/core/configurators/slash/cursor.js

@@ -0,0 +1,37 @@
+import { SlashCommandConfigurator } from './base.js';
+const FILE_PATHS = {
+    proposal: '.cursor/commands/openspec-proposal.md',
+    apply: '.cursor/commands/openspec-apply.md',
+    archive: '.cursor/commands/openspec-archive.md'
+};
+const FRONTMATTER = {
+    proposal: `---
+name: /openspec-proposal
+id: openspec-proposal
+category: OpenSpec
+description: Scaffold a new OpenSpec change and validate strictly.
+---`,
+    apply: `---
+name: /openspec-apply
+id: openspec-apply
+category: OpenSpec
+description: Implement an approved OpenSpec change and keep tasks in sync.
+---`,
+    archive: `---
+name: /openspec-archive
+id: openspec-archive
+category: OpenSpec
+description: Archive a deployed OpenSpec change and update specs.
+---`
+};
+export class CursorSlashCommandConfigurator extends SlashCommandConfigurator {
+    toolId = 'cursor';
+    isAvailable = true;
+    getRelativePath(id) {
+        return FILE_PATHS[id];
+    }
+    getFrontmatter(id) {
+        return FRONTMATTER[id];
+    }
+}
+//# sourceMappingURL=cursor.js.map

package/dist/core/configurators/slash/registry.d.ts

@@ -0,0 +1,8 @@
+import { SlashCommandConfigurator } from './base.js';
+export declare class SlashCommandRegistry {
+    private static configurators;
+    static register(configurator: SlashCommandConfigurator): void;
+    static get(toolId: string): SlashCommandConfigurator | undefined;
+    static getAll(): SlashCommandConfigurator[];
+}
+//# sourceMappingURL=registry.d.ts.map

package/dist/core/configurators/slash/registry.js

@@ -0,0 +1,21 @@
+import { ClaudeSlashCommandConfigurator } from './claude.js';
+import { CursorSlashCommandConfigurator } from './cursor.js';
+export class SlashCommandRegistry {
+    static configurators = new Map();
+    static {
+        const claude = new ClaudeSlashCommandConfigurator();
+        const cursor = new CursorSlashCommandConfigurator();
+        this.configurators.set(claude.toolId, claude);
+        this.configurators.set(cursor.toolId, cursor);
+    }
+    static register(configurator) {
+        this.configurators.set(configurator.toolId, configurator);
+    }
+    static get(toolId) {
+        return this.configurators.get(toolId);
+    }
+    static getAll() {
+        return Array.from(this.configurators.values());
+    }
+}
+//# sourceMappingURL=registry.js.map