@mindfoldhq/trellis 0.3.10-beta.0 → 0.3.10

package/dist/templates/opencode/commands/trellis/onboard.md

@@ -126,13 +126,13 @@ AI needs the same onboarding - but compressed into seconds at session start.
 
 ---
 
-### /trellis:before-dev - Inject Specialized Knowledge
+### /trellis:before-frontend-dev and /trellis:before-backend-dev - Inject Specialized Knowledge
 
 **WHY IT EXISTS**:
 AI models have "pre-trained knowledge" - general patterns from millions of codebases. But YOUR project has specific conventions that differ from generic patterns.
 
 **WHAT IT ACTUALLY DOES**:
-1. Discovers spec layers via `get_context.py --mode packages` and reads relevant guidelines
+1. Reads `.trellis/spec/frontend/` or `.trellis/spec/backend/`
 2. Loads project-specific patterns into AI's working context:
    - Component naming conventions
    - State management patterns
@@ -140,12 +140,12 @@ AI models have "pre-trained knowledge" - general patterns from millions of codeb
    - Error handling standards
 
 **WHY THIS MATTERS**:
-- Without before-dev: AI writes generic code that doesn't match project style.
-- With before-dev: AI writes code that looks like the rest of the codebase.
+- Without before-*-dev: AI writes generic code that doesn't match project style.
+- With before-*-dev: AI writes code that looks like the rest of the codebase.
 
 ---
 
-### /trellis:check - Combat Context Drift
+### /trellis:check-frontend and /trellis:check-backend - Combat Context Drift
 
 **WHY IT EXISTS**:
 AI context window has limited capacity. As conversation progresses, guidelines injected at session start become less influential. This causes "context drift."
@@ -211,9 +211,9 @@ All the context AI built during this session will be lost when session ends. The
 
 **[1/8] /trellis:start** - AI needs project context before touching code
 **[2/8] python3 ./.trellis/scripts/task.py create "Fix bug" --slug fix-bug** - Track work for future reference
-**[3/8] /trellis:before-dev** - Inject project-specific development guidelines
+**[3/8] /trellis:before-frontend-dev** - Inject project-specific frontend knowledge
 **[4/8] Investigate and fix the bug** - Actual development work
-**[5/8] /trellis:check** - Re-verify code against guidelines
+**[5/8] /trellis:check-frontend** - Re-verify code against guidelines
 **[6/8] /trellis:finish-work** - Holistic cross-layer review
 **[7/8] Human tests and commits** - Human validates before code enters repo
 **[8/8] /trellis:record-session** - Persist memory for future sessions
@@ -228,9 +228,9 @@ All the context AI built during this session will be lost when session ends. The
 ### Example 3: Code Review Fixes
 
 **[1/6] /trellis:start** - Resume context from previous session
-**[2/6] /trellis:before-dev** - Re-inject guidelines before fixes
+**[2/6] /trellis:before-backend-dev** - Re-inject guidelines before fixes
 **[3/6] Fix each CR issue** - Address feedback with guidelines in context
-**[4/6] /trellis:check** - Verify fixes did not introduce new issues
+**[4/6] /trellis:check-backend** - Verify fixes didn't introduce new issues
 **[5/6] /trellis:finish-work** - Document lessons from CR
 **[6/6] Human commits, then /trellis:record-session** - Preserve CR lessons
 
@@ -238,16 +238,16 @@ All the context AI built during this session will be lost when session ends. The
 
 **[1/5] /trellis:start** - Clear baseline before major changes
 **[2/5] Plan phases** - Break into verifiable chunks
-**[3/5] Execute phase by phase with /trellis:check after each** - Incremental verification
+**[3/5] Execute phase by phase with /check-* after each** - Incremental verification
 **[4/5] /trellis:finish-work** - Check if new patterns should be documented
 **[5/5] Record with multiple commit hashes** - Link all commits to one feature
 
 ### Example 5: Debug Session
 
 **[1/6] /trellis:start** - See if this bug was investigated before
-**[2/6] /trellis:before-dev** - Guidelines might document known gotchas
+**[2/6] /trellis:before-backend-dev** - Guidelines might document known gotchas
 **[3/6] Investigation** - Actual debugging work
-**[4/6] /trellis:check** - Verify debug changes do not break other things
+**[4/6] /trellis:check-backend** - Verify debug changes don't break other things
 **[5/6] /trellis:finish-work** - Debug findings might need documentation
 **[6/6] Human commits, then /trellis:record-session** - Debug knowledge is valuable
 
@@ -256,7 +256,7 @@ All the context AI built during this session will be lost when session ends. The
 ## KEY RULES TO EMPHASIZE
 
 1. **AI NEVER commits** - Human tests and approves. AI prepares, human validates.
-2. **Guidelines before code** - /before-dev command injects project knowledge.
+2. **Guidelines before code** - /before-*-dev commands inject project knowledge.
 3. **Check after code** - /check-* commands catch context drift.
 4. **Record everything** - /trellis:record-session persists memory.
 

package/dist/templates/opencode/commands/trellis/parallel.md

@@ -41,7 +41,8 @@ python3 ./.trellis/scripts/get_context.py
 ### Step 3: Read Project Guidelines `[AI]`
 
 ```bash
-python3 ./.trellis/scripts/get_context.py --mode packages  # Discover available spec layers
+cat .trellis/spec/frontend/index.md  # Frontend guidelines index
+cat .trellis/spec/backend/index.md   # Backend guidelines index
 cat .trellis/spec/guides/index.md    # Thinking guides
 ```
 

package/dist/templates/opencode/commands/trellis/record-session.md

@@ -1,6 +1,6 @@
 [!] **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`).
+**Do NOT run `git commit` directly** — the scripts below handle their own commits for `.trellis/` metadata. You only need to read git history (`git log`, `git status`, `git diff`) and run the Python scripts.
 
 ---
 
@@ -31,7 +31,7 @@ python3 ./.trellis/scripts/add_session.py \
   --summary "Brief summary of what was done"
 
 # Method 2: Pass detailed content via stdin
-cat << 'EOF' | python3 ./.trellis/scripts/add_session.py --stdin --title "Title" --commit "hash"
+cat << 'EOF' | python3 ./.trellis/scripts/add_session.py --title "Title" --commit "hash"
 | Feature | Description |
 |---------|-------------|
 | New API | Added user authentication endpoint |

package/dist/templates/opencode/commands/trellis/start.md

@@ -40,14 +40,9 @@ This shows: developer identity, git status, current task (if any), active tasks.
 ### Step 3: Read Guidelines Index
 
 ```bash
-python3 ./.trellis/scripts/get_context.py --mode packages
-```
-
-This shows available packages and their spec layers. Read the relevant spec indexes:
-
-```bash
-cat .trellis/spec/<package>/<layer>/index.md   # Package-specific guidelines
-cat .trellis/spec/guides/index.md              # Thinking guides (always read)
+cat .trellis/spec/frontend/index.md  # Frontend guidelines
+cat .trellis/spec/backend/index.md   # Backend guidelines
+cat .trellis/spec/guides/index.md    # Thinking guides
 ```
 
 > **Important**: The index files are navigation — they list the actual guideline files (e.g., `error-handling.md`, `conventions.md`, `mock-strategies.md`).

package/dist/templates/opencode/plugin/inject-subagent-context.js

@@ -9,7 +9,7 @@
  * - Otherwise, this plugin handles injection
  */
 
-import { existsSync, writeFileSync, readdirSync } from "fs"
+import { existsSync, writeFileSync } from "fs"
 import { join } from "path"
 import { TrellisContext, debugLog } from "../lib/trellis-context.js"
 
@@ -119,7 +119,8 @@ function getCheckContext(ctx, taskDir) {
     const checkFiles = [
       [".opencode/commands/trellis/finish-work.md", "Finish work checklist"],
       [".opencode/commands/trellis/check-cross-layer.md", "Cross-layer check spec"],
-      [".opencode/commands/trellis/check.md", "Check spec"],
+      [".opencode/commands/trellis/check-backend.md", "Backend check spec"],
+      [".opencode/commands/trellis/check-frontend.md", "Frontend check spec"],
     ]
     for (const [f, description] of checkFiles) {
       const content = ctx.readProjectFile(f)
@@ -201,7 +202,8 @@ function getDebugContext(ctx, taskDir) {
     }
 
     const checkFiles = [
-      [".opencode/commands/trellis/check.md", "Check spec"],
+      [".opencode/commands/trellis/check-backend.md", "Backend check spec"],
+      [".opencode/commands/trellis/check-frontend.md", "Frontend check spec"],
       [".opencode/commands/trellis/check-cross-layer.md", "Cross-layer check spec"],
     ]
     for (const [f, description] of checkFiles) {
@@ -227,46 +229,17 @@ function getDebugContext(ctx, taskDir) {
 function getResearchContext(ctx, taskDir) {
   const parts = []
 
-  // Dynamic project structure (scan actual spec directory)
-  const specPath = ".trellis/spec"
-  const specFull = join(ctx.directory, specPath)
-
-  const structureLines = [`## Project Spec Directory Structure\n\n\`\`\`\n${specPath}/`]
-  if (existsSync(specFull)) {
-    try {
-      const entries = readdirSync(specFull, { withFileTypes: true })
-        .filter(d => d.isDirectory() && !d.name.startsWith("."))
-        .sort((a, b) => a.name.localeCompare(b.name))
-
-      for (const entry of entries) {
-        const entryPath = join(specFull, entry.name)
-        // Check if this is a direct spec layer (has index.md)
-        if (existsSync(join(entryPath, "index.md"))) {
-          structureLines.push(`├── ${entry.name}/`)
-        } else {
-          // Check for nested package dirs (monorepo)
-          try {
-            const nested = readdirSync(entryPath, { withFileTypes: true })
-              .filter(d => d.isDirectory() && existsSync(join(entryPath, d.name, "index.md")))
-              .sort((a, b) => a.name.localeCompare(b.name))
-            if (nested.length > 0) {
-              structureLines.push(`├── ${entry.name}/`)
-              for (const n of nested) {
-                structureLines.push(`│   ├── ${n.name}/`)
-              }
-            }
-          } catch {
-            // Ignore nested read errors
-          }
-        }
-      }
-    } catch {
-      // Ignore read errors
-    }
-  }
-  structureLines.push("```")
+  parts.push(`## Project Spec Directory Structure
+
+\`\`\`
+.trellis/spec/
+├── shared/      # Cross-project common specs
+├── frontend/    # Frontend standards
+├── backend/     # Backend standards
+└── guides/      # Thinking guides
 
-  parts.push(structureLines.join("\n") + `
+.trellis/big-question/  # Known issues and pitfalls
+\`\`\`
 
 ## Search Tips
 
@@ -277,10 +250,10 @@ function getResearchContext(ctx, taskDir) {
 
   if (taskDir) {
     const jsonlPath = join(ctx.directory, taskDir, "research.jsonl")
-    const researchEntries = ctx.readJsonlWithFiles(jsonlPath)
-    if (researchEntries.length > 0) {
+    const entries = ctx.readJsonlWithFiles(jsonlPath)
+    if (entries.length > 0) {
       parts.push("\n## Additional Search Context\n")
-      parts.push(ctx.buildContextFromEntries(researchEntries))
+      parts.push(ctx.buildContextFromEntries(entries))
     }
   }
 

package/dist/templates/opencode/plugin/session-start.js

@@ -12,12 +12,8 @@
 
 import { existsSync, readFileSync, readdirSync, statSync } from "fs"
 import { join } from "path"
-import { execFileSync } from "child_process"
-import { platform } from "os"
 import { TrellisContext, contextCollector, debugLog } from "../lib/trellis-context.js"
 
-const PYTHON_CMD = platform() === "win32" ? "python" : "python3"
-
 
 /**
  * Check current task status and return structured status string.
@@ -105,124 +101,6 @@ function getTaskStatus(directory) {
   return `Status: READY\nTask: ${taskTitle}\nNext: Continue with implement or check`
 }
 
-/**
- * Load Trellis config for session-start decisions.
- * Calls get_context.py --mode packages --json for reliable config data.
- */
-function loadTrellisConfig(directory) {
-  const scriptPath = join(directory, ".trellis", "scripts", "get_context.py")
-  if (!existsSync(scriptPath)) {
-    return { isMonorepo: false, packages: {}, specScope: null, activeTaskPackage: null, defaultPackage: null }
-  }
-  try {
-    const output = execFileSync(PYTHON_CMD, [scriptPath, "--mode", "packages", "--json"], {
-      cwd: directory,
-      timeout: 5000,
-      encoding: "utf-8",
-      stdio: ["pipe", "pipe", "pipe"],
-    })
-    const data = JSON.parse(output)
-    if (data.mode !== "monorepo") {
-      return { isMonorepo: false, packages: {}, specScope: null, activeTaskPackage: null, defaultPackage: null }
-    }
-    // Convert packages array to dict keyed by name
-    const pkgDict = {}
-    for (const pkg of (data.packages || [])) {
-      pkgDict[pkg.name] = pkg
-    }
-    return {
-      isMonorepo: true,
-      packages: pkgDict,
-      specScope: data.specScope || null,
-      activeTaskPackage: data.activeTaskPackage || null,
-      defaultPackage: data.defaultPackage || null,
-    }
-  } catch (e) {
-    debugLog("session", "loadTrellisConfig error:", e.message)
-    return { isMonorepo: false, packages: {}, specScope: null, activeTaskPackage: null, defaultPackage: null }
-  }
-}
-
-
-/**
- * Check for legacy spec directory structure in monorepo.
- */
-function checkLegacySpec(directory, config) {
-  if (!config.isMonorepo || Object.keys(config.packages).length === 0) {
-    return null
-  }
-
-  const specDir = join(directory, ".trellis", "spec")
-  if (!existsSync(specDir)) return null
-
-  // Check for legacy flat spec dirs
-  let hasLegacy = false
-  for (const name of ["backend", "frontend"]) {
-    if (existsSync(join(specDir, name, "index.md"))) {
-      hasLegacy = true
-      break
-    }
-  }
-  if (!hasLegacy) return null
-
-  // Check which packages are missing spec/<pkg>/ directory
-  const pkgNames = Object.keys(config.packages).sort()
-  const missing = pkgNames.filter(name => !existsSync(join(specDir, name)))
-
-  if (missing.length === 0) return null
-
-  if (missing.length === pkgNames.length) {
-    return (
-      `[!] Legacy spec structure detected: found \`spec/backend/\` or \`spec/frontend/\` ` +
-      `but no package-scoped \`spec/<package>/\` directories.\n` +
-      `Monorepo packages: ${pkgNames.join(", ")}\n` +
-      `Please reorganize: \`spec/backend/\` -> \`spec/<package>/backend/\``
-    )
-  }
-  return (
-    `[!] Partial spec migration detected: packages ${missing.join(", ")} ` +
-    `still missing \`spec/<pkg>/\` directory.\n` +
-    `Please complete migration for all packages.`
-  )
-}
-
-
-/**
- * Resolve which packages should have their specs injected.
- * Returns a Set of allowed package names, or null for full scan.
- */
-function resolveSpecScope(config) {
-  if (!config.isMonorepo || Object.keys(config.packages).length === 0) {
-    return null
-  }
-
-  const { specScope, activeTaskPackage, defaultPackage, packages } = config
-  if (specScope == null) return null
-
-  if (specScope === "active_task") {
-    if (activeTaskPackage && activeTaskPackage in packages) return new Set([activeTaskPackage])
-    if (defaultPackage && defaultPackage in packages) return new Set([defaultPackage])
-    return null
-  }
-
-  if (Array.isArray(specScope)) {
-    const valid = new Set()
-    for (const entry of specScope) {
-      if (entry in packages) {
-        valid.add(entry)
-      }
-    }
-    if (valid.size > 0) return valid
-    // All invalid: fallback
-    if (activeTaskPackage && activeTaskPackage in packages) return new Set([activeTaskPackage])
-    if (defaultPackage && defaultPackage in packages) return new Set([defaultPackage])
-    return null
-  }
-
-  return null
-}
-
-
 /**
  * Build session context for injection
  */
@@ -232,10 +110,6 @@ function buildSessionContext(ctx) {
   const claudeDir = join(directory, ".claude")
   const opencodeDir = join(directory, ".opencode")
 
-  // Load config for scope filtering and legacy detection
-  const config = loadTrellisConfig(directory)
-  const allowedPkgs = resolveSpecScope(config)
-
   const parts = []
 
   // 1. Header
@@ -244,12 +118,6 @@ You are starting a new session in a Trellis-managed project.
 Read and follow all instructions below carefully.
 </trellis-context>`)
 
-  // Legacy migration warning
-  const legacyWarning = checkLegacySpec(directory, config)
-  if (legacyWarning) {
-    parts.push(`<migration-warning>\n${legacyWarning}\n</migration-warning>`)
-  }
-
   // 2. Current Context (dynamic)
   const contextScript = join(trellisDir, "scripts", "get_context.py")
   if (existsSync(contextScript)) {
@@ -287,31 +155,15 @@ Read and follow all instructions below carefully.
       }).sort()
 
       for (const sub of subs) {
-        // Always include guides/ regardless of scope
-        if (sub === "guides") {
-          const indexFile = join(specDir, sub, "index.md")
-          if (existsSync(indexFile)) {
-            const content = ctx.readFile(indexFile)
-            if (content) {
-              parts.push(`## ${sub}\n${content}\n`)
-            }
-          }
-          continue
-        }
-
         const indexFile = join(specDir, sub, "index.md")
         if (existsSync(indexFile)) {
-          // Flat spec dir: spec/<layer>/index.md (single-repo)
+          // Flat spec dir: spec/<layer>/index.md
           const content = ctx.readFile(indexFile)
           if (content) {
             parts.push(`## ${sub}\n${content}\n`)
           }
         } else {
           // Nested package dirs (monorepo): spec/<pkg>/<layer>/index.md
-          // Apply scope filter
-          if (allowedPkgs !== null && !allowedPkgs.has(sub)) {
-            continue
-          }
           try {
             const nested = readdirSync(join(specDir, sub)).filter(name => {
               try {

package/dist/templates/qoder/skills/before-backend-dev/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: before-backend-dev
+description: "Read the backend development guidelines before starting your development task."
+---
+
+Read the backend development guidelines before starting your development task.
+
+Execute these steps:
+1. Read `.trellis/spec/backend/index.md` to understand available guidelines
+2. Based on your task, read the relevant guideline files:
+   - Database work → `.trellis/spec/backend/database-guidelines.md`
+   - Error handling → `.trellis/spec/backend/error-handling.md`
+   - Logging → `.trellis/spec/backend/logging-guidelines.md`
+   - Type questions → `.trellis/spec/backend/type-safety.md`
+3. Understand the coding standards and patterns you need to follow
+4. Then proceed with your development plan
+
+This step is **mandatory** before writing any backend code.

package/dist/templates/qoder/skills/before-frontend-dev/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: before-frontend-dev
+description: "Read the frontend development guidelines before starting your development task."
+---
+
+Read the frontend development guidelines before starting your development task.
+
+Execute these steps:
+1. Read `.trellis/spec/frontend/index.md` to understand available guidelines
+2. Based on your task, read the relevant guideline files:
+   - Component work → `.trellis/spec/frontend/component-guidelines.md`
+   - Hook work → `.trellis/spec/frontend/hook-guidelines.md`
+   - State management → `.trellis/spec/frontend/state-management.md`
+   - Type questions → `.trellis/spec/frontend/type-safety.md`
+3. Understand the coding standards and patterns you need to follow
+4. Then proceed with your development plan
+
+This step is **mandatory** before writing any frontend code.

package/dist/templates/qoder/skills/check-backend/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: check-backend
+description: "Check if the code you just wrote follows the backend development guidelines."
+---
+
+Check if the code you just wrote follows the backend development guidelines.
+
+Execute these steps:
+1. Run `git status` to see modified files
+2. Read `.trellis/spec/backend/index.md` to understand which guidelines apply
+3. Based on what you changed, read the relevant guideline files:
+   - Database changes → `.trellis/spec/backend/database-guidelines.md`
+   - Error handling → `.trellis/spec/backend/error-handling.md`
+   - Logging changes → `.trellis/spec/backend/logging-guidelines.md`
+   - Type changes → `.trellis/spec/backend/type-safety.md`
+   - Any changes → `.trellis/spec/backend/quality-guidelines.md`
+4. Review your code against the guidelines
+5. Report any violations and fix them if found

package/dist/templates/qoder/skills/check-frontend/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: check-frontend
+description: "Check if the code you just wrote follows the frontend development guidelines."
+---
+
+Check if the code you just wrote follows the frontend development guidelines.
+
+Execute these steps:
+1. Run `git status` to see modified files
+2. Read `.trellis/spec/frontend/index.md` to understand which guidelines apply
+3. Based on what you changed, read the relevant guideline files:
+   - Component changes → `.trellis/spec/frontend/component-guidelines.md`
+   - Hook changes → `.trellis/spec/frontend/hook-guidelines.md`
+   - State changes → `.trellis/spec/frontend/state-management.md`
+   - Type changes → `.trellis/spec/frontend/type-safety.md`
+   - Any changes → `.trellis/spec/frontend/quality-guidelines.md`
+4. Review your code against the guidelines
+5. Report any violations and fix them if found

package/dist/templates/qoder/skills/create-command/SKILL.md

@@ -93,8 +93,8 @@ Description:
 | Skill Type | Prefix | Example |
 |------------|--------|---------|
 | Session Start | `start` | `start` |
-| Pre-development | `before-` | `before-dev` |
-| Check | `check-` | `check` |
+| Pre-development | `before-` | `before-frontend-dev` |
+| Check | `check-` | `check-frontend` |
 | Record | `record-` | `record-session` |
 | Generate | `generate-` | `generate-api-doc` |
 | Update | `update-` | `update-changelog` |

package/dist/templates/qoder/skills/onboard/SKILL.md

@@ -131,13 +131,13 @@ AI needs the same onboarding - but compressed into seconds at session start.
 
 ---
 
-### $before-dev - Inject Specialized Knowledge
+### $before-frontend-dev and $before-backend-dev - Inject Specialized Knowledge
 
 **WHY IT EXISTS**:
 AI models have "pre-trained knowledge" - general patterns from millions of codebases. But YOUR project has specific conventions that differ from generic patterns.
 
 **WHAT IT ACTUALLY DOES**:
-1. Discovers spec layers via `get_context.py --mode packages` and reads relevant guidelines
+1. Reads `.trellis/spec/frontend/` or `.trellis/spec/backend/`
 2. Loads project-specific patterns into AI's working context:
    - Component naming conventions
    - State management patterns
@@ -145,12 +145,12 @@ AI models have "pre-trained knowledge" - general patterns from millions of codeb
    - Error handling standards
 
 **WHY THIS MATTERS**:
-- Without before-dev: AI writes generic code that doesn't match project style.
-- With before-dev: AI writes code that looks like the rest of the codebase.
+- Without before-*-dev: AI writes generic code that doesn't match project style.
+- With before-*-dev: AI writes code that looks like the rest of the codebase.
 
 ---
 
-### $check - Combat Context Drift
+### $check-frontend and $check-backend - Combat Context Drift
 
 **WHY IT EXISTS**:
 AI context window has limited capacity. As conversation progresses, guidelines injected at session start become less influential. This causes "context drift."
@@ -216,9 +216,9 @@ All the context AI built during this session will be lost when session ends. The
 
 **[1/8] $start** - AI needs project context before touching code
 **[2/8] python3 ./.trellis/scripts/task.py create "Fix bug" --slug fix-bug** - Track work for future reference
-**[3/8] $before-dev** - Inject project-specific development guidelines
+**[3/8] $before-frontend-dev** - Inject project-specific frontend knowledge
 **[4/8] Investigate and fix the bug** - Actual development work
-**[5/8] $check** - Re-verify code against guidelines
+**[5/8] $check-frontend** - Re-verify code against guidelines
 **[6/8] $finish-work** - Holistic cross-layer review
 **[7/8] Human tests and commits** - Human validates before code enters repo
 **[8/8] $record-session** - Persist memory for future sessions
@@ -233,9 +233,9 @@ All the context AI built during this session will be lost when session ends. The
 ### Example 3: Code Review Fixes
 
 **[1/6] $start** - Resume context from previous session
-**[2/6] $before-dev** - Re-inject guidelines before fixes
+**[2/6] $before-backend-dev** - Re-inject guidelines before fixes
 **[3/6] Fix each CR issue** - Address feedback with guidelines in context
-**[4/6] $check** - Verify fixes did not introduce new issues
+**[4/6] $check-backend** - Verify fixes didn't introduce new issues
 **[5/6] $finish-work** - Document lessons from CR
 **[6/6] Human commits, then $record-session** - Preserve CR lessons
 
@@ -243,16 +243,16 @@ All the context AI built during this session will be lost when session ends. The
 
 **[1/5] $start** - Clear baseline before major changes
 **[2/5] Plan phases** - Break into verifiable chunks
-**[3/5] Execute phase by phase with $check after each** - Incremental verification
+**[3/5] Execute phase by phase with /check-* after each** - Incremental verification
 **[4/5] $finish-work** - Check if new patterns should be documented
 **[5/5] Record with multiple commit hashes** - Link all commits to one feature
 
 ### Example 5: Debug Session
 
 **[1/6] $start** - See if this bug was investigated before
-**[2/6] $before-dev** - Guidelines might document known gotchas
+**[2/6] $before-backend-dev** - Guidelines might document known gotchas
 **[3/6] Investigation** - Actual debugging work
-**[4/6] $check** - Verify debug changes do not break other things
+**[4/6] $check-backend** - Verify debug changes don't break other things
 **[5/6] $finish-work** - Debug findings might need documentation
 **[6/6] Human commits, then $record-session** - Debug knowledge is valuable
 
@@ -261,7 +261,7 @@ All the context AI built during this session will be lost when session ends. The
 ## KEY RULES TO EMPHASIZE
 
 1. **AI NEVER commits** - Human tests and approves. AI prepares, human validates.
-2. **Guidelines before code** - $before-dev command injects project knowledge.
+2. **Guidelines before code** - /before-*-dev commands inject project knowledge.
 3. **Check after code** - /check-* commands catch context drift.
 4. **Record everything** - $record-session persists memory.
 

package/dist/templates/qoder/skills/record-session/SKILL.md

@@ -5,7 +5,7 @@ description: "Record work progress after human has tested and committed code"
 
 [!] **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`).
+**Do NOT run `git commit` directly** — the scripts below handle their own commits for `.trellis/` metadata. You only need to read git history (`git log`, `git status`, `git diff`) and run the Python scripts.
 
 ---
 
@@ -36,7 +36,7 @@ python3 ./.trellis/scripts/add_session.py \
   --summary "Brief summary of what was done"
 
 # Method 2: Pass detailed content via stdin
-cat << 'EOF' | python3 ./.trellis/scripts/add_session.py --stdin --title "Title" --commit "hash"
+cat << 'EOF' | python3 ./.trellis/scripts/add_session.py --title "Title" --commit "hash"
 | Feature | Description |
 |---------|-------------|
 | New API | Added user authentication endpoint |

package/dist/templates/qoder/skills/start/SKILL.md

@@ -45,14 +45,9 @@ This shows: developer identity, git status, current task (if any), active tasks.
 ### Step 3: Read Guidelines Index
 
 ```bash
-python3 ./.trellis/scripts/get_context.py --mode packages
-```
-
-This shows available packages and their spec layers. Read the relevant spec indexes:
-
-```bash
-cat .trellis/spec/<package>/<layer>/index.md   # Package-specific guidelines
-cat .trellis/spec/guides/index.md              # Thinking guides (always read)
+cat .trellis/spec/frontend/index.md  # Frontend guidelines
+cat .trellis/spec/backend/index.md   # Backend guidelines
+cat .trellis/spec/guides/index.md    # Thinking guides
 ```
 
 > **Important**: The index files are navigation — they list the actual guideline files (e.g., `error-handling.md`, `conventions.md`, `mock-strategies.md`).

package/dist/templates/trellis/config.yaml

@@ -31,23 +31,3 @@ max_journal_lines: 2000
 #     - "echo 'Task finished'"
 #   after_archive:
 #     - "echo 'Task archived'"
-
-#-------------------------------------------------------------------------------
-# Monorepo / Packages
-#-------------------------------------------------------------------------------
-
-# Declare packages for monorepo projects.
-# Trellis auto-detects workspaces during `trellis init`, but you can also
-# configure them manually here.
-#
-# packages:
-#   frontend:
-#     path: packages/frontend
-#   backend:
-#     path: packages/backend
-#   docs:
-#     path: docs-site
-#     type: submodule
-
-# Default package used when --package is not specified.
-# default_package: frontend