@blulotus/trellis 0.7.0

package/dist/templates/kiro/agents/trellis-research.json

@@ -0,0 +1,30 @@
+{
+  "name": "trellis-research",
+  "description": "Code and tech search expert. Persists findings to {TASK_DIR}/research/. No writes outside that directory.",
+  "prompt": "# Research Agent\n\nYou are the Research Agent in the Trellis workflow.\n\n## Core Principle\n\n**You do one thing: find, explain, and PERSIST information.**\n\nConversations get compacted; files don't. Every research output MUST end up as a file under `{TASK_DIR}/research/`. Returning findings only through the chat reply is a failure \u2014 the caller cannot read them next session.\n\n---\n\n## Core Responsibilities\n\n1. **Internal Search** \u2014 locate files/components, understand code logic, discover patterns (Glob, Grep, Read)\n2. **External Search** \u2014 library docs, API references, best practices (web search)\n3. **Persist** \u2014 write each research topic to `{TASK_DIR}/research/<topic>.md`\n4. **Report** \u2014 return file paths + one-line summaries to the main agent (not full content)\n\n---\n\n## Workflow\n\n### Step 1: Resolve Current Task\n\nRun `python3 ./.trellis/scripts/task.py current --source` \u2192 active task path. If no active task is set, ask the user where to write output; do NOT guess.\n\nEnsure `{TASK_DIR}/research/` exists:\n\n```bash\nmkdir -p <TASK_DIR>/research\n```\n\n### Step 2: Understand Search Request\n\nClassify: internal / external / mixed. Determine scope (global / specific directory) and expected shape (file list / pattern notes / tech comparison).\n\n### Step 3: Execute Search\n\nRun independent searches in parallel (Glob + Grep + web) for efficiency.\n\n### Step 4: Persist Each Topic\n\nFor each distinct research topic, Write a markdown file at `{TASK_DIR}/research/<topic-slug>.md`. Use the File Format below.\n\n### Step 5: Report to Main Agent\n\nReply with ONLY:\n\n- List of files written (paths relative to repo root)\n- One-line summary per file\n- Any critical caveats that the main agent needs to know right now\n\nDo NOT paste full research content into the reply. The files are the contract.\n\n---\n\n## Scope Limits (Strict)\n\n### Write ALLOWED\n\n- `{TASK_DIR}/research/*.md` \u2014 your own output\n- Creating `{TASK_DIR}/research/` if it doesn't exist (via `mkdir -p`)\n\n### Write FORBIDDEN\n\n- Code files (`src/`, `lib/`, \u2026)\n- Spec files (`.trellis/spec/`) \u2014 main agent should use `update-spec` skill instead\n- `.trellis/scripts/`, `.trellis/workflow.md`, platform config (`.claude/`, `.cursor/`, etc.)\n- Other task directories\n- Any git operation (commit / push / branch / merge)\n\nIf the user asks you to edit code, decline and suggest spawning `implement` instead.\n\n---\n\n## File Format\n\nEach `{TASK_DIR}/research/<topic>.md` should follow:\n\n```markdown\n# Research: <topic>\n\n- **Query**: <original query>\n- **Scope**: <internal / external / mixed>\n- **Date**: <YYYY-MM-DD>\n\n## Findings\n\n### Files Found\n\n| File Path | Description |\n|---|---|\n| `src/services/xxx.ts` | Main implementation |\n| `src/types/xxx.ts` | Type definitions |\n\n### Code Patterns\n\n<describe patterns, cite file:line>\n\n### External References\n\n- [Library X docs](url) \u2014 <why relevant, version constraints>\n\n### Related Specs\n\n- `.trellis/spec/xxx.md` \u2014 <description>\n\n## Caveats / Not Found\n\n<anything incomplete or uncertain>\n```\n\n---\n\n## Guidelines\n\n### DO\n\n- Provide specific file paths and line numbers\n- Quote actual code snippets\n- Persist every topic to its own file\n- Return file paths in your reply, not the full content\n- Mark \"not found\" explicitly when searches come up empty\n\n### DON'T\n\n- Don't write code or modify files outside `{TASK_DIR}/research/`\n- Don't guess uncertain info\n- Don't paste full research text into the reply (files are the deliverable)\n- Don't propose improvements or critique implementation (that's not your role)\n",
+  "tools": [
+    "read",
+    "write",
+    "glob",
+    "grep",
+    "bash",
+    "web_search",
+    "web_fetch"
+  ],
+  "allowedTools": [
+    "read",
+    "write",
+    "glob",
+    "grep",
+    "bash",
+    "web_search",
+    "web_fetch"
+  ],
+  "hooks": {
+    "agentSpawn": [
+      {
+        "command": "{{PYTHON_CMD}} .kiro/hooks/inject-subagent-context.py"
+      }
+    ]
+  }
+}

package/dist/templates/kiro/agents/trellis.json

@@ -0,0 +1,34 @@
+{
+  "name": "trellis",
+  "description": "Trellis workflow main agent. Drives the Trellis development workflow: reads .trellis/workflow.md, classifies each turn, and routes work through plan / implement / check phases. Use as the default Kiro agent for projects that run Trellis.",
+  "prompt": "# Trellis Workflow Agent\n\nYou are the main session agent for a project that uses the Trellis workflow.\n\n## On Every Turn\n\nA `userPromptSubmit` hook injects a `<workflow-state>` breadcrumb each turn telling you the active task and its current phase. An `agentSpawn` hook injects a `<session-context>` overview when this agent starts. Trust those injections to orient yourself — do not re-derive context from scratch.\n\n## How to Work\n\n1. **Follow the workflow.** `.trellis/workflow.md` is the single source of truth for phases and steps. It is also attached as a resource for this agent. Read it (or the injected Phase Index) and follow the matching phase.\n2. **Resolve the active task** with `python3 ./.trellis/scripts/task.py current --source` when the breadcrumb is missing or stale.\n3. **Classify the turn** before acting: simple conversation, small edit, or a complex task that needs a Trellis task directory + planning. Do not create a task for trivial turns.\n4. **Plan before implementing.** For complex work, write `prd.md` (and `design.md` / `implement.md` when warranted) and get the user's confirmation before entering implementation.\n5. **Load task context in order** for implementation/check: jsonl entries -> `prd.md` -> `design.md` (if present) -> `implement.md` (if present).\n6. **Verify** with the project's lint / type-check / test commands before declaring work done.\n\n## Constraints\n\n- Do NOT run `git commit` / `git push` / `git merge` unless the user explicitly asks.\n- Keep changes surgical and scoped to the request.\n- Discover guidelines on demand: `python3 ./.trellis/scripts/get_context.py --mode packages`.\n",
+  "tools": [
+    "read",
+    "write",
+    "shell",
+    "glob",
+    "grep"
+  ],
+  "allowedTools": [
+    "read",
+    "write",
+    "shell",
+    "glob",
+    "grep"
+  ],
+  "resources": [
+    "file://.trellis/workflow.md"
+  ],
+  "hooks": {
+    "agentSpawn": [
+      {
+        "command": "{{PYTHON_CMD}} .kiro/hooks/session-start.py"
+      }
+    ],
+    "userPromptSubmit": [
+      {
+        "command": "{{PYTHON_CMD}} .kiro/hooks/inject-workflow-state.py"
+      }
+    ]
+  }
+}

package/dist/templates/kiro/hooks/trellis-workflow-state.kiro.hook

@@ -0,0 +1,14 @@
+{
+  "version": "1.0.0",
+  "enabled": true,
+  "name": "trellis-workflow-state",
+  "description": "Inject Trellis workflow state on each prompt",
+  "when": {
+    "type": "promptSubmit"
+  },
+  "then": {
+    "type": "runCommand",
+    "command": "{{PYTHON_CMD}} .kiro/hooks/inject-workflow-state.py",
+    "timeout": 30
+  }
+}

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

@@ -0,0 +1,32 @@
+/**
+ * Kiro templates
+ *
+ * Kiro uses pure JSON agent definitions, not Markdown.
+ * CLI agents embed hooks in their JSON (`hooks.agentSpawn`,
+ * `hooks.userPromptSubmit`); the IDE surface reads standalone `.kiro.hook`
+ * JSON files (`when`/`then` schema).
+ *
+ * Directory structure:
+ *   kiro/
+ *   ├── agents/      # Agent definitions (JSON) — main `trellis` + 3 sub-agents
+ *   └── hooks/       # IDE `.kiro.hook` definitions (JSON)
+ */
+import { type AgentTemplate } from "../template-utils.js";
+export type { AgentTemplate };
+/**
+ * Get all Kiro agent templates (JSON format).
+ * Content contains {{PYTHON_CMD}} placeholder that must be resolved before writing.
+ */
+export declare const getAllAgents: () => AgentTemplate[];
+export interface IdeHookTemplate {
+    /** Filename (e.g. "trellis-workflow-state.kiro.hook") */
+    name: string;
+    /** Raw JSON content; contains {{PYTHON_CMD}} placeholder. */
+    content: string;
+}
+/**
+ * Get all Kiro IDE hook templates (`*.kiro.hook` JSON files).
+ * Content contains {{PYTHON_CMD}} placeholder that must be resolved before writing.
+ */
+export declare const getIdeHooks: () => IdeHookTemplate[];
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/kiro/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,EAAwB,KAAK,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAChF,YAAY,EAAE,aAAa,EAAE,CAAC;AAM9B;;;GAGG;AACH,eAAO,MAAM,YAAY,QAAO,aAAa,EAAsB,CAAC;AAEpE,MAAM,WAAW,eAAe;IAC9B,yDAAyD;IACzD,IAAI,EAAE,MAAM,CAAC;IACb,6DAA6D;IAC7D,OAAO,EAAE,MAAM,CAAC;CACjB;AAED;;;GAGG;AACH,eAAO,MAAM,WAAW,QAAO,eAAe,EAGqB,CAAC"}

package/dist/templates/kiro/index.js

@@ -0,0 +1,28 @@
+/**
+ * Kiro templates
+ *
+ * Kiro uses pure JSON agent definitions, not Markdown.
+ * CLI agents embed hooks in their JSON (`hooks.agentSpawn`,
+ * `hooks.userPromptSubmit`); the IDE surface reads standalone `.kiro.hook`
+ * JSON files (`when`/`then` schema).
+ *
+ * Directory structure:
+ *   kiro/
+ *   ├── agents/      # Agent definitions (JSON) — main `trellis` + 3 sub-agents
+ *   └── hooks/       # IDE `.kiro.hook` definitions (JSON)
+ */
+import { createTemplateReader } from "../template-utils.js";
+const { listFiles, readTemplate, listJsonAgents } = createTemplateReader(import.meta.url);
+/**
+ * Get all Kiro agent templates (JSON format).
+ * Content contains {{PYTHON_CMD}} placeholder that must be resolved before writing.
+ */
+export const getAllAgents = () => listJsonAgents();
+/**
+ * Get all Kiro IDE hook templates (`*.kiro.hook` JSON files).
+ * Content contains {{PYTHON_CMD}} placeholder that must be resolved before writing.
+ */
+export const getIdeHooks = () => listFiles("hooks")
+    .filter((f) => f.endsWith(".kiro.hook"))
+    .map((f) => ({ name: f, content: readTemplate(`hooks/${f}`) }));
+//# sourceMappingURL=index.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/kiro/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,EAAE,oBAAoB,EAAsB,MAAM,sBAAsB,CAAC;AAGhF,MAAM,EAAE,SAAS,EAAE,YAAY,EAAE,cAAc,EAAE,GAAG,oBAAoB,CACtE,MAAM,CAAC,IAAI,CAAC,GAAG,CAChB,CAAC;AAEF;;;GAGG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,GAAoB,EAAE,CAAC,cAAc,EAAE,CAAC;AASpE;;;GAGG;AACH,MAAM,CAAC,MAAM,WAAW,GAAG,GAAsB,EAAE,CACjD,SAAS,CAAC,OAAO,CAAC;KACf,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,CAAC,YAAY,CAAC,CAAC;KACvC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,EAAE,IAAI,EAAE,CAAC,EAAE,OAAO,EAAE,YAAY,CAAC,SAAS,CAAC,EAAE,CAAC,EAAE,CAAC,CAAC,CAAC"}

package/dist/templates/markdown/agents.md

@@ -0,0 +1,21 @@
+<!-- TRELLIS:START -->
+# Trellis Instructions
+
+These instructions are for AI assistants working in this project.
+
+This project is managed by Trellis. The working knowledge you need lives under `.trellis/`:
+
+- `.trellis/workflow.md` — development phases, when to create tasks, skill routing
+- `.trellis/spec/` — package- and layer-scoped coding guidelines (read before writing code in a given layer)
+- `.trellis/workspace/` — per-developer journals and session traces
+- `.trellis/tasks/` — active and archived tasks (PRDs, research, jsonl context)
+
+If a Trellis command is available on your platform (e.g. `/trellis:finish-work`, `/trellis:continue`), prefer it over manual steps. Not every platform exposes every command.
+
+If you're using Codex or another agent-capable tool, additional project-scoped helpers may live in:
+- `.agents/skills/` — reusable Trellis skills
+- `.codex/agents/` — optional custom subagents
+
+Managed by Trellis. Edits outside this block are preserved; edits inside may be overwritten by a future `trellis update`.
+
+<!-- TRELLIS:END -->

package/dist/templates/markdown/gitignore.txt

@@ -0,0 +1,15 @@
+# Trellis workflow gitignore
+# Runtime files that should not be committed
+
+# Developer identity (local to each developer)
+.developer
+
+# Current task pointer (local state)
+.current-task
+
+# Session/window scoped runtime state
+.runtime/
+
+# Agent runtime files (in worktree)
+.agent-log
+.session-id

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

@@ -0,0 +1,27 @@
+/**
+ * Markdown templates for Trellis workflow
+ *
+ * These are GENERIC templates for new projects.
+ * Structure templates use .md.txt extension as they are generic templates.
+ */
+export declare const agentsMdContent: string;
+export declare const workspaceIndexContent: string;
+export declare const agentProgressIndexContent: string;
+export declare const workflowGitignoreContent: string;
+export declare const backendIndexContent: string;
+export declare const backendDirectoryStructureContent: string;
+export declare const backendDatabaseGuidelinesContent: string;
+export declare const backendLoggingGuidelinesContent: string;
+export declare const backendQualityGuidelinesContent: string;
+export declare const backendErrorHandlingContent: string;
+export declare const frontendIndexContent: string;
+export declare const frontendDirectoryStructureContent: string;
+export declare const frontendTypeSafetyContent: string;
+export declare const frontendHookGuidelinesContent: string;
+export declare const frontendComponentGuidelinesContent: string;
+export declare const frontendQualityGuidelinesContent: string;
+export declare const frontendStateManagementContent: string;
+export declare const guidesIndexContent: string;
+export declare const guidesCrossLayerThinkingGuideContent: string;
+export declare const guidesCodeReuseThinkingGuideContent: string;
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/markdown/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAqBH,eAAO,MAAM,eAAe,EAAE,MAAuC,CAAC;AAGtE,eAAO,MAAM,qBAAqB,EAAE,MACK,CAAC;AAG1C,eAAO,MAAM,yBAAyB,QAAwB,CAAC;AAG/D,eAAO,MAAM,wBAAwB,EAAE,MACH,CAAC;AAQrC,eAAO,MAAM,mBAAmB,EAAE,MAEjC,CAAC;AACF,eAAO,MAAM,gCAAgC,EAAE,MAE9C,CAAC;AACF,eAAO,MAAM,gCAAgC,EAAE,MAE9C,CAAC;AACF,eAAO,MAAM,+BAA+B,EAAE,MAE7C,CAAC;AACF,eAAO,MAAM,+BAA+B,EAAE,MAE7C,CAAC;AACF,eAAO,MAAM,2BAA2B,EAAE,MAEzC,CAAC;AAGF,eAAO,MAAM,oBAAoB,EAAE,MAElC,CAAC;AACF,eAAO,MAAM,iCAAiC,EAAE,MAE/C,CAAC;AACF,eAAO,MAAM,yBAAyB,EAAE,MAEvC,CAAC;AACF,eAAO,MAAM,6BAA6B,EAAE,MAE3C,CAAC;AACF,eAAO,MAAM,kCAAkC,EAAE,MAEhD,CAAC;AACF,eAAO,MAAM,gCAAgC,EAAE,MAE9C,CAAC;AACF,eAAO,MAAM,8BAA8B,EAAE,MAE5C,CAAC;AAGF,eAAO,MAAM,kBAAkB,EAAE,MAEhC,CAAC;AACF,eAAO,MAAM,oCAAoC,EAAE,MAElD,CAAC;AACF,eAAO,MAAM,mCAAmC,EAAE,MAEjD,CAAC"}

package/dist/templates/markdown/index.js

@@ -0,0 +1,52 @@
+/**
+ * Markdown templates for Trellis workflow
+ *
+ * These are GENERIC templates for new projects.
+ * Structure templates use .md.txt extension as they are generic templates.
+ */
+import { readFileSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+/**
+ * Read a template file from src/templates/markdown/
+ */
+function readLocalTemplate(filename) {
+    const filePath = join(__dirname, filename);
+    return readFileSync(filePath, "utf-8");
+}
+// =============================================================================
+// Root files for new projects
+// =============================================================================
+export const agentsMdContent = readLocalTemplate("agents.md");
+// Workspace index template (developer work records)
+export const workspaceIndexContent = readLocalTemplate("workspace-index.md");
+// Backwards compatibility alias
+export const agentProgressIndexContent = workspaceIndexContent;
+// Gitignore (template file - .gitignore is ignored by npm)
+export const workflowGitignoreContent = readLocalTemplate("gitignore.txt");
+// =============================================================================
+// Structure templates (generic templates from .txt files)
+// These are NOT dogfooded - they are generic templates for new projects
+// =============================================================================
+// Backend structure (multi-doc format)
+export const backendIndexContent = readLocalTemplate("spec/backend/index.md.txt");
+export const backendDirectoryStructureContent = readLocalTemplate("spec/backend/directory-structure.md.txt");
+export const backendDatabaseGuidelinesContent = readLocalTemplate("spec/backend/database-guidelines.md.txt");
+export const backendLoggingGuidelinesContent = readLocalTemplate("spec/backend/logging-guidelines.md.txt");
+export const backendQualityGuidelinesContent = readLocalTemplate("spec/backend/quality-guidelines.md.txt");
+export const backendErrorHandlingContent = readLocalTemplate("spec/backend/error-handling.md.txt");
+// Frontend structure (multi-doc format)
+export const frontendIndexContent = readLocalTemplate("spec/frontend/index.md.txt");
+export const frontendDirectoryStructureContent = readLocalTemplate("spec/frontend/directory-structure.md.txt");
+export const frontendTypeSafetyContent = readLocalTemplate("spec/frontend/type-safety.md.txt");
+export const frontendHookGuidelinesContent = readLocalTemplate("spec/frontend/hook-guidelines.md.txt");
+export const frontendComponentGuidelinesContent = readLocalTemplate("spec/frontend/component-guidelines.md.txt");
+export const frontendQualityGuidelinesContent = readLocalTemplate("spec/frontend/quality-guidelines.md.txt");
+export const frontendStateManagementContent = readLocalTemplate("spec/frontend/state-management.md.txt");
+// Guides structure
+export const guidesIndexContent = readLocalTemplate("spec/guides/index.md.txt");
+export const guidesCrossLayerThinkingGuideContent = readLocalTemplate("spec/guides/cross-layer-thinking-guide.md.txt");
+export const guidesCodeReuseThinkingGuideContent = readLocalTemplate("spec/guides/code-reuse-thinking-guide.md.txt");
+//# sourceMappingURL=index.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/markdown/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACvC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAC1C,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC,MAAM,UAAU,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAClD,MAAM,SAAS,GAAG,OAAO,CAAC,UAAU,CAAC,CAAC;AAEtC;;GAEG;AACH,SAAS,iBAAiB,CAAC,QAAgB;IACzC,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,EAAE,QAAQ,CAAC,CAAC;IAC3C,OAAO,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;AACzC,CAAC;AAED,gFAAgF;AAChF,8BAA8B;AAC9B,gFAAgF;AAEhF,MAAM,CAAC,MAAM,eAAe,GAAW,iBAAiB,CAAC,WAAW,CAAC,CAAC;AAEtE,oDAAoD;AACpD,MAAM,CAAC,MAAM,qBAAqB,GAChC,iBAAiB,CAAC,oBAAoB,CAAC,CAAC;AAE1C,gCAAgC;AAChC,MAAM,CAAC,MAAM,yBAAyB,GAAG,qBAAqB,CAAC;AAE/D,2DAA2D;AAC3D,MAAM,CAAC,MAAM,wBAAwB,GACnC,iBAAiB,CAAC,eAAe,CAAC,CAAC;AAErC,gFAAgF;AAChF,0DAA0D;AAC1D,wEAAwE;AACxE,gFAAgF;AAEhF,uCAAuC;AACvC,MAAM,CAAC,MAAM,mBAAmB,GAAW,iBAAiB,CAC1D,2BAA2B,CAC5B,CAAC;AACF,MAAM,CAAC,MAAM,gCAAgC,GAAW,iBAAiB,CACvE,yCAAyC,CAC1C,CAAC;AACF,MAAM,CAAC,MAAM,gCAAgC,GAAW,iBAAiB,CACvE,yCAAyC,CAC1C,CAAC;AACF,MAAM,CAAC,MAAM,+BAA+B,GAAW,iBAAiB,CACtE,wCAAwC,CACzC,CAAC;AACF,MAAM,CAAC,MAAM,+BAA+B,GAAW,iBAAiB,CACtE,wCAAwC,CACzC,CAAC;AACF,MAAM,CAAC,MAAM,2BAA2B,GAAW,iBAAiB,CAClE,oCAAoC,CACrC,CAAC;AAEF,wCAAwC;AACxC,MAAM,CAAC,MAAM,oBAAoB,GAAW,iBAAiB,CAC3D,4BAA4B,CAC7B,CAAC;AACF,MAAM,CAAC,MAAM,iCAAiC,GAAW,iBAAiB,CACxE,0CAA0C,CAC3C,CAAC;AACF,MAAM,CAAC,MAAM,yBAAyB,GAAW,iBAAiB,CAChE,kCAAkC,CACnC,CAAC;AACF,MAAM,CAAC,MAAM,6BAA6B,GAAW,iBAAiB,CACpE,sCAAsC,CACvC,CAAC;AACF,MAAM,CAAC,MAAM,kCAAkC,GAAW,iBAAiB,CACzE,2CAA2C,CAC5C,CAAC;AACF,MAAM,CAAC,MAAM,gCAAgC,GAAW,iBAAiB,CACvE,yCAAyC,CAC1C,CAAC;AACF,MAAM,CAAC,MAAM,8BAA8B,GAAW,iBAAiB,CACrE,uCAAuC,CACxC,CAAC;AAEF,mBAAmB;AACnB,MAAM,CAAC,MAAM,kBAAkB,GAAW,iBAAiB,CACzD,0BAA0B,CAC3B,CAAC;AACF,MAAM,CAAC,MAAM,oCAAoC,GAAW,iBAAiB,CAC3E,+CAA+C,CAChD,CAAC;AACF,MAAM,CAAC,MAAM,mCAAmC,GAAW,iBAAiB,CAC1E,8CAA8C,CAC/C,CAAC"}

package/dist/templates/markdown/spec/backend/database-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Database Guidelines
+
+> Database patterns and conventions for this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's database conventions here.
+
+Questions to answer:
+- What ORM/query library do you use?
+- How are migrations managed?
+- What are the naming conventions for tables/columns?
+- How do you handle transactions?
+-->
+
+(To be filled by the team)
+
+---
+
+## Query Patterns
+
+<!-- How should queries be written? Batch operations? -->
+
+(To be filled by the team)
+
+---
+
+## Migrations
+
+<!-- How to create and run migrations -->
+
+(To be filled by the team)
+
+---
+
+## Naming Conventions
+
+<!-- Table names, column names, index names -->
+
+(To be filled by the team)
+
+---
+
+## Common Mistakes
+
+<!-- Database-related mistakes your team has made -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/backend/directory-structure.md.txt

@@ -0,0 +1,54 @@
+# Directory Structure
+
+> How backend code is organized in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's backend directory structure here.
+
+Questions to answer:
+- How are modules/packages organized?
+- Where does business logic live?
+- Where are API endpoints defined?
+- How are utilities and helpers organized?
+-->
+
+(To be filled by the team)
+
+---
+
+## Directory Layout
+
+```
+<!-- Replace with your actual structure -->
+src/
+├── ...
+└── ...
+```
+
+---
+
+## Module Organization
+
+<!-- How should new features/modules be organized? -->
+
+(To be filled by the team)
+
+---
+
+## Naming Conventions
+
+<!-- File and folder naming rules -->
+
+(To be filled by the team)
+
+---
+
+## Examples
+
+<!-- Link to well-organized modules as examples -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/backend/error-handling.md.txt

@@ -0,0 +1,51 @@
+# Error Handling
+
+> How errors are handled in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's error handling conventions here.
+
+Questions to answer:
+- What error types do you define?
+- How are errors propagated?
+- How are errors logged?
+- How are errors returned to clients?
+-->
+
+(To be filled by the team)
+
+---
+
+## Error Types
+
+<!-- Custom error classes/types -->
+
+(To be filled by the team)
+
+---
+
+## Error Handling Patterns
+
+<!-- Try-catch patterns, error propagation -->
+
+(To be filled by the team)
+
+---
+
+## API Error Responses
+
+<!-- Standard error response format -->
+
+(To be filled by the team)
+
+---
+
+## Common Mistakes
+
+<!-- Error handling mistakes your team has made -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/backend/index.md.txt

@@ -0,0 +1,38 @@
+# Backend Development Guidelines
+
+> Best practices for backend development in this project.
+
+---
+
+## Overview
+
+This directory contains guidelines for backend development. Fill in each file with your project's specific conventions.
+
+---
+
+## Guidelines Index
+
+| Guide | Description | Status |
+|-------|-------------|--------|
+| [Directory Structure](./directory-structure.md) | Module organization and file layout | To fill |
+| [Database Guidelines](./database-guidelines.md) | ORM patterns, queries, migrations | To fill |
+| [Error Handling](./error-handling.md) | Error types, handling strategies | To fill |
+| [Quality Guidelines](./quality-guidelines.md) | Code standards, forbidden patterns | To fill |
+| [Logging Guidelines](./logging-guidelines.md) | Structured logging, log levels | To fill |
+
+---
+
+## How to Fill These Guidelines
+
+For each guideline file:
+
+1. Document your project's **actual conventions** (not ideals)
+2. Include **code examples** from your codebase
+3. List **forbidden patterns** and why
+4. Add **common mistakes** your team has made
+
+The goal is to help AI assistants and new team members understand how YOUR project works.
+
+---
+
+**Language**: All documentation should be written in **English**.

package/dist/templates/markdown/spec/backend/logging-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Logging Guidelines
+
+> How logging is done in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's logging conventions here.
+
+Questions to answer:
+- What logging library do you use?
+- What are the log levels and when to use each?
+- What should be logged?
+- What should NOT be logged (PII, secrets)?
+-->
+
+(To be filled by the team)
+
+---
+
+## Log Levels
+
+<!-- When to use each level: debug, info, warn, error -->
+
+(To be filled by the team)
+
+---
+
+## Structured Logging
+
+<!-- Log format, required fields -->
+
+(To be filled by the team)
+
+---
+
+## What to Log
+
+<!-- Important events to log -->
+
+(To be filled by the team)
+
+---
+
+## What NOT to Log
+
+<!-- Sensitive data, PII, secrets -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/backend/quality-guidelines.md.txt

@@ -0,0 +1,51 @@
+# Quality Guidelines
+
+> Code quality standards for backend development.
+
+---
+
+## Overview
+
+<!--
+Document your project's quality standards here.
+
+Questions to answer:
+- What patterns are forbidden?
+- What linting rules do you enforce?
+- What are your testing requirements?
+- What code review standards apply?
+-->
+
+(To be filled by the team)
+
+---
+
+## Forbidden Patterns
+
+<!-- Patterns that should never be used and why -->
+
+(To be filled by the team)
+
+---
+
+## Required Patterns
+
+<!-- Patterns that must always be used -->
+
+(To be filled by the team)
+
+---
+
+## Testing Requirements
+
+<!-- What level of testing is expected -->
+
+(To be filled by the team)
+
+---
+
+## Code Review Checklist
+
+<!-- What reviewers should check -->
+
+(To be filled by the team)

package/dist/templates/markdown/spec/frontend/component-guidelines.md.txt

@@ -0,0 +1,59 @@
+# Component Guidelines
+
+> How components are built in this project.
+
+---
+
+## Overview
+
+<!--
+Document your project's component conventions here.
+
+Questions to answer:
+- What component patterns do you use?
+- How are props defined?
+- How do you handle composition?
+- What accessibility standards apply?
+-->
+
+(To be filled by the team)
+
+---
+
+## Component Structure
+
+<!-- Standard structure of a component file -->
+
+(To be filled by the team)
+
+---
+
+## Props Conventions
+
+<!-- How props should be defined and typed -->
+
+(To be filled by the team)
+
+---
+
+## Styling Patterns
+
+<!-- How styles are applied (CSS modules, styled-components, Tailwind, etc.) -->
+
+(To be filled by the team)
+
+---
+
+## Accessibility
+
+<!-- A11y requirements and patterns -->
+
+(To be filled by the team)
+
+---
+
+## Common Mistakes
+
+<!-- Component-related mistakes your team has made -->
+
+(To be filled by the team)