@mind-fold/open-flow 0.2.11 → 0.2.12

package/dist/templates/commands/break-loop.txt

@@ -1,6 +1,6 @@
 # Break the Loop - Deep Bug Analysis
 
-When debug is complete, use this command for deep analysis to break the "fix bug → forget → repeat" cycle.
+When debug is complete, use this command for deep analysis to break the "fix bug -> forget -> repeat" cycle.
 
 ---
 

package/dist/templates/commands/check-cross-layer.txt

@@ -45,8 +45,8 @@ Based on your change type, execute relevant checks below:
 | Utility | `utils/`, `lib/` |
 
 **Checklist**:
-- [ ] Read flow: Database → Service → API → Hook → Component
-- [ ] Write flow: Component → Hook → API → Service → Database
+- [ ] Read flow: Database -> Service -> API -> Hook -> Component
+- [ ] Write flow: Component -> Hook -> API -> Service -> Database
 - [ ] Types correctly passed between layers?
 - [ ] Errors properly propagated to UI?
 - [ ] Loading states handled at each layer?
@@ -69,7 +69,7 @@ Based on your change type, execute relevant checks below:
   ```bash
   grep -r "value-to-change" --include="*.ts" --include="*.tsx"
   ```
-- [ ] If 2+ places define same value → Should extract to shared constant
+- [ ] If 2+ places define same value -> Should extract to shared constant
 - [ ] After modification, all usage sites updated?
 - [ ] If creating utility: Does similar utility already exist?
 

package/dist/templates/commands/create-command.txt

@@ -68,7 +68,7 @@ Create in both directories:
 
 Output result:
 ```
-✅ Created Slash Command: /<command-name>
+[OK] Created Slash Command: /<command-name>
 
 File paths:
 - .cursor/commands/<command-name>.md
@@ -83,14 +83,14 @@ Description:
 
 ## Command Content Guidelines
 
-### ✅ Good command content
+### [OK] Good command content
 
 1. **Clear and concise**: Immediately understandable
 2. **Executable**: AI can follow steps directly
 3. **Well-scoped**: Clear boundaries of what to do and not do
 4. **Has output**: Specifies expected output format (if needed)
 
-### ❌ Avoid
+### [X] Avoid
 
 1. **Too vague**: e.g., "optimize code"
 2. **Too complex**: Single command should not exceed 100 lines
@@ -146,8 +146,8 @@ Format:
 - [file list]
 
 ### Check Results
-- ✅ Passed items
-- ❌ Issues found
+- [OK] Passed items
+- [X] Issues found
 
 ### Suggestions
 - [improvement suggestions]

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

@@ -17,11 +17,11 @@ Extract development guidelines from external service llms.txt or other LLM-frien
 
 ## Core Principle
 
-> ⚠️ **Important**: The extracted content should be **development guidelines**, not direct project code.
+> [!] **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
+> - 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.
 
@@ -100,7 +100,7 @@ Add a new section to the corresponding `doc.md`:
 
 ```markdown
 @@@section:service-<service-name>
-## 🔌 <Service Name> Integration Guide
+## # <Service Name> Integration Guide
 
 ### Overview
 [Core functionality and use cases of the service]
@@ -139,14 +139,14 @@ See `examples/services/<service-name>/`
 
 ```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
+|-- 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
@@ -163,12 +163,12 @@ Add to the Quick Navigation table in `index.md`:
 
 ## LLM Document Extraction Report: `<service-name>`
 
-### 📋 Source
+### # Source
 - **Document URL**: [llms.txt](url)
 - **Service Type**: [Frontend/Backend/Full-stack]
 - **Integration Target**: `workflow/structure/{target}/`
 
-### 📚 Extracted Content
+### # Extracted Content
 
 | Category | Content |
 |----------|---------|
@@ -177,7 +177,7 @@ Add to the Quick Navigation table in `index.md`:
 | Type Definitions | [Type import methods] |
 | Best Practices | [Recommended approaches] |
 
-### 📁 Integration Locations
+### # Integration Locations
 
 | Type | Path |
 |------|------|
@@ -185,14 +185,14 @@ Add to the Quick Navigation table in `index.md`:
 | Code examples | `workflow/structure/{target}/examples/services/<name>/` |
 | Index update | `workflow/structure/{target}/index.md` |
 
-### ✅ Completed Changes
+### [OK] 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
+### # External Links
 
 - [Official Documentation](url)
 - [API Reference](url)

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

@@ -43,30 +43,30 @@ cat <source-file-path>
 - [ ] All reference links/files
 - [ ] All edge cases/gotchas
 
-**⚠️ CRITICAL**: Extract **EVERYTHING** - do not summarize or omit details!
+**[!] 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
+- 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
+- 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
+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
 
@@ -116,7 +116,7 @@ cat workflow/structure/<target>/doc.md
 @@@/section:<section-id>
 ```
 
-**⚠️ IMPORTANT**:
+**[!] IMPORTANT**:
 1. Include ALL examples from source
 2. Include ALL code snippets from source
 3. Include ALL best practices from source
@@ -148,11 +148,11 @@ cat workflow/structure/<target>/doc.md
 
 ```
 <target>/doc.md (approx. XXXX lines)
-├── ...
-├── <emoji> <Title> (`<section-id>`)
-│   ├── Subsection 1 (`<subsection-id>`)
-│   └── Subsection 2 (`<subsection-id>`)
-└── ...
+|-- ...
+|-- <emoji> <Title> (`<section-id>`)
+|   |-- Subsection 1 (`<subsection-id>`)
+|   \-- Subsection 2 (`<subsection-id>`)
+\-- ...
 ```
 
 ### Step 7: Update doc.md
@@ -191,12 +191,12 @@ cat workflow/structure/<target>/doc.md
 
 <detailed-content>
 
-**Anti-Pattern** ❌:
+**Anti-Pattern** [X]:
 ```<language>
 <bad-code>
 ```
 
-**Correct** ✅:
+**Correct** [OK]:
 ```<language>
 <good-code>
 ```
@@ -245,7 +245,7 @@ Expected: Complete section content is displayed
 Output a summary:
 
 ```markdown
-✅ Knowledge Extracted and Integrated
+[OK] Knowledge Extracted and Integrated
 
 **Source**: <source-file-path>
 **Target**: workflow/structure/<target>/
@@ -256,11 +256,11 @@ Output a summary:
 - 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
+- [OK] index.md - Added to Quick Navigation
+- [OK] index.md - Added to Scenario X
+- [OK] index.md - Added to Core Rules
+- [OK] index.md - Updated Document Structure
+- [OK] doc.md - Added complete section with X subsections
 
 **Content Included**:
 - X paragraphs of explanation
@@ -279,7 +279,7 @@ sed -n '/@@@section:<section-id>/,/@@@\/section:<section-id>/p' workflow/structu
 
 ## Critical Rules
 
-### ✅ DO
+### [OK] DO
 
 1. **Extract EVERYTHING** from source document
    - All explanations
@@ -311,7 +311,7 @@ sed -n '/@@@section:<section-id>/,/@@@\/section:<section-id>/p' workflow/structu
    - Include keywords in content
    - Add to relevant scenarios
 
-### ❌ DON'T
+### [X] DON'T
 
 1. **Don't summarize** - Extract complete content
 2. **Don't skip examples** - Include all code examples
@@ -402,9 +402,9 @@ Before completing, verify:
 
 **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
+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
 
@@ -426,8 +426,8 @@ Before completing, verify:
 
 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
+1. [OK] All source content is in doc.md
+2. [OK] Index.md accurately reflects new content
+3. [OK] Section can be extracted with sed command
+4. [OK] New developers can find and use the knowledge
+5. [OK] No information loss from source document

package/dist/templates/commands/finish-work.txt

@@ -37,7 +37,7 @@ pnpm test
 **Key Question**: 
 > "If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"
 
-If YES → Update the relevant structure doc.
+If YES -> Update the relevant structure doc.
 
 ### 3. API Changes
 
@@ -106,13 +106,13 @@ git diff --name-only
 
 ```
 Development Flow:
-  Write code → Test → /finish-work → git commit → /record-agent-flow
-                          ↑                              ↑
+  Write code -> Test -> /finish-work -> git commit -> /record-agent-flow
+                          |                              |
                    Ensure completeness              Record progress
                    
 Debug Flow:
-  Hit bug → Fix → /break-loop → Knowledge capture
-                       ↑
+  Hit bug -> Fix -> /break-loop -> Knowledge capture
+                       |
                   Deep analysis
 ```
 

package/dist/templates/commands/generate-backend-structure.txt

@@ -6,7 +6,7 @@ Scan the project's backend code, analyze existing code patterns and tech stack,
 
 ---
 
-## ⚠️ CRITICAL: Requirements
+## [!] CRITICAL: Requirements
 
 1. **Language**: All documentation must be written in **English**
 2. **Section Markers**: Use `@@@section:kebab-case-id` and `@@@/section:kebab-case-id` to mark sections
@@ -104,7 +104,7 @@ mkdir -p workflow/structure/backend
 These guidelines define the development standards and best practices for [Project Name] backend modules.
 
 @@@section:directory-structure
-## 📁 Directory Structure Guidelines
+## # Directory Structure Guidelines
 
 ### Module Organization
 [describe directory structure]
@@ -112,31 +112,31 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:directory-structure
 
 @@@section:type-safety
-## 🎯 Type Safety Guidelines
+## # Type Safety Guidelines
 
 @@@section:non-null-assertion
 ### 1. TypeScript Non-null Assertion Rules
 
 **Never use non-null assertion operator (`!`), use local variable extraction instead**
 
-#### ❌ Wrong Approach
+#### [X] Wrong Approach
 
 ```typescript
 if (user.profileId) {
   await db.update(profiles)
     .set({ name: newName })
-    .where(eq(profiles.id, user.profileId!)); // ❌ non-null assertion
+    .where(eq(profiles.id, user.profileId!)); // [X] non-null assertion
 }
 ```
 
-#### ✅ Correct Approach
+#### [OK] Correct Approach
 
 ```typescript
 if (user.profileId) {
   const profileId = user.profileId; // type narrowed to string
   await db.update(profiles)
     .set({ name: newName })
-    .where(eq(profiles.id, profileId)); // ✅ type safe
+    .where(eq(profiles.id, profileId)); // [OK] type safe
 }
 ```
 
@@ -177,7 +177,7 @@ if (user.profileId) {
 @@@/section:type-safety
 
 @@@section:logging
-## 🪵 Logging Guidelines
+## # Logging Guidelines
 
 ### Use Structured Logging
 
@@ -188,10 +188,10 @@ if (user.profileId) {
 @@@/section:logging
 
 @@@section:database-operations
-## 🗄️ Database Operation Guidelines
+## # Database Operation Guidelines
 
 @@@section:no-loops
-### 🚨 Never Execute Database Operations in Loops
+### [!] Never Execute Database Operations in Loops
 
 [anti-pattern and correct pattern examples]
 
@@ -206,7 +206,7 @@ if (user.profileId) {
 @@@/section:database-operations
 
 @@@section:error-handling
-## 🎨 Error Handling
+## # Error Handling
 
 ### Graceful Degradation
 [code example]
@@ -217,7 +217,7 @@ if (user.profileId) {
 @@@/section:error-handling
 
 @@@section:router-guidelines
-## 🎯 Router Guidelines
+## # Router Guidelines
 
 ### Hono Router Example
 [code example]
@@ -228,7 +228,7 @@ if (user.profileId) {
 @@@/section:router-guidelines
 
 @@@section:checklist
-## ✅ Checklist
+## [OK] Checklist
 
 Before committing, confirm:
 
@@ -246,7 +246,7 @@ Before committing, confirm:
 @@@/section:checklist
 
 @@@section:reference-examples
-## 📚 Reference Examples
+## # Reference Examples
 
 | Feature | Reference File |
 |---------|----------------|
@@ -268,13 +268,13 @@ This index helps you quickly locate the sections needed for backend tasks.
 
 | Section | Key Content | Section ID |
 |---------|-------------|------------|
-| 📁 Directory Structure | Module directory template, examples | `directory-structure` |
-| 🎯 Type Safety Guidelines | TypeScript rules, Zod Schema | `type-safety` |
-| 🪵 Logging Guidelines | Structured logging, no console | `logging` |
-| 🗄️ Database Operations | Query directory, batch operations | `database-operations` |
-| 🎨 Error Handling | Graceful degradation, response format | `error-handling` |
-| 🎯 Router Guidelines | Route definitions, middleware | `router-guidelines` |
-| ✅ Checklist | Pre-commit checks | `checklist` |
+| # Directory Structure | Module directory template, examples | `directory-structure` |
+| # Type Safety Guidelines | TypeScript rules, Zod Schema | `type-safety` |
+| # Logging Guidelines | Structured logging, no console | `logging` |
+| # Database Operations | Query directory, batch operations | `database-operations` |
+| # Error Handling | Graceful degradation, response format | `error-handling` |
+| # Router Guidelines | Route definitions, middleware | `router-guidelines` |
+| [OK] Checklist | Pre-commit checks | `checklist` |
 
 ## How to Read Sections
 
@@ -286,16 +286,16 @@ sed -n '/@@@section:database-operations/,/@@@\/section:database-operations/p' do
 ## By Scenario
 
 ### Scenario 1: Create New API Module
-- Required: 📁 Directory Structure (`directory-structure`)
-- Also read: 🎯 Type Safety Guidelines (`type-safety`)
+- Required: # Directory Structure (`directory-structure`)
+- Also read: # Type Safety Guidelines (`type-safety`)
 
 ### Scenario 2: Write Database Operations
-- Required: 🗄️ Database Operations (`database-operations`)
-- Reference: 🎨 Error Handling (`error-handling`)
+- Required: # Database Operations (`database-operations`)
+- Reference: # Error Handling (`error-handling`)
 
 ### Scenario 3: Add New Endpoint
-- Required: 🎯 Router Guidelines (`router-guidelines`)
-- Reference: 🎯 Type Safety Guidelines (`type-safety`)
+- Required: # Router Guidelines (`router-guidelines`)
+- Reference: # Type Safety Guidelines (`type-safety`)
 
 [... add more scenarios based on project needs ...]
 

package/dist/templates/commands/generate-frontend-structure.txt

@@ -6,7 +6,7 @@ Scan the project's frontend code, analyze existing code patterns and tech stack,
 
 ---
 
-## ⚠️ CRITICAL: Requirements
+## [!] CRITICAL: Requirements
 
 1. **Language**: All documentation must be written in **English**
 2. **Section Markers**: Use `@@@section:kebab-case-id` and `@@@/section:kebab-case-id` to mark sections
@@ -98,7 +98,7 @@ mkdir -p workflow/structure/frontend
 These guidelines define the development standards and best practices for [Project Name] frontend modules.
 
 @@@section:directory-structure
-## 📁 Directory Structure Guidelines
+## # Directory Structure Guidelines
 
 @@@section:module-organization
 ### Module Organization
@@ -112,15 +112,15 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:directory-structure
 
 @@@section:type-safety
-## 🎯 Type Safety Guidelines
+## # Type Safety Guidelines
 
 @@@section:backend-contract-types
 ### 1. Backend Contract Types vs Frontend View Models
 
-#### ✅ Correct Approach - Import Types from Backend
+#### [OK] Correct Approach - Import Types from Backend
 [code example]
 
-#### ❌ Wrong Approach
+#### [X] Wrong Approach
 [anti-pattern code example]
 
 @@@/section:backend-contract-types
@@ -128,12 +128,12 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:type-safety
 
 @@@section:hook-development
-## 🪝 Hook Development Guidelines
+## # Hook Development Guidelines
 
 @@@section:query-hook-guidelines
 ### 1. Query Hook Standards
 
-#### ✅ Correct Query Hook Pattern
+#### [OK] Correct Query Hook Pattern
 [code example]
 
 @@@/section:query-hook-guidelines
@@ -141,7 +141,7 @@ These guidelines define the development standards and best practices for [Projec
 @@@section:mutation-hook-guidelines
 ### 2. Mutation Hook Standards
 
-#### ✅ Correct Mutation Hook Pattern
+#### [OK] Correct Mutation Hook Pattern
 [code example]
 
 @@@/section:mutation-hook-guidelines
@@ -149,7 +149,7 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:hook-development
 
 @@@section:api-calls
-## 🔌 API Call Guidelines
+## # API Call Guidelines
 
 ### Basic Usage
 [code example]
@@ -157,7 +157,7 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:api-calls
 
 @@@section:state-management
-## 🏗️ State Management Guidelines
+## # State Management Guidelines
 
 ### 1. URL State Management
 [code example]
@@ -168,7 +168,7 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:state-management
 
 @@@section:component-development
-## 🎨 Component Development Guidelines
+## # Component Development Guidelines
 
 ### 1. Component Structure
 [code example]
@@ -179,14 +179,14 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:component-development
 
 @@@section:performance-optimization
-## ⚡ Performance Optimization Guidelines
+## # Performance Optimization Guidelines
 
 [performance rules]
 
 @@@/section:performance-optimization
 
 @@@section:code-quality
-## 🔍 Code Quality Guidelines
+## # Code Quality Guidelines
 
 ### Lint and Formatting
 [tool configuration and usage]
@@ -194,7 +194,7 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:code-quality
 
 @@@section:checklist
-## ✅ Checklist
+## [OK] Checklist
 
 - [ ] Code passes lint check
 - [ ] Type check passes
@@ -203,7 +203,7 @@ These guidelines define the development standards and best practices for [Projec
 @@@/section:checklist
 
 @@@section:reference-examples
-## 📚 Reference Examples
+## # Reference Examples
 
 | Feature | Reference File |
 |---------|----------------|