@mindfoldhq/trellis 0.3.10 → 0.4.0-beta.10

package/dist/templates/trellis/scripts-shell-archive/create-bootstrap.sh

@@ -59,7 +59,7 @@ write_prd_header() {
 Welcome to Trellis! This is your first task.
 
 AI agents use `.trellis/spec/` to understand YOUR project's coding conventions.
-**Empty templates = AI writes generic code that doesn't match your project style.**
+**Starting from scratch = AI writes generic code that doesn't match your project style.**
 
 Filling these guidelines is a one-time setup that pays off for every future AI session.
 

package/dist/templates/trellis/workflow.md

@@ -58,35 +58,30 @@ git status && git log --oneline -10              # Git state
 **CRITICAL**: Read guidelines before writing any code:
 
 ```bash
-# Read frontend guidelines index (if applicable)
-cat .trellis/spec/frontend/index.md
+# Discover available packages and spec layers
+python3 ./.trellis/scripts/get_context.py --mode packages
 
-# Read backend guidelines index (if applicable)
-cat .trellis/spec/backend/index.md
+# Read the spec index for each relevant module
+cat .trellis/spec/<package>/<layer>/index.md
+
+# Always read shared guides
+cat .trellis/spec/guides/index.md
 ```
 
-**Why read both?**
-- Understand the full project architecture
-- Know coding standards for the entire codebase
-- See how frontend and backend interact
+**Why this matters?**
+- Understand which spec layers apply to your task
+- Know coding standards for the packages you'll modify
 - Learn the overall code quality requirements
 
 ### Step 3: Before Coding - Read Specific Guidelines (Required)
 
-Based on your task, read the **detailed** guidelines:
-
-**Frontend Task**:
-```bash
-cat .trellis/spec/frontend/hook-guidelines.md      # For hooks
-cat .trellis/spec/frontend/component-guidelines.md # For components
-cat .trellis/spec/frontend/type-safety.md          # For types
-```
+Based on your task, read the **detailed** guideline files listed in each spec index's **Pre-Development Checklist**:
 
-**Backend Task**:
 ```bash
-cat .trellis/spec/backend/database-guidelines.md   # For DB operations
-cat .trellis/spec/backend/type-safety.md           # For types
-cat .trellis/spec/backend/logging-guidelines.md    # For logging
+# The index points to specific files — read those, not just the index
+cat .trellis/spec/<package>/<layer>/error-handling.md
+cat .trellis/spec/<package>/<layer>/conventions.md
+# etc. — based on what the Pre-Development Checklist lists
 ```
 
 ---
@@ -168,21 +163,14 @@ python3 ./.trellis/scripts/get_context.py --json
 
 Based on what you'll develop, read the corresponding guidelines:
 
-**Frontend Development** (if applicable):
 ```bash
-# Read index first, then specific docs based on task
-cat .trellis/spec/frontend/index.md
-```
+# Discover available packages and spec layers
+python3 ./.trellis/scripts/get_context.py --mode packages
 
-**Backend Development** (if applicable):
-```bash
-# Read index first, then specific docs based on task
-cat .trellis/spec/backend/index.md
-```
+# Read spec indexes for relevant modules
+cat .trellis/spec/<package>/<layer>/index.md
 
-**Cross-Layer Features**:
-```bash
-# For features spanning multiple layers
+# For cross-layer features
 cat .trellis/spec/guides/cross-layer-thinking-guide.md
 ```
 
@@ -208,21 +196,30 @@ python3 ./.trellis/scripts/task.py create "<title>" --slug <task-name>
 1. Create or select task
    --> python3 ./.trellis/scripts/task.py create "<title>" --slug <name> or list
 
-2. Write code according to guidelines
+2. Start task (mark as current)
+   --> python3 ./.trellis/scripts/task.py start <name>
+   --> Writes .trellis/.current-task; future sessions see it in <current-state>
+
+3. Write code according to guidelines
    --> Read .trellis/spec/ docs relevant to your task
    --> For cross-layer: read .trellis/spec/guides/
 
-3. Self-test
+4. Self-test
    --> Run project's lint/test commands (see spec docs)
    --> Manual feature testing
 
-4. Commit code
+5. Commit code
    --> git add <files>
    --> git commit -m "type(scope): description"
        Format: feat/fix/docs/refactor/test/chore
 
-5. Record session (one command)
+6. Record session (one command)
    --> python3 ./.trellis/scripts/add_session.py --title "Title" --commit "hash"
+
+7. Finish task (clear current)
+   --> python3 ./.trellis/scripts/task.py finish
+   --> Only when the task is fully done; otherwise leave it set so the
+       next session resumes where you left off
 ```
 
 ### Code Quality Checklist
@@ -233,8 +230,7 @@ python3 ./.trellis/scripts/task.py create "<title>" --slug <task-name>
 - [OK] Manual feature testing passes
 
 **Project-specific checks**:
-- See `.trellis/spec/frontend/quality-guidelines.md` for frontend
-- See `.trellis/spec/backend/quality-guidelines.md` for backend
+- See `.trellis/spec/<package>/<layer>/quality-guidelines.md` for package-specific checks
 
 ---
 
@@ -328,11 +324,15 @@ tasks/
 **Commands**:
 ```bash
 python3 ./.trellis/scripts/task.py create "<title>" [--slug <name>]   # Create task directory
+python3 ./.trellis/scripts/task.py start <name>    # Set as current task (writes .current-task, triggers after_start hooks)
+python3 ./.trellis/scripts/task.py finish          # Clear current task (triggers after_finish hooks)
 python3 ./.trellis/scripts/task.py archive <name>  # Archive to archive/{year-month}/
 python3 ./.trellis/scripts/task.py list            # List active tasks
 python3 ./.trellis/scripts/task.py list-archive    # List archived tasks
 ```
 
+**Current task mechanism**: `task.py start <name>` writes the selected task path to `.trellis/.current-task`. The SessionStart hook reads this file to inject `## CURRENT TASK` into every new session's context, so the AI immediately knows what you're working on without being told. Run `task.py finish` when you're done — subsequent sessions will show `(none)` until you start another task.
+
 ---
 
 ## Best Practices

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

@@ -0,0 +1,21 @@
+/**
+ * Windsurf workflow templates
+ *
+ * These are GENERIC templates for user projects.
+ * Do NOT use Trellis project's own .windsurf/ directory (which may be customized).
+ *
+ * Directory structure:
+ *   windsurf/
+ *   └── workflows/   # Workflow files
+ */
+export interface WorkflowTemplate {
+    name: string;
+    content: string;
+}
+/**
+ * Get all workflow templates.
+ * Workflow names match their filename stem
+ * (e.g. trellis-start.md -> /trellis-start).
+ */
+export declare function getAllWorkflows(): WorkflowTemplate[];
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/windsurf/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAqBH,MAAM,WAAW,gBAAgB;IAC/B,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;CACjB;AAED;;;;GAIG;AACH,wBAAgB,eAAe,IAAI,gBAAgB,EAAE,CAcpD"}

package/dist/templates/windsurf/index.js

@@ -0,0 +1,44 @@
+/**
+ * Windsurf workflow templates
+ *
+ * These are GENERIC templates for user projects.
+ * Do NOT use Trellis project's own .windsurf/ directory (which may be customized).
+ *
+ * Directory structure:
+ *   windsurf/
+ *   └── workflows/   # Workflow files
+ */
+import { readdirSync, 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);
+function readTemplate(relativePath) {
+    return readFileSync(join(__dirname, relativePath), "utf-8");
+}
+function listFiles(dir) {
+    try {
+        return readdirSync(join(__dirname, dir));
+    }
+    catch {
+        return [];
+    }
+}
+/**
+ * Get all workflow templates.
+ * Workflow names match their filename stem
+ * (e.g. trellis-start.md -> /trellis-start).
+ */
+export function getAllWorkflows() {
+    const workflows = [];
+    for (const file of listFiles("workflows")) {
+        if (!file.endsWith(".md")) {
+            continue;
+        }
+        const name = file.replace(".md", "");
+        const content = readTemplate(`workflows/${file}`);
+        workflows.push({ name, content });
+    }
+    return workflows;
+}
+//# sourceMappingURL=index.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/windsurf/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,OAAO,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACpD,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,SAAS,YAAY,CAAC,YAAoB;IACxC,OAAO,YAAY,CAAC,IAAI,CAAC,SAAS,EAAE,YAAY,CAAC,EAAE,OAAO,CAAC,CAAC;AAC9D,CAAC;AAED,SAAS,SAAS,CAAC,GAAW;IAC5B,IAAI,CAAC;QACH,OAAO,WAAW,CAAC,IAAI,CAAC,SAAS,EAAE,GAAG,CAAC,CAAC,CAAC;IAC3C,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,CAAC;IACZ,CAAC;AACH,CAAC;AAOD;;;;GAIG;AACH,MAAM,UAAU,eAAe;IAC7B,MAAM,SAAS,GAAuB,EAAE,CAAC;IAEzC,KAAK,MAAM,IAAI,IAAI,SAAS,CAAC,WAAW,CAAC,EAAE,CAAC;QAC1C,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC;YAC1B,SAAS;QACX,CAAC;QAED,MAAM,IAAI,GAAG,IAAI,CAAC,OAAO,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC;QACrC,MAAM,OAAO,GAAG,YAAY,CAAC,aAAa,IAAI,EAAE,CAAC,CAAC;QAClD,SAAS,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,OAAO,EAAE,CAAC,CAAC;IACpC,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC"}

package/dist/templates/windsurf/workflows/trellis-before-dev.md

@@ -0,0 +1,31 @@
+---
+description: Read the relevant development guidelines before starting your task.
+---
+
+Execute these steps:
+
+1. **Discover packages and their spec layers**:
+   ```bash
+   python3 ./.trellis/scripts/get_context.py --mode packages
+   ```
+
+2. **Identify which specs apply** to your task based on:
+   - Which package you're modifying (e.g., `cli/`, `docs-site/`)
+   - What type of work (backend, frontend, unit-test, docs, etc.)
+
+3. **Read the spec index** for each relevant module:
+   ```bash
+   cat .trellis/spec/<package>/<layer>/index.md
+   ```
+   Follow the **"Pre-Development Checklist"** section in the index.
+
+4. **Read the specific guideline files** listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., `error-handling.md`, `conventions.md`, `mock-strategies.md`). Read those files to understand the coding standards and patterns.
+
+5. **Always read shared guides**:
+   ```bash
+   cat .trellis/spec/guides/index.md
+   ```
+
+6. Understand the coding standards and patterns you need to follow, then proceed with your development plan.
+
+This step is **mandatory** before writing any code.