@blxzer/cursor-trellis 0.2.9 → 0.3.2

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/local-architecture/task-system.md

@@ -1,11 +1,11 @@
 # Local Task System
 
-The Trellis task system is stored entirely under `.trellis/tasks/` in the user project. Each task is a directory containing requirements, context, research, state, and relationship information.
+The Trellis task system is stored entirely under `.cstl/tasks/` in the user project. Each task is a directory containing requirements, context, research, state, and relationship information.
 
 ## Task Directory Structure
 
 ```text
-.trellis/tasks/
+.cstl/tasks/
 ├── 04-28-example-task/
 │   ├── task.json
 │   ├── prd.md
@@ -59,31 +59,31 @@ Use child tasks for deliverables that can move through planning, implementation,
 Create new children with:
 
 ```bash
-python3 ./.trellis/scripts/task.py create "<child title>" --slug <child-slug> --parent <parent-dir>
+python3 ./.cstl/scripts/task.py create "<child title>" --slug <child-slug> --parent <parent-dir>
 ```
 
 Link or unlink existing tasks with:
 
 ```bash
-python3 ./.trellis/scripts/task.py add-subtask <parent-dir> <child-dir>
-python3 ./.trellis/scripts/task.py remove-subtask <parent-dir> <child-dir>
+python3 ./.cstl/scripts/task.py add-subtask <parent-dir> <child-dir>
+python3 ./.cstl/scripts/task.py remove-subtask <parent-dir> <child-dir>
 ```
 
 `children` on the parent is a historical list. When a child is archived, Trellis keeps that child name in the parent so progress like `[2/3 done]` remains meaningful after completed children move to `archive/`.
 
 The AI should not treat phase numbers as task status. Task progress is mainly determined by `status`, artifact presence (`prd.md`, optional `design.md` / `implement.md`), whether JSONL context is configured for sub-agent mode, and the phase descriptions in `workflow.md`.
 
-## Selected Task
-
-The user sees a "selected task," and Trellis stores that selection per live session.
-
-```text
-.trellis/.runtime/sessions/<context-key>.json
-```
-
-`task.py select <task>` writes the task path into the runtime session file for the current session. `task.py selected --source` shows the selected task and where it came from. Different AI windows can point to different tasks without overwriting each other.
-
-If the platform or shell environment has no stable session identity, `task.py select` may be unable to set the selected task. The AI should read the error, inspect the platform hook/session environment, and not fall back to a shared global pointer.
+## Selected Task
+
+The user sees a "selected task," and Trellis stores that selection per live session.
+
+```text
+.cstl/.runtime/sessions/<context-key>.json
+```
+
+`task.py select <task>` writes the task path into the runtime session file for the current session. `task.py selected --source` shows the selected task and where it came from. Different AI windows can point to different tasks without overwriting each other.
+
+If the platform or shell environment has no stable session identity, `task.py select` may be unable to set the selected task. The AI should read the error, inspect the platform hook/session environment, and not fall back to a shared global pointer.
 
 ## JSONL Context
 
@@ -92,8 +92,8 @@ If the platform or shell environment has no stable session identity, `task.py se
 Format:
 
 ```jsonl
-{"file": ".trellis/spec/cli/backend/index.md", "reason": "Backend conventions"}
-{"file": ".trellis/tasks/04-28-example/research/api.md", "reason": "API research"}
+{"file": ".cstl/spec/cli/backend/index.md", "reason": "Backend conventions"}
+{"file": ".cstl/tasks/04-28-example/research/api.md", "reason": "API research"}
 ```
 
 Rules:
@@ -106,17 +106,17 @@ Rules:
 ## Common Commands
 
 ```bash
-python3 ./.trellis/scripts/task.py create "<title>" --slug <slug>
-python3 ./.trellis/scripts/task.py dashboard
-python3 ./.trellis/scripts/task.py select <task>
-python3 ./.trellis/scripts/task.py selected --source
-python3 ./.trellis/scripts/task.py start-execution <task> --check
-python3 ./.trellis/scripts/task.py start-execution <task> --approved
-python3 ./.trellis/scripts/task.py add-context <task> implement <file> <reason>
-python3 ./.trellis/scripts/task.py validate <task>
-python3 ./.trellis/scripts/task.py exit
-python3 ./.trellis/scripts/task.py archive <task>
-```
+python3 ./.cstl/scripts/task.py create "<title>" --slug <slug>
+python3 ./.cstl/scripts/task.py dashboard
+python3 ./.cstl/scripts/task.py select <task>
+python3 ./.cstl/scripts/task.py selected --source
+python3 ./.cstl/scripts/task.py start-execution <task> --check
+python3 ./.cstl/scripts/task.py start-execution <task> --approved
+python3 ./.cstl/scripts/task.py add-context <task> implement <file> <reason>
+python3 ./.cstl/scripts/task.py validate <task>
+python3 ./.cstl/scripts/task.py exit
+python3 ./.cstl/scripts/task.py archive <task>
+```
 
 When modifying the task system, the AI should prefer script commands to maintain structure. Edit JSON/Markdown directly only when scripts do not cover the need.
 
@@ -124,10 +124,10 @@ When modifying the task system, the AI should prefer script commands to maintain
 
 | Need | Edit location |
 | --- | --- |
-| Change the default task template | `.trellis/scripts/common/task_store.py` and task creation instructions. |
-| Change status semantics | `.trellis/workflow.md`, workflow-state hook logic, and task usage conventions. |
-| Add task lifecycle actions | `hooks.after_*` in `.trellis/config.yaml`. |
-| Change context rules | Planning artifact guidance in `.trellis/workflow.md` and related platform agent/hook instructions. |
-| Change archive policy | `.trellis/scripts/common/task_store.py` / `task_utils.py`. |
+| Change the default task template | `.cstl/scripts/common/task_store.py` and task creation instructions. |
+| Change status semantics | `.cstl/workflow.md`, workflow-state hook logic, and task usage conventions. |
+| Add task lifecycle actions | `hooks.after_*` in `.cstl/config.yaml`. |
+| Change context rules | Planning artifact guidance in `.cstl/workflow.md` and related platform agent/hook instructions. |
+| Change archive policy | `.cstl/scripts/common/task_store.py` / `task_utils.py`. |
 
 These are local files in the user project. Do not default to editing Trellis CLI source code unless the user wants to contribute upstream.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/local-architecture/workflow.md

@@ -1,10 +1,10 @@
 # Local Workflow System
 
-`.trellis/workflow.md` is the Trellis workflow source of truth inside the user project. An AI does not need Trellis source code to understand how the current project should move tasks forward; this file is enough.
+`.cstl/workflow.md` is the Trellis workflow source of truth inside the user project. An AI does not need Trellis source code to understand how the current project should move tasks forward; this file is enough.
 
 ## File Responsibilities
 
-`.trellis/workflow.md` has three responsibilities:
+`.cstl/workflow.md` has three responsibilities:
 
 1. **Explain workflow phases**: Plan, Execute, Finish.
 2. **Define skill routing**: which skill or agent the AI should use when the user expresses a certain intent.
@@ -24,8 +24,8 @@ Each phase contains numbered steps, such as `1.3 Configure context`. These numbe
 
 `workflow.md` separates routing by platform capability:
 
-- Platforms with sub-agent support: dispatch `trellis-implement` by default for implementation and `trellis-check` for checking.
-- Platforms without sub-agent support: the main session reads skills such as `trellis-before-dev`, then executes directly.
+- Platforms with sub-agent support: dispatch `cstl-implement` by default for implementation and `cstl-check` for checking.
+- Platforms without sub-agent support: the main session reads skills such as `cstl-before-dev`, then executes directly.
 
 When changing local AI behavior, update the routing descriptions in `workflow.md` first, then check whether the corresponding platform skill, command, or agent files need to stay in sync.
 
@@ -39,11 +39,11 @@ The bottom of `workflow.md` can contain state blocks like this:
 [/workflow-state:no_task]
 ```
 
-Hooks choose the right block based on selected task status and inject it into the conversation. Common states include:
+Hooks choose the right block based on selected task status and inject it into the conversation. Common states include:
 
 | State | Meaning |
 | --- | --- |
-| `no_task` | The current session has no selected task. |
+| `no_task` | The current session has no selected task. |
 | `planning` | The task is still in requirements, research, or context configuration. |
 | `in_progress` | The task has entered implementation and checking. |
 | `completed` | The task is complete and waiting for wrap-up or archive. |
@@ -62,13 +62,13 @@ Common changes:
 | Change the wrap-up flow | Update Phase 3 and `finish-work` related descriptions. Note the current split: Phase 3.4 = AI-driven code commits (batched, user-confirmed), Phase 3.5 = `/finish-work` (archive + record session). `/finish-work` refuses to run if the working tree is dirty. |
 | Change platform differences | Update routing descriptions grouped by platform. |
 
-After editing, make the AI reread `.trellis/workflow.md`; do not assume the flow from the old conversation is still valid.
+After editing, make the AI reread `.cstl/workflow.md`; do not assume the flow from the old conversation is still valid.
 
 ## Relationship To Platform Files
 
 `workflow.md` is the semantic center of the local workflow, but each platform can also have its own entry files:
 
-- skills, such as `trellis-brainstorm` and `trellis-check`.
+- skills, such as `cstl-brainstorm` and `cstl-check`.
 - commands/prompts/workflows, such as continue and finish-work.
 - hooks, such as session-start or workflow-state injection.
 

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/local-architecture/workspace-memory.md

@@ -1,11 +1,11 @@
 # Local Workspace Memory System
 
-`.trellis/workspace/` stores cross-session memory. Its purpose is to let AI and humans understand what happened before across different windows and different days.
+`.cstl/workspace/` stores cross-session memory. Its purpose is to let AI and humans understand what happened before across different windows and different days.
 
 ## Directory Structure
 
 ```text
-.trellis/workspace/
+.cstl/workspace/
 ├── index.md
 └── <developer>/
     ├── index.md
@@ -15,20 +15,20 @@
 
 | File | Purpose |
 | --- | --- |
-| `.trellis/.developer` | Current developer identity. |
-| `.trellis/workspace/index.md` | Global workspace overview. |
-| `.trellis/workspace/<developer>/index.md` | Session index for a developer. |
-| `.trellis/workspace/<developer>/journal-N.md` | Session journal. |
+| `.cstl/.developer` | Current developer identity. |
+| `.cstl/workspace/index.md` | Global workspace overview. |
+| `.cstl/workspace/<developer>/index.md` | Session index for a developer. |
+| `.cstl/workspace/<developer>/journal-N.md` | Session journal. |
 
 ## Developer Identity
 
 Run this the first time:
 
 ```bash
-python3 ./.trellis/scripts/init_developer.py <name>
+python3 ./.cstl/scripts/init_developer.py <name>
 ```
 
-This creates `.trellis/.developer` and the corresponding workspace directory. The AI should not change developer identity casually; if the identity is wrong, first confirm who is using the current project.
+This creates `.cstl/.developer` and the corresponding workspace directory. The AI should not change developer identity casually; if the identity is wrong, first confirm who is using the current project.
 
 ## Journal
 
@@ -37,7 +37,7 @@ This creates `.trellis/.developer` and the corresponding workspace directory. Th
 Common command for recording a session:
 
 ```bash
-python3 ./.trellis/scripts/add_session.py \
+python3 ./.cstl/scripts/add_session.py \
   --title "Session title" \
   --summary "What changed" \
   --commit "abc1234"
@@ -49,23 +49,23 @@ Planning or review work without a commit can also be recorded by using `--no-com
 
 | System | What it stores |
 | --- | --- |
-| `.trellis/tasks/` | Requirements, design, research, and state for a specific task. |
-| `.trellis/workspace/` | Work records across tasks and sessions. |
-| `.trellis/spec/` | Engineering knowledge preserved as long-term conventions. |
+| `.cstl/tasks/` | Requirements, design, research, and state for a specific task. |
+| `.cstl/workspace/` | Work records across tasks and sessions. |
+| `.cstl/spec/` | Engineering knowledge preserved as long-term conventions. |
 
-If information is only useful for the selected task, put it in the task directory.
-If information describes what happened in the current session, put it in the workspace journal.
+If information is only useful for the selected task, put it in the task directory.
+If information describes what happened in the current session, put it in the workspace journal.
 If information should be followed every time code is written in the future, put it in spec.
 
 ## Local Customization Points
 
 | Need | Edit location |
 | --- | --- |
-| Change maximum journal lines | `max_journal_lines` in `.trellis/config.yaml`. |
-| Change session auto-commit message | `session_commit_message` in `.trellis/config.yaml`. |
-| Change session content format | `.trellis/scripts/add_session.py`. |
-| Change how workspace is displayed in context | `.trellis/scripts/common/session_context.py`. |
+| Change maximum journal lines | `max_journal_lines` in `.cstl/config.yaml`. |
+| Change session auto-commit message | `session_commit_message` in `.cstl/config.yaml`. |
+| Change session content format | `.cstl/scripts/add_session.py`. |
+| Change how workspace is displayed in context | `.cstl/scripts/common/session_context.py`. |
 
 ## AI Usage Rules
 
-The AI should not treat workspace as the only source of truth. When resuming a task, read the selected task first, then use workspace for background. After a task is complete, record important process notes in workspace; if long-term rules emerged, update spec.
+The AI should not treat workspace as the only source of truth. When resuming a task, read the selected task first, then use workspace for background. After a task is complete, record important process notes in workspace; if long-term rules emerged, update spec.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/platform-files/agents.md

@@ -2,9 +2,9 @@
 
 Trellis agent files define specialized roles. Common Trellis agents in a user project are:
 
-- `trellis-research`
-- `trellis-implement`
-- `trellis-check`
+- `cstl-research`
+- `cstl-implement`
+- `cstl-check`
 
 Responsibility boundaries should stay consistent regardless of file format.
 
@@ -14,9 +14,9 @@ Responsibility boundaries should stay consistent regardless of file format.
 
 | Agent | Responsibility |
 | --- | --- |
-| `trellis-research` | Investigate the question and write findings into the selected task's `research/`. |
-| `trellis-implement` | Implement against `prd.md`, optional `design.md` / `implement.md`, `implement.jsonl`, and related spec/research. |
-| `trellis-check` | Review changes, fix discovered issues, and run necessary checks. |
+| `cstl-research` | Investigate the question and write findings into the selected task's `research/`. |
+| `cstl-implement` | Implement against `prd.md`, optional `design.md` / `implement.md`, `implement.jsonl`, and related spec/research. |
+| `cstl-check` | Review changes, fix discovered issues, and run necessary checks. |
 
 Agent files should not become generic chat prompts. They should define input sources, write boundaries, whether code may be changed, and how results are reported.
 
@@ -24,7 +24,7 @@ Agent files should not become generic chat prompts. They should define input sou
 
 | Platform | Agent path |
 | --- | --- |
-| Cursor | `.cursor/agents/trellis-*.md` |
+| Cursor | `.cursor/agents/cstl-*.md` |
 
 Agent files are dispatched via the Cursor Task tool, opened as Agent sessions, or invoked inline as Skill forms depending on the entry point. See `cursor-subagent-policy.md.txt` for the full entry-point matrix and Method 1–2.6 model dispatch strategy.
 
@@ -38,7 +38,7 @@ The Cursor hook (`inject-subagent-context.py`, registered in `.cursor/hooks.json
 
 The agent file instructs the agent to read after startup:
 
-- `python3 ./.trellis/scripts/task.py selected --source`
+- `python3 ./.cstl/scripts/task.py selected --source`
 - `implement.jsonl` or `check.jsonl`
 - spec/research files referenced by JSONL
 - selected task `prd.md`
@@ -51,9 +51,9 @@ This mode fits cases where the hook cannot reliably rewrite the sub-agent prompt
 
 | User need | Edit location |
 | --- | --- |
-| Implement agent must follow extra restrictions | `.cursor/agents/trellis-implement.md`. |
-| Check agent must run project-specific commands | `.cursor/agents/trellis-check.md`, and `.trellis/spec/` if needed. |
-| Research agent must output a fixed format | `.cursor/agents/trellis-research.md`. |
+| Implement agent must follow extra restrictions | `.cursor/agents/cstl-implement.md`. |
+| Check agent must run project-specific commands | `.cursor/agents/cstl-check.md`, and `.cstl/spec/` if needed. |
+| Research agent must output a fixed format | `.cursor/agents/cstl-research.md`. |
 | Agent cannot read task context | Agent prelude in the agent file, or the `inject-subagent-context` hook registration in `.cursor/hooks.json`. |
 | Add a project-specific agent | `.cursor/agents/` + related skill/command entry point that invokes it. |
 
@@ -62,7 +62,7 @@ This mode fits cases where the hook cannot reliably rewrite the sub-agent prompt
 1. **Keep responsibilities single-purpose**. Do not mix research, implement, and check responsibilities into one agent.
 2. **Specify the read order**. Agents must know to start from the selected task, read jsonl/spec context, then read `prd.md`, `design.md` if present, and `implement.md` if present.
 3. **Specify write boundaries**. Research usually only writes `research/`; implement can write code; check can fix issues.
-4. **Treat dogfood + published copies consistently**. `.cursor/agents/trellis-*.md` (dogfooded) and `packages/cli/src/templates/cursor/agents/trellis-*.md` (published template) must stay in sync — see `cross-layer-thinking-guide.md.txt` → Cross-Package Template Consistency.
+4. **Treat dogfood + published copies consistently**. `.cursor/agents/cstl-*.md` (dogfooded) and `packages/cli/src/templates/cursor/agents/cstl-*.md` (published template) must stay in sync — see `cross-layer-thinking-guide.md.txt` → Cross-Package Template Consistency.
 
 ## Do Not Default To Editing Upstream Templates
 

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/platform-files/hooks-and-settings.md

@@ -7,13 +7,13 @@ Hooks/settings are the entry layer that connects Cursor to Trellis. They decide
 `.cursor/hooks.json` registers:
 
 - session-start hook: injects a Trellis overview when a new session starts or context resets (note the Cursor `additional_context` bug #158452 — see `cursor-context-injection-guide.md.txt`).
-- workflow-state hook: parses `[workflow-state:STATUS]` blocks from `.trellis/workflow.md` and emits the body matching the selected task `status` on each user input. Parser-only; the script does not embed fallback content.
+- workflow-state hook: parses `[workflow-state:STATUS]` blocks from `.cstl/workflow.md` and emits the body matching the selected task `status` on each user input. Parser-only; the script does not embed fallback content.
 - sub-agent context hook: injects task context when implementation/check/research agents start.
 - shell/session bridge: lets shell commands see the same Trellis session identity.
 
 > Trellis previously shipped settings/config files for many platforms (`.claude/settings.json`, `.codex/hooks.json`, `.gemini/settings.json`, etc.). The project has converged on **Cursor-only**. New Trellis features ship into `.cursor/hooks.json` + `.cursor/hooks/`.
 
-Whether legacy settings/config files exist in a project depends on which historical `trellis init --<platform>` flags the user previously ran; `trellis update` preserves them.
+Whether legacy settings/config files exist in a project depends on which historical `cstl init --<platform>` flags the user previously ran; `cstl update` preserves them.
 
 | Platform | settings/config |
 | --- | --- |
@@ -24,7 +24,7 @@ Whether legacy settings/config files exist in a project depends on which histori
 | Script | Purpose |
 | --- | --- |
 | `session-start.py` | Generates session-start context. |
-| `inject-workflow-state.py` | Parses `[workflow-state:STATUS]` blocks in `.trellis/workflow.md` and emits the body matching the selected task status. Falls back to `Refer to workflow.md for current step.` when no matching block exists. |
+| `inject-workflow-state.py` | Parses `[workflow-state:STATUS]` blocks in `.cstl/workflow.md` and emits the body matching the selected task status. Falls back to `Refer to workflow.md for current step.` when no matching block exists. |
 | `inject-subagent-context.py` | Injects PRD, JSONL context, and related spec/research into sub-agents. |
 | `inject-shell-session-context.py` | Lets shell commands inherit Trellis session identity. |
 
@@ -35,7 +35,7 @@ Cursor exposes sessionStart, preToolUse on Task/Subagent, beforeShellExecution,
 | User need | Edit location |
 | --- | --- |
 | AI should see more/less context in a new session | `.cursor/hooks.json` → `session-start` hook (or `.cursor/rules/*.mdc` for content the model must see every turn — see `cursor-context-injection-guide.md.txt`). |
-| Per-turn hint policy should change | `[workflow-state:STATUS]` block in `.trellis/workflow.md`. The hook parses workflow.md verbatim — no script edit required. |
+| Per-turn hint policy should change | `[workflow-state:STATUS]` block in `.cstl/workflow.md`. The hook parses workflow.md verbatim — no script edit required. |
 | Sub-agent cannot read PRD/spec | `inject-subagent-context.py` hook or agent prelude in `.cursor/agents/*.md`. |
 | `task.py selected` in shell has no selected task | `inject-shell-session-context.py` hook or environment-variable configuration. |
 | Disable an automatic injection | The corresponding hook registration in `.cursor/hooks.json`. |
@@ -44,7 +44,7 @@ Cursor exposes sessionStart, preToolUse on Task/Subagent, beforeShellExecution,
 
 1. **Settings wire things up; hooks define behavior**. If only the hook changes, Cursor may never call it. If only settings change, behavior may not change.
 2. **Confirm Cursor event names first**. Cursor's hook event surface has changed between releases; what an older guide calls `UserPromptSubmit` may now be modeled by `beforeSubmitPrompt` instead.
-3. **Hooks read local `.trellis/`, not upstream source**. `.trellis/scripts/` and `.trellis/workflow.md` in the user project are the default targets.
+3. **Hooks read local `.cstl/`, not upstream source**. `.cstl/scripts/` and `.cstl/workflow.md` in the user project are the default targets.
 4. **Errors must be visible**. Hook failures should tell the user what was not injected instead of silently leaving the AI without context.
 
 ## Troubleshooting Path
@@ -53,6 +53,6 @@ If the user says "AI did not read Trellis state":
 
 1. Check whether `.cursor/hooks.json` registers the hook.
 2. Check whether the hook file exists under `.cursor/hooks/`.
-3. Manually run the `.trellis/scripts/get_context.py` or `task.py selected --source` command that the hook depends on.
-4. Check whether selected task state exists in `.trellis/.runtime/sessions/`.
+3. Manually run the `.cstl/scripts/get_context.py` or `task.py selected --source` command that the hook depends on.
+4. Check whether selected task state exists in `.cstl/.runtime/sessions/`.
 5. Check whether the Cursor shell passes session identity.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/platform-files/overview.md

@@ -1,15 +1,15 @@
 # Platform Files Overview
 
-Trellis connects the same local architecture to **Cursor**. `.trellis/` stores the shared runtime; `.cursor/` stores adapter files that define how Cursor enters Trellis.
+Trellis connects the same local architecture to **Cursor**. `.cstl/` stores the shared runtime; `.cursor/` stores adapter files that define how Cursor enters Trellis.
 
 When a local AI modifies Trellis, it should distinguish two file categories first:
 
-- **Shared files**: `.trellis/workflow.md`, `.trellis/tasks/`, `.trellis/spec/`, `.trellis/scripts/`.
+- **Shared files**: `.cstl/workflow.md`, `.cstl/tasks/`, `.cstl/spec/`, `.cstl/scripts/`.
 - **Platform files**: `.cursor/` (settings, hooks, agents, skills, commands, rules).
 
 Platform files do not store business state. They let Cursor read Trellis state, call Trellis scripts, and load Trellis skills/agents/hooks.
 
-> **Historical note**: Trellis previously shipped adapter directories for many AI tools (`.claude/`, `.codex/`, `.opencode/`, etc.). The project has converged on **Cursor-only**. Legacy adapter directories may still exist in upgraded projects (`trellis update` preserves user files), but new framework/runtime behavior targets Cursor exclusively.
+> **Historical note**: Trellis previously shipped adapter directories for many AI tools (`.claude/`, `.codex/`, `.opencode/`, etc.). The project has converged on **Cursor-only**. Legacy adapter directories may still exist in upgraded projects (`cstl update` preserves user files), but new framework/runtime behavior targets Cursor exclusively.
 
 ## Platform File Categories (Cursor)
 
@@ -18,16 +18,16 @@ Platform files do not store business state. They let Cursor read Trellis state,
 | settings/config | `.cursor/hooks.json` | Register hooks and platform behavior. |
 | hooks | `.cursor/hooks/` | Inject context at session start, pre-tool-use on Task/Subagent, before-shell-execution, and stop events. |
 | rules | `.cursor/rules/*.mdc` (`alwaysApply: true`) | Per-turn policy prepended before every prompt (e.g. Request Triage, retrieval routing). See `cursor-context-injection-guide.md.txt` for the channel-reliability matrix. |
-| agents | `.cursor/agents/` | Define `trellis-research`, `trellis-implement`, and `trellis-check` for Task / Agent-session dispatch. |
+| agents | `.cursor/agents/` | Define `cstl-research`, `cstl-implement`, and `cstl-check` for Task / Agent-session dispatch. |
 | skills | `.cursor/skills/` | Capability descriptions that auto-trigger or can be read on demand. |
-| commands | `.cursor/commands/` | User-invocable `/slash` entry points (e.g. `trellis-continue`, `record-session`). |
+| commands | `.cursor/commands/` | User-invocable `/slash` entry points (e.g. `cstl-continue`, `record-session`). |
 
 ## Cursor Integration Mode
 
 Cursor combines three integration styles:
 
 1. **Hook / Extension Driven** — `.cursor/hooks.json` + `.cursor/hooks/` fire on sessionStart, pre-tool-use on Task/Subagent, beforeShellExecution, and stop. Common capabilities: session-start Task Dashboard + Phase Index injection (note the `additional_context` Cursor bug #158452 — use `.cursor/rules` or `AGENTS.md` for must-always-be-visible content), PRD/jsonl injection when sub-agents start, shell commands inheriting session identity.
-2. **Agent Prelude / Pull-Based** — `.cursor/agents/*.md` instruct each custom Task subagent to read the selected task, PRD, and JSONL context after startup (the `<!-- trellis-hook-injected -->` marker confirms injected context).
+2. **Agent Prelude / Pull-Based** — `.cursor/agents/*.md` instruct each custom Task subagent to read the selected task, PRD, and JSONL context after startup (the `<!-- cstl-hook-injected -->` marker confirms injected context).
 3. **Main-Session Workflow** — `.cursor/commands/*.md` and `.cursor/skills/*.md` guide the main-session AI to read files, run scripts, and move tasks forward; `.cursor/rules/*.mdc` enforce per-turn policy.
 
 To change "when the AI knows what," inspect `.cursor/hooks.json` and `.cursor/rules/` first. To change how sub-agents load context, inspect `.cursor/agents/`. To change user-invocable entry points, inspect `.cursor/commands/` and `.cursor/skills/`.
@@ -36,10 +36,10 @@ To change "when the AI knows what," inspect `.cursor/hooks.json` and `.cursor/ru
 
 When the user asks to customize behavior:
 
-1. Read `.trellis/workflow.md` to confirm the shared flow.
+1. Read `.cstl/workflow.md` to confirm the shared flow.
 2. Read `.cursor/hooks.json` to see which hooks are registered.
 3. Read the relevant `.cursor/agents/*.md`, `.cursor/skills/*/SKILL.md`, `.cursor/commands/*.md`, and `.cursor/rules/*.mdc`.
 4. Modify the local file closest to the user's need.
-5. If the change affects the shared flow, synchronize `.trellis/workflow.md` or `.trellis/spec/`.
+5. If the change affects the shared flow, synchronize `.cstl/workflow.md` or `.cstl/spec/`.
 
-Do not modify only platform files and forget the shared workflow. Do not modify only `.trellis/workflow.md` and forget that platform entry points may still contain old descriptions.
+Do not modify only platform files and forget the shared workflow. Do not modify only `.cstl/workflow.md` and forget that platform entry points may still contain old descriptions.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/platform-files/platform-map.md

@@ -2,7 +2,7 @@
 
 This page lists Trellis file locations in a user project on **Cursor**.
 
-Trellis originally supported multiple AI platforms (Claude Code, Codex, OpenCode, Kilo, Kiro, Gemini, Antigravity, Windsurf, Qoder, CodeBuddy, GitHub Copilot, Factory Droid, Pi Agent). The project has since converged on **Cursor-only**. Legacy adapter directories may still exist in upgraded projects (`trellis update` preserves user files), but new framework/runtime behavior targets Cursor exclusively.
+Trellis originally supported multiple AI platforms (Claude Code, Codex, OpenCode, Kilo, Kiro, Gemini, Antigravity, Windsurf, Qoder, CodeBuddy, GitHub Copilot, Factory Droid, Pi Agent). The project has since converged on **Cursor-only**. Legacy adapter directories may still exist in upgraded projects (`cstl update` preserves user files), but new framework/runtime behavior targets Cursor exclusively.
 
 ## Matrix
 
@@ -13,8 +13,8 @@ Trellis originally supported multiple AI platforms (Claude Code, Codex, OpenCode
 ## Capability Reference (Cursor)
 
 - **Skills** auto-trigger via the workflow matcher and can be read on demand. They live in `.cursor/skills/`.
-- **Agents** (`trellis-research`, `trellis-implement`, `trellis-check`) live in `.cursor/agents/` and are dispatched via the Task tool or opened as Agent sessions / Skill forms depending on the entry point (see `cursor-subagent-policy.md.txt`).
-- **Commands** (e.g. `record-session`, `trellis-continue`) live in `.cursor/commands/` and are user-invocable via `/slash`.
+- **Agents** (`cstl-research`, `cstl-implement`, `cstl-check`) live in `.cursor/agents/` and are dispatched via the Task tool or opened as Agent sessions / Skill forms depending on the entry point (see `cursor-subagent-policy.md.txt`).
+- **Commands** (e.g. `record-session`, `cstl-continue`) live in `.cursor/commands/` and are user-invocable via `/slash`.
 - **Hooks** (session start, pre-tool-use on Task/Subagent, before-shell-execution, stop) are registered in `.cursor/hooks.json` and their handler scripts live in `.cursor/hooks/`.
 - **Project rules** (always-applied policy) live in `.cursor/rules/*.mdc`.
 
@@ -22,9 +22,9 @@ Trellis originally supported multiple AI platforms (Claude Code, Codex, OpenCode
 
 1. User specified a platform other than Cursor: treat as a legacy adapter inspection — preserve existing files but do not extend new behavior there.
 2. User says "all platforms should do this": in Cursor-only world this is equivalent to "modify the Cursor path"; also mirror any dogfooded copy under `.cursor/` in `packages/cli/src/templates/cursor/` if applicable.
-3. User only says "my AI": inspect which directories actually exist in the project; on a fresh `trellis init` only `.cursor/` and `.trellis/` are created.
-4. User wants project rules: prefer `.trellis/spec/` or a project-local skill under `.cursor/skills/`.
-5. User wants Trellis behavior: edit `.trellis/workflow.md` plus `.cursor/hooks.json` / `.cursor/agents/` / `.cursor/skills/` / `.cursor/commands/`.
+3. User only says "my AI": inspect which directories actually exist in the project; on a fresh `cstl init` only `.cursor/` and `.cstl/` are created.
+4. User wants project rules: prefer `.cstl/spec/` or a project-local skill under `.cursor/skills/`.
+5. User wants Trellis behavior: edit `.cstl/workflow.md` plus `.cursor/hooks.json` / `.cursor/agents/` / `.cursor/skills/` / `.cursor/commands/`.
 
 ## When Paths Differ
 
@@ -40,6 +40,6 @@ Do not delete a custom file just because it is not listed in this path table.
 
 If a user project still contains legacy platform directories (e.g. `.claude/`, `.codex/`, `.opencode/`):
 
-- `trellis update` preserves them; do not delete on sight.
+- `cstl update` preserves them; do not delete on sight.
 - If the user asks to clean them up, suggest removing the unused platform directories after confirming they are not shared with another tool.
 - Do not register new hooks/agents/skills/commands under legacy platform directories. New Trellis features ship to `.cursor/` only.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/platform-files/skills-and-commands.md

@@ -16,19 +16,19 @@ Skills and commands are textual entry points for user interaction with Trellis.
 Trellis has two skill families:
 
 - Workflow skills: `brainstorm`, `before-dev`, `check`, `update-spec`, and `break-loop`.
-- Multi-file bundled skills include `trellis-meta`, `trellis-spec-bootstrap`, `trellis-skill-creator`, `smart-search-cli`, `trellis-micro-grill`, and `trellis-cursor2plus-setup`.
+- Multi-file bundled skills include `cstl-meta`, `cstl-spec-bootstrap`, `cstl-skill-creator`, `smart-search-cli`, `cstl-micro-grill`, and `cstl-cursor2plus-setup`.
 
-Bundled skills are installed as directories and may include nested `agents/`, `examples/`, `references/`, or other lazy-loadable files. Do not describe bundled skills as a closed `trellis-*` list: `smart-search-cli` intentionally keeps its existing non-`trellis-` name.
+Bundled skills are installed as directories and may include nested `agents/`, `examples/`, `references/`, or other lazy-loadable files. Do not describe bundled skills as a closed `cstl-*` list: `smart-search-cli` intentionally keeps its existing non-`cstl-` name.
 
 `smart-search-cli` is CLI-backed source retrieval. The Trellis package exposes the `smart-search` executable through its runtime wrapper; the skill documents how agents should use that CLI and cite retrieved sources.
 
-`trellis-spec-bootstrap` bootstraps project-specific `.trellis/spec/` guidance from the real repository.
+`cstl-spec-bootstrap` bootstraps project-specific `.cstl/spec/` guidance from the real repository.
 
-`trellis-skill-creator` is the authoring and review guide for Trellis-compatible skills. Use it when creating or improving project-local skills under `.cursor/skills/`, the shared `.agents/skills/` directory (industry skill-sharing, kept but not extended by new Trellis behavior), or upstream bundled skills. Keep `trellis-meta` focused on architecture and routing.
+`cstl-skill-creator` is the authoring and review guide for Trellis-compatible skills. Use it when creating or improving project-local skills under `.cursor/skills/`, the shared `.agents/skills/` directory (industry skill-sharing, kept but not extended by new Trellis behavior), or upstream bundled skills. Keep `cstl-meta` focused on architecture and routing.
 
-`trellis-micro-grill` is the Trellis clarification adapter. It asks one high-value question at a time and escalates to Lite, Full, or Parent/Child task modes only when durable artifacts or broader risk require it.
+`cstl-micro-grill` is the Trellis clarification adapter. It asks one high-value question at a time and escalates to Lite, Full, or Parent/Child task modes only when durable artifacts or broader risk require it.
 
-`trellis-cursor2plus-setup` guides Cursor++ BYOK users through `trellis-task-models.json5` (primary/fallback per Task role), `patch_wpelc8.py`, and Reload Window. Use after `trellis init --cursor` or when `providers.json` changes.
+`cstl-cursor2plus-setup` guides Cursor++ BYOK users through `trellis-task-models.json5` (primary/fallback per Task role), `patch_wpelc8.py`, and Reload Window. Use after `cstl init --cursor` or when `providers.json` changes.
 
 ## Common Paths (Cursor)
 
@@ -36,20 +36,20 @@ Bundled skills are installed as directories and may include nested `agents/`, `e
 | --- | --- |
 | Cursor | `.cursor/skills/` (preferred); `.cursor/commands/` is legacy compatibility-only |
 
-In a user project, use the files actually generated by init as authoritative. On current Cursor, Trellis prefers Agent Skills for manual entrypoints such as `trellis-continue` and `trellis-finish-work`; legacy `.cursor/commands/` files may exist in older projects but should be treated as an explicit compatibility surface rather than the default current-platform command surface.
+In a user project, use the files actually generated by init as authoritative. On current Cursor, Trellis prefers Agent Skills for manual entrypoints such as `cstl-continue` and `cstl-finish-work`; legacy `.cursor/commands/` files may exist in older projects but should be treated as an explicit compatibility surface rather than the default current-platform command surface.
 
 ## Skill Structure
 
 A common skill is a directory:
 
 ```text
-trellis-meta/
+cstl-meta/
 ├── SKILL.md
 └── references/
-trellis-spec-bootstrap/
+cstl-spec-bootstrap/
 ├── SKILL.md
 └── references/
-trellis-skill-creator/
+cstl-skill-creator/
 ├── SKILL.md
 └── references/
 smart-search-cli/
@@ -57,9 +57,9 @@ smart-search-cli/
 ├── agents/
 ├── examples/
 └── references/
-trellis-micro-grill/
+cstl-micro-grill/
 └── SKILL.md
-trellis-cursor2plus-setup/
+cstl-cursor2plus-setup/
 └── SKILL.md
 ```
 
@@ -76,11 +76,11 @@ References hold longer explanations so the entry file does not contain everythin
 Commands, prompts, and workflows are usually single files. Their content should include:
 
 - When to use it.
-- Which `.trellis/` files to read.
+- Which `.cstl/` files to read.
 - Which scripts to run.
 - How to report after completion.
 
-They should not store task state; task state belongs in `.trellis/tasks/` and `.trellis/.runtime/`.
+They should not store task state; task state belongs in `.cstl/tasks/` and `.cstl/.runtime/`.
 
 Task selection uses `selected_task`, not legacy current/active task commands. The current command chain is:
 
@@ -100,13 +100,13 @@ Do not reintroduce `task.py start`, `task.py current`, or `task.py finish` into
 | Change AI auto-trigger rules | The corresponding skill's frontmatter description. |
 | Change user command behavior | The corresponding command/prompt/workflow file. |
 | Add a project-local skill | `.cursor/skills/` (or `.agents/skills/` only when explicitly sharing with another non-Trellis tool that reads that path). |
-| Change finish/continue entry points | On current Cursor, prefer `.cursor/skills/trellis-continue` and `.cursor/skills/trellis-finish-work` over legacy `.cursor/commands/`. |
+| Change finish/continue entry points | On current Cursor, prefer `.cursor/skills/cstl-continue` and `.cursor/skills/cstl-finish-work` over legacy `.cursor/commands/`. |
 
 ## Modification Principles
 
-1. **Keep entry files short; references carry long content**. This matters especially for multi-file skills like `trellis-meta` and `trellis-skill-creator`.
+1. **Keep entry files short; references carry long content**. This matters especially for multi-file skills like `cstl-meta` and `cstl-skill-creator`.
 2. **Make trigger descriptions specific**. A description that is too broad can mis-trigger; one that is too narrow may not trigger.
-3. **Keep behavior descriptions consistent with the shared `.trellis/` runtime**. Format may differ per file type, but semantics should match the shared workflow.
-4. **Put project-specific capabilities in local skills**. Do not put team-private flows into public `trellis-meta`.
+3. **Keep behavior descriptions consistent with the shared `.cstl/` runtime**. Format may differ per file type, but semantics should match the shared workflow.
+4. **Put project-specific capabilities in local skills**. Do not put team-private flows into public `cstl-meta`.
 
-If the user only wants local AI to know one more project rule, usually create a project-local skill under `.cursor/skills/` or update `.trellis/spec/` instead of changing a Trellis built-in workflow skill.
+If the user only wants local AI to know one more project rule, usually create a project-local skill under `.cursor/skills/` or update `.cstl/spec/` instead of changing a Trellis built-in workflow skill.