@mind-fold/open-flow 0.1.10 → 0.1.12

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

@@ -0,0 +1,297 @@
+# Generate Frontend Structure Guidelines
+
+## Task Description
+
+Scan the project's frontend code, analyze existing code patterns and tech stack, then auto-generate `doc.md` (detailed guidelines) with section markers, then generate `index.md` (navigation index) using section IDs.
+
+---
+
+## ⚠️ 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
+3. **Index**: Reference sections by ID, not line numbers
+
+---
+
+## Execution Steps
+
+### Step 1: Identify Frontend Directory
+
+Scan these possible frontend directories to determine the main frontend code location:
+
+```bash
+# Common frontend directories
+ls -la apps/web/ 2>/dev/null || \
+ls -la src/ 2>/dev/null || \
+ls -la frontend/ 2>/dev/null || \
+ls -la client/ 2>/dev/null || \
+ls -la packages/web/ 2>/dev/null
+```
+
+### Step 2: Identify Tech Stack
+
+Analyze `package.json` and code files to identify:
+
+**Frameworks and Libraries**:
+- [ ] Framework: Next.js / React / Vue / Svelte / Angular
+- [ ] State Management: React Query / Zustand / Redux / Jotai / Pinia
+- [ ] UI Library: Shadcn / Radix / MUI / Ant Design / Chakra
+- [ ] Styling: Tailwind / CSS Modules / Styled Components / Sass
+- [ ] Types: TypeScript / JavaScript
+- [ ] API Client: tRPC / oRPC / REST / GraphQL
+
+**Toolchain**:
+- [ ] Build Tool: Vite / Webpack / Turbopack
+- [ ] Package Manager: pnpm / npm / yarn / bun
+- [ ] Linter: Biome / ESLint / Prettier
+
+### Step 3: Analyze Code Patterns
+
+Scan frontend code to extract the following patterns:
+
+**Directory Structure**:
+```bash
+# List main directory structure
+find [frontend-dir] -type d -maxdepth 3 | head -50
+```
+
+**Component Patterns**:
+- File naming convention (PascalCase / kebab-case)
+- Component file structure (single file / folder)
+- Export style (default / named)
+
+**Hook Patterns**:
+- Naming convention (useXxx)
+- Query Hook patterns
+- Mutation Hook patterns
+- Custom Hook patterns
+
+**Type Definition Patterns**:
+- Type file locations
+- Type import style
+- Backend type reuse patterns
+
+**API Call Patterns**:
+- API client initialization
+- Request/Response handling
+- Error handling approach
+
+**State Management Patterns**:
+- Global state
+- Local state
+- URL state synchronization
+
+### Step 4: Generate `doc.md` with Section Markers
+
+Create directory and generate detailed guidelines:
+
+```bash
+mkdir -p workflow/structure/frontend
+```
+
+**doc.md template** (adjust based on project):
+
+```markdown
+# Frontend Development Guidelines
+
+These guidelines define the development standards and best practices for [Project Name] frontend modules.
+
+@@@section:directory-structure
+## 📁 Directory Structure Guidelines
+
+@@@section:module-organization
+### Module Organization
+[Describe directory structure with tree diagram code block]
+
+**Reference Example**:
+- `[path]` - [description]
+
+@@@/section:module-organization
+
+@@@/section:directory-structure
+
+@@@section:type-safety
+## 🎯 Type Safety Guidelines
+
+@@@section:backend-contract-types
+### 1. Backend Contract Types vs Frontend View Models
+
+#### ✅ Correct Approach - Import Types from Backend
+[code example]
+
+#### ❌ Wrong Approach
+[anti-pattern code example]
+
+@@@/section:backend-contract-types
+
+@@@/section:type-safety
+
+@@@section:hook-development
+## 🪝 Hook Development Guidelines
+
+@@@section:query-hook-guidelines
+### 1. Query Hook Standards
+
+#### ✅ Correct Query Hook Pattern
+[code example]
+
+@@@/section:query-hook-guidelines
+
+@@@section:mutation-hook-guidelines
+### 2. Mutation Hook Standards
+
+#### ✅ Correct Mutation Hook Pattern
+[code example]
+
+@@@/section:mutation-hook-guidelines
+
+@@@/section:hook-development
+
+@@@section:api-calls
+## 🔌 API Call Guidelines
+
+### Basic Usage
+[code example]
+
+@@@/section:api-calls
+
+@@@section:state-management
+## 🏗️ State Management Guidelines
+
+### 1. URL State Management
+[code example]
+
+### 2. React Context Standards
+[code example]
+
+@@@/section:state-management
+
+@@@section:component-development
+## 🎨 Component Development Guidelines
+
+### 1. Component Structure
+[code example]
+
+### 2. Styling Standards
+[code example]
+
+@@@/section:component-development
+
+@@@section:performance-optimization
+## ⚡ Performance Optimization Guidelines
+
+[performance rules]
+
+@@@/section:performance-optimization
+
+@@@section:code-quality
+## 🔍 Code Quality Guidelines
+
+### Lint and Formatting
+[tool configuration and usage]
+
+@@@/section:code-quality
+
+@@@section:checklist
+## ✅ Checklist
+
+- [ ] Code passes lint check
+- [ ] Type check passes
+- [ ] [other check items...]
+
+@@@/section:checklist
+
+@@@section:reference-examples
+## 📚 Reference Examples
+
+| Feature | Reference File |
+|---------|----------------|
+| [Feature1] | `[path]` |
+
+@@@/section:reference-examples
+```
+
+### Step 5: Generate `index.md` with Section IDs
+
+```markdown
+# Frontend Development Guidelines Index
+
+> **Full Documentation**: See `./doc.md` for detailed guidelines
+
+This index helps you quickly locate the guidelines you need based on your task type.
+
+## Quick Navigation
+
+| Development Task | Section to Read | Section ID |
+|-----------------|-----------------|------------|
+| **New feature module** | Directory Structure | `directory-structure` |
+| **Write Query Hook** | Hook Guidelines > Query Hook | `query-hook-guidelines` |
+| **Write Mutation Hook** | Hook Guidelines > Mutation Hook | `mutation-hook-guidelines` |
+| **API calls** | API Call Guidelines | `api-calls` |
+| **State management** | State Management Guidelines | `state-management` |
+| **Write component** | Component Guidelines | `component-development` |
+| **Performance optimization** | Performance Guidelines | `performance-optimization` |
+| **Code quality check** | Code Quality Guidelines | `code-quality` |
+
+## How to Read Sections
+
+```bash
+# Extract a specific section by ID
+sed -n '/@@@section:query-hook-guidelines/,/@@@\/section:query-hook-guidelines/p' doc.md
+```
+
+## By Development Scenario
+
+### Scenario 1: Create a new Query Hook
+
+**Required Reading**:
+- Type Safety > Backend Contract Types (`backend-contract-types`)
+- Hook Guidelines > Query Hook (`query-hook-guidelines`)
+
+### Scenario 2: Create a new UI Component
+
+**Required Reading**:
+- Component Guidelines (`component-development`)
+
+[... add more scenarios based on project needs ...]
+
+## Core Rules Quick Reference
+
+| Rule | Section ID |
+|------|------------|
+| Import types from backend, don't redefine | `backend-contract-types` |
+| Query Hook patterns | `query-hook-guidelines` |
+| [other core rules...] | `section-id` |
+
+## Reference Example Files
+
+| Feature | Reference File |
+|---------|----------------|
+| Query Hook | `[path]` |
+| Mutation Hook | `[path]` |
+| Component | `[path]` |
+```
+
+---
+
+## Output Requirements
+
+1. **Create directory**: `mkdir -p workflow/structure/frontend`
+2. **Write in English**: All documentation must be in English
+3. **Add section markers**: Use `@@@section:id` and `@@@/section:id` format
+4. **Generate index.md**: Reference sections by ID, not line numbers
+5. **Use actual project code**: Examples should come from real project files
+
+---
+
+## Completion Confirmation
+
+- [ ] `doc.md` created with detailed guidelines in **English**
+- [ ] Section markers added to all major sections
+- [ ] `index.md` created with section IDs
+- [ ] Example code from actual project files
+- [ ] Covers all major patterns used in project
+
+Report: "Frontend structure guidelines generated, please check `workflow/structure/frontend/` directory"
+

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

@@ -0,0 +1,18 @@
+/**
+ * Command templates for open-flow workflow
+ * Each command is stored as a .txt file
+ */
+export declare const initAgentTemplate: string;
+export declare const checkFrontendTemplate: string;
+export declare const checkBackendTemplate: string;
+export declare const recordAgentFlowTemplate: string;
+export declare const recordQuestionTemplate: string;
+export declare const onboardDeveloperTemplate: string;
+export declare const generateFrontendStructureTemplate: string;
+export declare const generateBackendStructureTemplate: string;
+export declare const beforeFrontendDevTemplate: string;
+export declare const beforeBackendDevTemplate: string;
+export declare const updateFrontendStructureTemplate: string;
+export declare const updateBackendStructureTemplate: string;
+export declare const createCommandTemplate: string;
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +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"}

package/dist/templates/commands/index.js

@@ -0,0 +1,19 @@
+/**
+ * Command templates for open-flow workflow
+ * Each command is stored as a .txt file
+ */
+import { readCommand } from "../extract.js";
+export const initAgentTemplate = readCommand("init-agent.txt");
+export const checkFrontendTemplate = readCommand("check-frontend.txt");
+export const checkBackendTemplate = readCommand("check-backend.txt");
+export const recordAgentFlowTemplate = readCommand("record-agent-flow.txt");
+export const recordQuestionTemplate = readCommand("record-question.txt");
+export const onboardDeveloperTemplate = readCommand("onboard-developer.txt");
+export const generateFrontendStructureTemplate = readCommand("generate-frontend-structure.txt");
+export const generateBackendStructureTemplate = readCommand("generate-backend-structure.txt");
+export const beforeFrontendDevTemplate = readCommand("before-frontend-dev.txt");
+export const beforeBackendDevTemplate = readCommand("before-backend-dev.txt");
+export const updateFrontendStructureTemplate = readCommand("update-frontend-structure.txt");
+export const updateBackendStructureTemplate = readCommand("update-backend-structure.txt");
+export const createCommandTemplate = readCommand("create-command.txt");
+//# sourceMappingURL=index.js.map

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

@@ -0,0 +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"}

package/dist/templates/commands/init-agent.txt

@@ -0,0 +1,11 @@
+Read the project root's init-agent.md file and follow the instructions to initialize the AI session.
+
+Execute these steps:
+1. Get full session context (one command):
+   ```bash
+   ./workflow/scripts/get-context.sh
+   ```
+2. If not initialized, guide the user to run: `./workflow/scripts/init-developer.sh <name>`
+3. Read relevant structure guidelines based on the task
+4. Report ready status and ask for the task
+

package/dist/templates/commands/onboard-developer.txt

@@ -0,0 +1,34 @@
+A new developer needs onboarding.
+
+Execute these steps in order:
+
+1. **Explain the workflow system** - Describe how open-flow works:
+   - `workflow/` directory structure
+   - Short commands available (/init-agent, /check-frontend, /check-backend, /record-agent-flow)
+   - Guidelines in `workflow/structure/`
+   - Progress tracking in `workflow/agent-progress/`
+
+2. **Initialize their identity**:
+   ```bash
+   ./workflow/scripts/init-developer.sh <developer-name>
+   ```
+
+3. **Guide them through first task**:
+   - Use `./workflow/scripts/get-context.sh` to get full context
+   - Use `./workflow/scripts/feature.sh list` to see active features
+   - Read relevant guidelines in `workflow/structure/`
+   - Start coding
+
+4. **Key scripts to know**:
+   | Script | Purpose |
+   |--------|---------|
+   | `get-context.sh` | Get full session context |
+   | `feature.sh` | Manage features (create/archive/list) |
+   | `add-session.sh` | One-click session recording |
+   | `update-index.sh` | Auto-update index.md |
+
+Key points to emphasize:
+- AI should NOT execute `git commit` - human is responsible for testing and committing
+- Each developer has their own progress directory
+- Read guidelines before coding (mandatory)
+

package/dist/templates/commands/record-agent-flow.txt

@@ -0,0 +1,64 @@
+⚠️ **Prerequisite**: This command should only be used AFTER the human has tested and committed the code.
+
+**AI must NOT execute git commit** - only read history (`git log`, `git status`, `git diff`).
+
+---
+
+## Record Work Progress (Simplified - Only 2 Steps)
+
+### Step 1: Get Context
+
+```bash
+./workflow/scripts/get-context.sh
+```
+
+### Step 2: One-Click Add Session
+
+```bash
+# Method 1: Simple parameters
+./workflow/scripts/add-session.sh \
+  --title "Session Title" \
+  --commit "hash1,hash2" \
+  --summary "Brief summary of what was done"
+
+# Method 2: Pass detailed content via stdin
+cat << 'EOF' | ./workflow/scripts/add-session.sh --title "Title" --commit "hash"
+| Feature | Description |
+|---------|-------------|
+| New API | Added user authentication endpoint |
+| Frontend | Updated login form |
+
+**Updated Files**:
+- `packages/api/modules/auth/router.ts`
+- `apps/web/modules/auth/components/login-form.tsx`
+EOF
+```
+
+**Auto-completes**:
+- ✅ Appends session to progress-N.md
+- ✅ Auto-detects line count, creates new file if >2000 lines
+- ✅ Updates index.md (Total Sessions +1, Last Active, line stats, history)
+
+---
+
+## Archive Completed Feature (if any)
+
+If a feature was completed this session:
+
+```bash
+./workflow/scripts/feature.sh archive <feature-name>
+```
+
+---
+
+## Script Command Reference
+
+| Command | Purpose |
+|---------|---------|
+| `get-context.sh` | Get all context info |
+| `add-session.sh --title "..." --commit "..."` | **One-click add session (recommended)** |
+| `update-index.sh add-session` | Update index.md separately |
+| `feature.sh create <name>` | Create new feature |
+| `feature.sh archive <name>` | Archive completed feature |
+| `feature.sh list` | List active features |
+

package/dist/templates/commands/record-question.txt

@@ -0,0 +1,38 @@
+Record the problem you just solved in `workflow/big-question/` directory.
+
+Create a new markdown file with a descriptive name (e.g., `issue-name.md`) that documents:
+
+1. **Problem Description**: What was the issue?
+2. **Initial Attempts**: What did you try first?
+3. **Why Initial Attempts Failed**: Why didn't the first approaches work?
+4. **Final Solution**: What ultimately solved the problem?
+5. **Why It Worked**: What made this solution effective?
+6. **Key Insight**: How did you arrive at this solution? What was the "aha" moment?
+
+This creates a knowledge base of solved problems for future reference, helping you and other developers avoid the same pitfalls.
+
+**Format**:
+```markdown
+# [Problem Title]
+
+## Problem Description
+[Describe the issue clearly]
+
+## Initial Attempts
+1. [First attempt]
+2. [Second attempt]
+...
+
+## Why Initial Attempts Failed
+[Explain why each attempt didn't work]
+
+## Final Solution
+[Describe what fixed the problem]
+
+## Why It Worked
+[Explain the root cause and why this solution addresses it]
+
+## Key Insight
+[What did you learn? How can this be applied in the future?]
+```
+

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

@@ -0,0 +1,16 @@
+Check if the backend development guidelines need to be updated based on recent code changes.
+
+Execute these steps:
+1. Review recent commits: `git log --oneline -10`
+2. Check if any new patterns or conventions were introduced
+3. Read current guidelines: `workflow/structure/backend/doc.md`
+4. If updates are needed:
+   - Update `doc.md` with new patterns or rules (in **English**)
+   - Add section markers: `@@@section:kebab-case-id` and `@@@/section:kebab-case-id`
+   - Update `index.md` with new section IDs
+5. Report what was updated (if anything)
+
+**Language requirement**: All documentation must be written in **English**.
+
+Only update if there are genuine new patterns worth documenting.
+

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

@@ -0,0 +1,16 @@
+Check if the frontend development guidelines need to be updated based on recent code changes.
+
+Execute these steps:
+1. Review recent commits: `git log --oneline -10`
+2. Check if any new patterns or conventions were introduced
+3. Read current guidelines: `workflow/structure/frontend/doc.md`
+4. If updates are needed:
+   - Update `doc.md` with new patterns or rules (in **English**)
+   - Add section markers: `@@@section:kebab-case-id` and `@@@/section:kebab-case-id`
+   - Update `index.md` with new section IDs
+5. Report what was updated (if anything)
+
+**Language requirement**: All documentation must be written in **English**.
+
+Only update if there are genuine new patterns worth documenting.
+

package/dist/templates/extract.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Read template content from a .txt file
+ * @param category - Template category ('scripts' | 'markdown' | 'commands')
+ * @param filename - Template filename (e.g., 'init-developer.sh.txt')
+ * @returns File content as string
+ */
+export declare function readTemplate(category: "scripts" | "markdown" | "commands", filename: string): string;
+/**
+ * Helper to read script template
+ */
+export declare function readScript(filename: string): string;
+/**
+ * Helper to read markdown template
+ */
+export declare function readMarkdown(filename: string): string;
+/**
+ * Helper to read command template
+ */
+export declare function readCommand(filename: string): string;
+//# sourceMappingURL=extract.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"extract.d.ts","sourceRoot":"","sources":["../../src/templates/extract.ts"],"names":[],"mappings":"AAOA;;;;;GAKG;AACH,wBAAgB,YAAY,CAC3B,QAAQ,EAAE,SAAS,GAAG,UAAU,GAAG,UAAU,EAC7C,QAAQ,EAAE,MAAM,GACd,MAAM,CAGR;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAEnD;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAErD;AAED;;GAEG;AACH,wBAAgB,WAAW,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,CAEpD"}

package/dist/templates/extract.js

@@ -0,0 +1,34 @@
+import * as fs from "node:fs";
+import * as path from "node:path";
+import { fileURLToPath } from "node:url";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = path.dirname(__filename);
+/**
+ * Read template content from a .txt file
+ * @param category - Template category ('scripts' | 'markdown' | 'commands')
+ * @param filename - Template filename (e.g., 'init-developer.sh.txt')
+ * @returns File content as string
+ */
+export function readTemplate(category, filename) {
+    const templatePath = path.join(__dirname, category, filename);
+    return fs.readFileSync(templatePath, "utf-8");
+}
+/**
+ * Helper to read script template
+ */
+export function readScript(filename) {
+    return readTemplate("scripts", filename);
+}
+/**
+ * Helper to read markdown template
+ */
+export function readMarkdown(filename) {
+    return readTemplate("markdown", filename);
+}
+/**
+ * Helper to read command template
+ */
+export function readCommand(filename) {
+    return readTemplate("commands", filename);
+}
+//# sourceMappingURL=extract.js.map

package/dist/templates/extract.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"extract.js","sourceRoot":"","sources":["../../src/templates/extract.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAClC,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC,MAAM,UAAU,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAClD,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC;AAE3C;;;;;GAKG;AACH,MAAM,UAAU,YAAY,CAC3B,QAA6C,EAC7C,QAAgB;IAEhB,MAAM,YAAY,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,QAAQ,EAAE,QAAQ,CAAC,CAAC;IAC9D,OAAO,EAAE,CAAC,YAAY,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC;AAC/C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,UAAU,CAAC,QAAgB;IAC1C,OAAO,YAAY,CAAC,SAAS,EAAE,QAAQ,CAAC,CAAC;AAC1C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,YAAY,CAAC,QAAgB;IAC5C,OAAO,YAAY,CAAC,UAAU,EAAE,QAAQ,CAAC,CAAC;AAC3C,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,WAAW,CAAC,QAAgB;IAC3C,OAAO,YAAY,CAAC,UAAU,EAAE,QAAQ,CAAC,CAAC;AAC3C,CAAC"}

package/dist/templates/markdown/agent-progress-index.d.ts

@@ -0,0 +1,2 @@
+export declare const agentProgressIndexContent: string;
+//# sourceMappingURL=agent-progress-index.d.ts.map

package/dist/templates/markdown/agent-progress-index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-progress-index.d.ts","sourceRoot":"","sources":["../../../src/templates/markdown/agent-progress-index.ts"],"names":[],"mappings":"AAIA,eAAO,MAAM,yBAAyB,QAAyC,CAAC"}

package/dist/templates/markdown/agent-progress-index.js

@@ -0,0 +1,5 @@
+import * as fs from "node:fs";
+import * as path from "node:path";
+const templatePath = path.join(__dirname, "agent-progress-index.md.txt");
+export const agentProgressIndexContent = fs.readFileSync(templatePath, "utf-8");
+//# sourceMappingURL=agent-progress-index.js.map

package/dist/templates/markdown/agent-progress-index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"agent-progress-index.js","sourceRoot":"","sources":["../../../src/templates/markdown/agent-progress-index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAElC,MAAM,YAAY,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,6BAA6B,CAAC,CAAC;AACzE,MAAM,CAAC,MAAM,yBAAyB,GAAG,EAAE,CAAC,YAAY,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC"}