@mind-fold/open-flow 0.1.15 → 0.1.17

package/dist/configurators/templates.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"templates.d.ts","sourceRoot":"","sources":["../../src/configurators/templates.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAmBH,MAAM,WAAW,gBAAgB;IAChC,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAAC;CACtB;AAED,wBAAgB,mBAAmB,IAAI,gBAAgB,CAiBtD"}
+{"version":3,"file":"templates.d.ts","sourceRoot":"","sources":["../../src/configurators/templates.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAqBH,MAAM,WAAW,gBAAgB;IAChC,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAAC;CACtB;AAED,wBAAgB,mBAAmB,IAAI,gBAAgB,CAmBtD"}

package/dist/configurators/templates.js

@@ -2,7 +2,7 @@
  * Short command templates for AI assistants
  * These are the core commands that enable AI-assisted development workflow
  */
-import { initAgentTemplate, checkFrontendTemplate, checkBackendTemplate, recordAgentFlowTemplate, recordQuestionTemplate, onboardDeveloperTemplate, generateFrontendStructureTemplate, generateBackendStructureTemplate, beforeFrontendDevTemplate, beforeBackendDevTemplate, updateFrontendStructureTemplate, updateBackendStructureTemplate, createCommandTemplate, integrateSkillTemplate, } from "../templates/commands/index.js";
+import { initAgentTemplate, checkFrontendTemplate, checkBackendTemplate, recordAgentFlowTemplate, recordQuestionTemplate, onboardDeveloperTemplate, generateFrontendStructureTemplate, generateBackendStructureTemplate, beforeFrontendDevTemplate, beforeBackendDevTemplate, updateFrontendStructureTemplate, updateBackendStructureTemplate, createCommandTemplate, integrateSkillTemplate, extractLlmDocsTemplate, extractToRulesTemplate, } from "../templates/commands/index.js";
 export function getCommandTemplates() {
     return {
         "init-agent": initAgentTemplate,
@@ -19,6 +19,8 @@ export function getCommandTemplates() {
         "update-backend-structure": updateBackendStructureTemplate,
         "create-command": createCommandTemplate,
         "integrate-skill": integrateSkillTemplate,
+        "extract-llm-docs": extractLlmDocsTemplate,
+        "extract-to-rules": extractToRulesTemplate,
     };
 }
 //# sourceMappingURL=templates.js.map

package/dist/configurators/templates.js.map

@@ -1 +1 @@
-{"version":3,"file":"templates.js","sourceRoot":"","sources":["../../src/configurators/templates.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EACN,iBAAiB,EACjB,qBAAqB,EACrB,oBAAoB,EACpB,uBAAuB,EACvB,sBAAsB,EACtB,wBAAwB,EACxB,iCAAiC,EACjC,gCAAgC,EAChC,yBAAyB,EACzB,wBAAwB,EACxB,+BAA+B,EAC/B,8BAA8B,EAC9B,qBAAqB,EACrB,sBAAsB,GACtB,MAAM,gCAAgC,CAAC;AAMxC,MAAM,UAAU,mBAAmB;IAClC,OAAO;QACN,YAAY,EAAE,iBAAiB;QAC/B,gBAAgB,EAAE,qBAAqB;QACvC,eAAe,EAAE,oBAAoB;QACrC,mBAAmB,EAAE,uBAAuB;QAC5C,iBAAiB,EAAE,sBAAsB;QACzC,mBAAmB,EAAE,wBAAwB;QAC7C,6BAA6B,EAAE,iCAAiC;QAChE,4BAA4B,EAAE,gCAAgC;QAC9D,qBAAqB,EAAE,yBAAyB;QAChD,oBAAoB,EAAE,wBAAwB;QAC9C,2BAA2B,EAAE,+BAA+B;QAC5D,0BAA0B,EAAE,8BAA8B;QAC1D,gBAAgB,EAAE,qBAAqB;QACvC,iBAAiB,EAAE,sBAAsB;KACzC,CAAC;AACH,CAAC"}
+{"version":3,"file":"templates.js","sourceRoot":"","sources":["../../src/configurators/templates.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EACN,iBAAiB,EACjB,qBAAqB,EACrB,oBAAoB,EACpB,uBAAuB,EACvB,sBAAsB,EACtB,wBAAwB,EACxB,iCAAiC,EACjC,gCAAgC,EAChC,yBAAyB,EACzB,wBAAwB,EACxB,+BAA+B,EAC/B,8BAA8B,EAC9B,qBAAqB,EACrB,sBAAsB,EACtB,sBAAsB,EACtB,sBAAsB,GACtB,MAAM,gCAAgC,CAAC;AAMxC,MAAM,UAAU,mBAAmB;IAClC,OAAO;QACN,YAAY,EAAE,iBAAiB;QAC/B,gBAAgB,EAAE,qBAAqB;QACvC,eAAe,EAAE,oBAAoB;QACrC,mBAAmB,EAAE,uBAAuB;QAC5C,iBAAiB,EAAE,sBAAsB;QACzC,mBAAmB,EAAE,wBAAwB;QAC7C,6BAA6B,EAAE,iCAAiC;QAChE,4BAA4B,EAAE,gCAAgC;QAC9D,qBAAqB,EAAE,yBAAyB;QAChD,oBAAoB,EAAE,wBAAwB;QAC9C,2BAA2B,EAAE,+BAA+B;QAC5D,0BAA0B,EAAE,8BAA8B;QAC1D,gBAAgB,EAAE,qBAAqB;QACvC,iBAAiB,EAAE,sBAAsB;QACzC,kBAAkB,EAAE,sBAAsB;QAC1C,kBAAkB,EAAE,sBAAsB;KAC1C,CAAC;AACH,CAAC"}

package/dist/templates/commands/extract-llm-docs.txt

@@ -0,0 +1,218 @@
+# Extract Development Guidelines from LLM Documents
+
+Extract development guidelines from external service llms.txt or other LLM-friendly documentation and integrate them into your project's structure documentation.
+
+## Usage
+
+```
+/extract-llm-docs <url-or-service-name>
+```
+
+**Examples**:
+```
+/extract-llm-docs https://docs.stripe.com/llms.txt
+/extract-llm-docs vercel
+/extract-llm-docs https://supabase.com/llms.txt
+```
+
+## Core Principle
+
+> ⚠️ **Important**: The extracted content should be **development guidelines**, not direct project code.
+>
+> - Guidelines content → Write to `workflow/structure/{target}/doc.md`
+> - Code examples → Place in `workflow/structure/{target}/examples/services/<service-name>/`
+> - Example files → Use `.template` suffix to avoid IDE errors
+>
+> Where `{target}` is `frontend` or `backend`, determined by service type.
+
+## Execution Steps
+
+### 1. Fetch LLM Documentation
+
+**Method A: Direct URL**
+```bash
+curl <url>
+```
+
+**Method B: Common service llms.txt locations**
+
+| Service | llms.txt URL |
+|---------|-------------|
+| Vercel | `https://vercel.com/llms.txt` |
+| Supabase | `https://supabase.com/llms.txt` |
+| Stripe | `https://docs.stripe.com/llms.txt` |
+| Cloudflare | `https://developers.cloudflare.com/llms.txt` |
+| Resend | `https://resend.com/llms.txt` |
+
+**Method C: Guess URL**
+```
+https://<service>.com/llms.txt
+https://docs.<service>.com/llms.txt
+https://developers.<service>.com/llms.txt
+```
+
+### 2. Parse Document Structure
+
+llms.txt standard format:
+```markdown
+# Project Name
+
+> Brief description
+
+## Core Documentation
+- [Quick Start](url): Getting started guide
+- [API Reference](url): API documentation
+
+## Optional
+- [Blog](url): Optional content
+```
+
+### 3. Determine Integration Target
+
+Based on service type, determine where to write:
+
+| Service Type | Integration Target |
+|--------------|-------------------|
+| UI components (shadcn, radix) | `workflow/structure/frontend/` |
+| Backend services (supabase, stripe) | `workflow/structure/backend/` |
+| Full-stack frameworks (vercel, next.js) | May involve both |
+| Email services (resend) | `workflow/structure/backend/` |
+| Storage services (cloudflare r2) | `workflow/structure/backend/` |
+
+### 4. Extract Key Guidelines
+
+Extract the following from documentation:
+
+| Category | Content to Extract |
+|----------|-------------------|
+| **Initialization** | Install commands, configuration methods |
+| **Core API** | Main function/method usage patterns |
+| **Type Definitions** | TypeScript type import methods |
+| **Best Practices** | Recommended usage patterns |
+| **Common Errors** | Error handling, edge cases |
+| **Project Adaptation** | How to integrate with existing project conventions |
+
+### 5. Execute Integration
+
+#### 5.1 Update Guidelines Document
+
+Add a new section to the corresponding `doc.md`:
+
+```markdown
+@@@section:service-<service-name>
+## 🔌 <Service Name> Integration Guide
+
+### Overview
+[Core functionality and use cases of the service]
+
+### Installation & Configuration
+[Install commands and environment configuration]
+
+### Usage Patterns
+
+#### Basic Usage
+[Code examples]
+
+#### Advanced Usage
+[Code examples]
+
+### Type Definitions
+[How to import and use types]
+
+### Error Handling
+[Common errors and how to handle them]
+
+### Project Adaptation
+- [Integration points with existing conventions]
+- [Notable differences to be aware of]
+
+### Reference Examples
+See `examples/services/<service-name>/`
+
+### External Documentation
+- [Official Docs](url)
+
+@@@/section:service-<service-name>
+```
+
+#### 5.2 Create Examples Directory (if code examples exist)
+
+```bash
+workflow/structure/{target}/
+├── doc.md                      # Add service-related section
+├── index.md                    # Update index
+└── examples/
+    └── services/
+        └── <service-name>/
+            ├── README.md               # Example documentation
+            ├── basic-usage.ts.template
+            └── advanced-usage.ts.template
+```
+
+#### 5.3 Update Index File
+
+Add to the Quick Navigation table in `index.md`:
+
+```markdown
+| Using <Service> | <Section name> | `service-<service-name>` |
+```
+
+### 6. Generate Integration Report
+
+---
+
+## LLM Document Extraction Report: `<service-name>`
+
+### 📋 Source
+- **Document URL**: [llms.txt](url)
+- **Service Type**: [Frontend/Backend/Full-stack]
+- **Integration Target**: `workflow/structure/{target}/`
+
+### 📚 Extracted Content
+
+| Category | Content |
+|----------|---------|
+| Initialization | [Install and config methods] |
+| Core API | [Main usage patterns] |
+| Type Definitions | [Type import methods] |
+| Best Practices | [Recommended approaches] |
+
+### 📁 Integration Locations
+
+| Type | Path |
+|------|------|
+| Guidelines doc | `workflow/structure/{target}/doc.md` (section: `service-<name>`) |
+| Code examples | `workflow/structure/{target}/examples/services/<name>/` |
+| Index update | `workflow/structure/{target}/index.md` |
+
+### ✅ Completed Changes
+
+- [ ] Added `@@@section:service-<name>` section to `doc.md`
+- [ ] Added index entry to `index.md`
+- [ ] Created example files in `examples/services/<name>/`
+- [ ] Example files use `.template` suffix
+
+### 🔗 External Links
+
+- [Official Documentation](url)
+- [API Reference](url)
+
+---
+
+## Common Services Reference
+
+| Service | Type | llms.txt |
+|---------|------|----------|
+| Vercel | Deployment | `vercel.com/llms.txt` |
+| Supabase | Backend | `supabase.com/llms.txt` |
+| Stripe | Payments | `docs.stripe.com/llms.txt` |
+| Resend | Email | `resend.com/llms.txt` |
+| Cloudflare | CDN/Storage | `developers.cloudflare.com/llms.txt` |
+| Upstash | Redis/Kafka | `upstash.com/llms.txt` |
+
+## Notes
+
+1. **Prefer llms.txt**: More concise than full documentation, better suited for LLM context
+2. **Focus on relevant content**: Only extract parts related to your project's tech stack
+3. **Avoid duplication**: Check if a related section already exists before adding
+4. **Keep updated**: Record document version or date for future updates

package/dist/templates/commands/extract-to-rules.txt

@@ -0,0 +1,433 @@
+# Extract Knowledge to Development Rules
+
+Extract knowledge from a source document and integrate it **completely** into the corresponding development guidelines (`frontend` or `backend` structure).
+
+## Usage
+
+```
+/extract-to-rules <source-file-path> <target: frontend|backend>
+```
+
+**Examples**:
+```
+/extract-to-rules docs/api-module-pattern.md backend
+/extract-to-rules docs/react-hooks-guide.md frontend
+/extract-to-rules workflow/big-question/turbopack-webpack-flexbox.md frontend
+```
+
+---
+
+## Execution Steps
+
+### Step 1: Validate Input
+
+1. Check source file exists
+2. Validate target is either `frontend` or `backend`
+3. Determine target paths:
+   - Frontend: `workflow/structure/frontend/`
+   - Backend: `workflow/structure/backend/`
+
+### Step 2: Read and Analyze Source Document
+
+**Read the source document COMPLETELY**:
+```bash
+cat <source-file-path>
+```
+
+**Analyze and extract**:
+- [ ] Main topic/concept
+- [ ] All key patterns/practices
+- [ ] All code examples (DO NOT skip any)
+- [ ] All rules/constraints
+- [ ] All common mistakes/anti-patterns
+- [ ] All reference links/files
+- [ ] All edge cases/gotchas
+
+**⚠️ CRITICAL**: Extract **EVERYTHING** - do not summarize or omit details!
+
+### Step 3: Determine Integration Target
+
+Based on the content, determine where to add in the guideline structure:
+
+**For Frontend**:
+- Component patterns → Add to "Component Development" section
+- Hook patterns → Add to "Hook Guidelines" section
+- State management → Add to "State Management" section
+- Performance tips → Add to "Performance Optimization" section
+- New category → Create new section
+
+**For Backend**:
+- API patterns → Add to "Directory Structure" section
+- Database patterns → Add to "Database Operations" section
+- Type safety → Add to "Type Safety" section
+- Performance patterns → Add to "Performance Patterns" section
+- New category → Create new section
+
+**Decision Rules**:
+1. If content fits existing section → Add as subsection
+2. If content is new domain → Create new top-level section
+3. If content has multiple aspects → Consider splitting
+
+### Step 4: Read Current Guidelines
+
+**Read the current index**:
+```bash
+cat workflow/structure/<target>/index.md
+```
+
+**Read the current doc** (to understand structure):
+```bash
+cat workflow/structure/<target>/doc.md
+```
+
+**Identify**:
+- [ ] Existing sections and their line numbers
+- [ ] Section ID naming pattern
+- [ ] Appropriate insertion point
+- [ ] Potential conflicts/duplications
+
+### Step 5: Prepare New Content
+
+**Create section ID**:
+- Use pattern: `kebab-case-descriptive-name`
+- Examples: `api-module-pattern`, `react-hooks-advanced`, `cursor-pagination-best-practices`
+
+**Structure the content** (follow existing format):
+
+```markdown
+@@@section:<section-id>
+## <emoji> Section Title
+
+### Subsection 1
+<content>
+
+### Subsection 2
+<content>
+
+**Examples**:
+<code-examples>
+
+**Anti-Patterns**:
+<anti-patterns>
+
+**Reference**:
+<references>
+
+@@@/section:<section-id>
+```
+
+**⚠️ IMPORTANT**:
+1. Include ALL examples from source
+2. Include ALL code snippets from source
+3. Include ALL best practices from source
+4. Include ALL anti-patterns from source
+5. Preserve all technical details
+6. Add section markers (`@@@section` / `@@@/section`)
+
+### Step 6: Update index.md
+
+**Add to Quick Navigation table**:
+
+| Section | Key Content | Section ID |
+|---------|-------------|------------|
+| <emoji> <Title> | <brief-description> | `<section-id>` |
+
+**Add to appropriate scenario** (if applicable):
+
+### Scenario X: <scenario-name>
+- **Must Read**: <emoji> <Title> (`<section-id>`)
+- **Reference**: ...
+
+**Add to Core Rules** (if applicable):
+
+| Rule | Section ID |
+|------|------------|
+| **<rule-summary>** | `<section-id>` |
+
+**Update Document Structure Overview**:
+
+```
+<target>/doc.md (approx. XXXX lines)
+├── ...
+├── <emoji> <Title> (`<section-id>`)
+│   ├── Subsection 1 (`<subsection-id>`)
+│   └── Subsection 2 (`<subsection-id>`)
+└── ...
+```
+
+### Step 7: Update doc.md
+
+**Insert new section at appropriate location**:
+
+1. Find insertion point (after related sections, before reference examples)
+2. Add complete section with all markers
+3. Ensure proper nesting and formatting
+
+**Template**:
+```markdown
+@@@section:<section-id>
+## <emoji> Section Title
+
+<overview-paragraph>
+
+@@@section:<subsection-id-1>
+### Subsection 1
+
+<detailed-content>
+
+**Example**:
+```<language>
+<code-example>
+```
+
+**Why?**
+- <reason-1>
+- <reason-2>
+
+@@@/section:<subsection-id-1>
+
+@@@section:<subsection-id-2>
+### Subsection 2
+
+<detailed-content>
+
+**Anti-Pattern** ❌:
+```<language>
+<bad-code>
+```
+
+**Correct** ✅:
+```<language>
+<good-code>
+```
+
+@@@/section:<subsection-id-2>
+
+@@@/section:<section-id>
+```
+
+### Step 8: Verify Integration
+
+**Check completeness**:
+- [ ] All content from source is included
+- [ ] All code examples are preserved
+- [ ] All anti-patterns are included
+- [ ] All references are added
+- [ ] Section markers are correct (`@@@section` / `@@@/section`)
+- [ ] Index is updated with new section
+- [ ] Scenarios are updated (if relevant)
+- [ ] Core rules are updated (if relevant)
+- [ ] Document structure overview is updated
+
+**Check formatting**:
+- [ ] Consistent emoji usage
+- [ ] Proper markdown formatting
+- [ ] Code blocks have language tags
+- [ ] Section IDs are kebab-case
+- [ ] Proper nesting (subsections inside main section)
+
+**Check no duplication**:
+- [ ] No existing section covers the same content
+- [ ] No conflicting guidelines
+- [ ] Merged with existing section if overlap
+
+### Step 9: Test Extraction
+
+**Verify section can be extracted**:
+```bash
+sed -n '/@@@section:<section-id>/,/@@@\/section:<section-id>/p' workflow/structure/<target>/doc.md
+```
+
+Expected: Complete section content is displayed
+
+### Step 10: Create Summary
+
+Output a summary:
+
+```markdown
+✅ Knowledge Extracted and Integrated
+
+**Source**: <source-file-path>
+**Target**: workflow/structure/<target>/
+
+**New Section**:
+- Section ID: `<section-id>`
+- Title: <emoji> <title>
+- Location: Line XXX in doc.md
+
+**Updates**:
+- ✅ index.md - Added to Quick Navigation
+- ✅ index.md - Added to Scenario X
+- ✅ index.md - Added to Core Rules
+- ✅ index.md - Updated Document Structure
+- ✅ doc.md - Added complete section with X subsections
+
+**Content Included**:
+- X paragraphs of explanation
+- X code examples
+- X anti-patterns
+- X best practices
+- X references
+
+**Extraction Command**:
+```bash
+sed -n '/@@@section:<section-id>/,/@@@\/section:<section-id>/p' workflow/structure/<target>/doc.md
+```
+```
+
+---
+
+## Critical Rules
+
+### ✅ DO
+
+1. **Extract EVERYTHING** from source document
+   - All explanations
+   - All code examples
+   - All edge cases
+   - All anti-patterns
+   - All references
+
+2. **Follow existing format**
+   - Use same emoji style
+   - Use same heading levels
+   - Use same code block format
+   - Use section markers
+
+3. **Update ALL affected parts**
+   - index.md Quick Navigation
+   - index.md Scenarios (if applicable)
+   - index.md Core Rules (if applicable)
+   - index.md Document Structure
+   - doc.md new section
+
+4. **Preserve technical accuracy**
+   - Keep exact code examples
+   - Keep exact error messages
+   - Keep exact command syntax
+
+5. **Make it searchable**
+   - Use descriptive section IDs
+   - Include keywords in content
+   - Add to relevant scenarios
+
+### ❌ DON'T
+
+1. **Don't summarize** - Extract complete content
+2. **Don't skip examples** - Include all code examples
+3. **Don't omit details** - Keep all technical specifics
+4. **Don't forget markers** - Always add `@@@section` tags
+5. **Don't skip index** - Always update index.md
+6. **Don't duplicate** - Check for existing similar content first
+
+---
+
+## Examples
+
+### Example 1: Adding API Module Pattern to Backend
+
+**Input**:
+```
+/extract-to-rules docs/api-module-pattern.md backend
+```
+
+**Process**:
+1. Read `docs/api-module-pattern.md` completely
+2. Analyze: This is about directory structure and organization
+3. Determine: Should enhance "Directory Structure" section
+4. Read current backend structure guidelines
+5. Create section ID: `api-module-pattern-detailed`
+6. Extract all content, examples, anti-patterns
+7. Update index.md:
+   - Add to Quick Navigation
+   - Add to Scenario 1 (Create New API Module)
+   - Update Document Structure
+8. Update doc.md:
+   - Insert after existing Directory Structure
+   - Add all subsections with markers
+9. Verify extraction works
+10. Output summary
+
+### Example 2: Adding React Hook Pattern to Frontend
+
+**Input**:
+```
+/extract-to-rules docs/react-hooks-advanced.md frontend
+```
+
+**Process**:
+1. Read `docs/react-hooks-advanced.md` completely
+2. Analyze: Advanced hook patterns and best practices
+3. Determine: Should add to "Hook Guidelines" section
+4. Read current frontend structure guidelines
+5. Create section ID: `hook-patterns-advanced`
+6. Extract all patterns, examples, gotchas
+7. Update index.md:
+   - Add to Quick Navigation
+   - Add to Scenario (Hook Development)
+   - Add key rules to Core Rules
+   - Update Document Structure
+8. Update doc.md:
+   - Add new subsection under Hook Guidelines
+   - Include all examples and anti-patterns
+9. Verify extraction works
+10. Output summary
+
+---
+
+## Quality Checklist
+
+Before completing, verify:
+
+- [ ] Source document read COMPLETELY
+- [ ] ALL content extracted (not summarized)
+- [ ] ALL code examples included
+- [ ] ALL anti-patterns included
+- [ ] Section ID is descriptive and unique
+- [ ] Section markers added (`@@@section` / `@@@/section`)
+- [ ] index.md Quick Navigation updated
+- [ ] index.md Scenarios updated (if relevant)
+- [ ] index.md Core Rules updated (if relevant)
+- [ ] index.md Document Structure updated
+- [ ] doc.md section added with proper formatting
+- [ ] No duplication with existing content
+- [ ] Extraction command tested and works
+- [ ] Summary provided with all details
+
+---
+
+## Troubleshooting
+
+### Issue: Content already exists
+
+**Solution**:
+1. Compare with existing section
+2. If identical → Skip, note in summary
+3. If complementary → Merge into existing section
+4. If different approach → Add as alternative pattern
+
+### Issue: Too much content
+
+**Solution**:
+1. Split into multiple related sections
+2. Use clear subsection hierarchy
+3. Link sections together in index
+
+### Issue: Unclear target section
+
+**Solution**:
+1. Create new top-level section
+2. Add clear description of scope
+3. Update index with new category
+
+---
+
+## Success Criteria
+
+Integration is complete when:
+
+1. ✅ All source content is in doc.md
+2. ✅ Index.md accurately reflects new content
+3. ✅ Section can be extracted with sed command
+4. ✅ New developers can find and use the knowledge
+5. ✅ No information loss from source document

package/dist/templates/commands/index.d.ts

@@ -16,4 +16,6 @@ export declare const updateFrontendStructureTemplate: string;
 export declare const updateBackendStructureTemplate: string;
 export declare const createCommandTemplate: string;
 export declare const integrateSkillTemplate: string;
+export declare const extractLlmDocsTemplate: string;
+export declare const extractToRulesTemplate: string;
 //# sourceMappingURL=index.d.ts.map

package/dist/templates/commands/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/commands/index.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAIH,eAAO,MAAM,iBAAiB,QAAgC,CAAC;AAC/D,eAAO,MAAM,qBAAqB,QAAoC,CAAC;AACvE,eAAO,MAAM,oBAAoB,QAAmC,CAAC;AACrE,eAAO,MAAM,uBAAuB,QAAuC,CAAC;AAC5E,eAAO,MAAM,sBAAsB,QAAqC,CAAC;AACzE,eAAO,MAAM,wBAAwB,QAAuC,CAAC;AAC7E,eAAO,MAAM,iCAAiC,QAE7C,CAAC;AACF,eAAO,MAAM,gCAAgC,QAE5C,CAAC;AACF,eAAO,MAAM,yBAAyB,QAAyC,CAAC;AAChF,eAAO,MAAM,wBAAwB,QAAwC,CAAC;AAC9E,eAAO,MAAM,+BAA+B,QAE3C,CAAC;AACF,eAAO,MAAM,8BAA8B,QAE1C,CAAC;AACF,eAAO,MAAM,qBAAqB,QAAoC,CAAC;AACvE,eAAO,MAAM,sBAAsB,QAAqC,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/commands/index.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAIH,eAAO,MAAM,iBAAiB,QAAgC,CAAC;AAC/D,eAAO,MAAM,qBAAqB,QAAoC,CAAC;AACvE,eAAO,MAAM,oBAAoB,QAAmC,CAAC;AACrE,eAAO,MAAM,uBAAuB,QAAuC,CAAC;AAC5E,eAAO,MAAM,sBAAsB,QAAqC,CAAC;AACzE,eAAO,MAAM,wBAAwB,QAAuC,CAAC;AAC7E,eAAO,MAAM,iCAAiC,QAE7C,CAAC;AACF,eAAO,MAAM,gCAAgC,QAE5C,CAAC;AACF,eAAO,MAAM,yBAAyB,QAAyC,CAAC;AAChF,eAAO,MAAM,wBAAwB,QAAwC,CAAC;AAC9E,eAAO,MAAM,+BAA+B,QAE3C,CAAC;AACF,eAAO,MAAM,8BAA8B,QAE1C,CAAC;AACF,eAAO,MAAM,qBAAqB,QAAoC,CAAC;AACvE,eAAO,MAAM,sBAAsB,QAAqC,CAAC;AACzE,eAAO,MAAM,sBAAsB,QAAsC,CAAC;AAC1E,eAAO,MAAM,sBAAsB,QAAsC,CAAC"}

package/dist/templates/commands/index.js

@@ -17,4 +17,6 @@ export const updateFrontendStructureTemplate = readCommand("update-frontend-stru
 export const updateBackendStructureTemplate = readCommand("update-backend-structure.txt");
 export const createCommandTemplate = readCommand("create-command.txt");
 export const integrateSkillTemplate = readCommand("integrate-skill.txt");
+export const extractLlmDocsTemplate = readCommand("extract-llm-docs.txt");
+export const extractToRulesTemplate = readCommand("extract-to-rules.txt");
 //# sourceMappingURL=index.js.map

package/dist/templates/commands/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/commands/index.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAE5C,MAAM,CAAC,MAAM,iBAAiB,GAAG,WAAW,CAAC,gBAAgB,CAAC,CAAC;AAC/D,MAAM,CAAC,MAAM,qBAAqB,GAAG,WAAW,CAAC,oBAAoB,CAAC,CAAC;AACvE,MAAM,CAAC,MAAM,oBAAoB,GAAG,WAAW,CAAC,mBAAmB,CAAC,CAAC;AACrE,MAAM,CAAC,MAAM,uBAAuB,GAAG,WAAW,CAAC,uBAAuB,CAAC,CAAC;AAC5E,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC,qBAAqB,CAAC,CAAC;AACzE,MAAM,CAAC,MAAM,wBAAwB,GAAG,WAAW,CAAC,uBAAuB,CAAC,CAAC;AAC7E,MAAM,CAAC,MAAM,iCAAiC,GAAG,WAAW,CAC3D,iCAAiC,CACjC,CAAC;AACF,MAAM,CAAC,MAAM,gCAAgC,GAAG,WAAW,CAC1D,gCAAgC,CAChC,CAAC;AACF,MAAM,CAAC,MAAM,yBAAyB,GAAG,WAAW,CAAC,yBAAyB,CAAC,CAAC;AAChF,MAAM,CAAC,MAAM,wBAAwB,GAAG,WAAW,CAAC,wBAAwB,CAAC,CAAC;AAC9E,MAAM,CAAC,MAAM,+BAA+B,GAAG,WAAW,CACzD,+BAA+B,CAC/B,CAAC;AACF,MAAM,CAAC,MAAM,8BAA8B,GAAG,WAAW,CACxD,8BAA8B,CAC9B,CAAC;AACF,MAAM,CAAC,MAAM,qBAAqB,GAAG,WAAW,CAAC,oBAAoB,CAAC,CAAC;AACvE,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC,qBAAqB,CAAC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/commands/index.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,WAAW,EAAE,MAAM,eAAe,CAAC;AAE5C,MAAM,CAAC,MAAM,iBAAiB,GAAG,WAAW,CAAC,gBAAgB,CAAC,CAAC;AAC/D,MAAM,CAAC,MAAM,qBAAqB,GAAG,WAAW,CAAC,oBAAoB,CAAC,CAAC;AACvE,MAAM,CAAC,MAAM,oBAAoB,GAAG,WAAW,CAAC,mBAAmB,CAAC,CAAC;AACrE,MAAM,CAAC,MAAM,uBAAuB,GAAG,WAAW,CAAC,uBAAuB,CAAC,CAAC;AAC5E,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC,qBAAqB,CAAC,CAAC;AACzE,MAAM,CAAC,MAAM,wBAAwB,GAAG,WAAW,CAAC,uBAAuB,CAAC,CAAC;AAC7E,MAAM,CAAC,MAAM,iCAAiC,GAAG,WAAW,CAC3D,iCAAiC,CACjC,CAAC;AACF,MAAM,CAAC,MAAM,gCAAgC,GAAG,WAAW,CAC1D,gCAAgC,CAChC,CAAC;AACF,MAAM,CAAC,MAAM,yBAAyB,GAAG,WAAW,CAAC,yBAAyB,CAAC,CAAC;AAChF,MAAM,CAAC,MAAM,wBAAwB,GAAG,WAAW,CAAC,wBAAwB,CAAC,CAAC;AAC9E,MAAM,CAAC,MAAM,+BAA+B,GAAG,WAAW,CACzD,+BAA+B,CAC/B,CAAC;AACF,MAAM,CAAC,MAAM,8BAA8B,GAAG,WAAW,CACxD,8BAA8B,CAC9B,CAAC;AACF,MAAM,CAAC,MAAM,qBAAqB,GAAG,WAAW,CAAC,oBAAoB,CAAC,CAAC;AACvE,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC,qBAAqB,CAAC,CAAC;AACzE,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC,sBAAsB,CAAC,CAAC;AAC1E,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC,sBAAsB,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@mind-fold/open-flow",
-	"version": "0.1.15",
+	"version": "0.1.17",
 	"description": "AI-assisted development workflow initializer for Cursor, Claude Code and more",
 	"type": "module",
 	"main": "./dist/index.js",