@blxzer/cursor-trellis 0.2.8 → 0.3.0

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

@@ -6,10 +6,10 @@ Trellis context injection aims to make AI read the right files at the right time
 
 | Type | Source | Purpose |
 | --- | --- | --- |
-| session context | `.trellis/scripts/get_context.py` | Current developer, git status, selected task, Task Dashboard, active tasks, journal, packages. |
+| session context | `.trellis/scripts/get_context.py` | Current developer, git status, selected task, Task Dashboard, active tasks, journal, packages. |
 | workflow context | `.trellis/workflow.md` | Current Trellis flow and next action. |
 | spec context | `.trellis/spec/` + task JSONL | Specs that must be followed during implementation/checking. |
-| task context | `.trellis/tasks/<task>/prd.md`, `design.md`, `implement.md`, `research/` | Selected task requirements, design, execution plan, and research. |
+| task context | `.trellis/tasks/<task>/prd.md`, `design.md`, `implement.md`, `research/` | Selected task requirements, design, execution plan, and research. |
 | platform context | Platform hooks/settings/agents | Lets different AI tools read the files above through their own mechanisms. |
 
 ## session-start
@@ -17,16 +17,16 @@ Trellis context injection aims to make AI read the right files at the right time
 Platforms with session-start support inject a Trellis overview when a session starts, clears, compacts, or receives a similar event. Injected content usually includes:
 
 - workflow summary.
-- selected task status.
-- active tasks.
+- selected task status.
+- active tasks.
 - spec index paths.
 - developer identity and git status.
 
-If the user feels the AI does not know the selected task in a new session, first check whether the platform's session-start hook or equivalent mechanism is installed and running.
+If the user feels the AI does not know the selected task in a new session, first check whether the platform's session-start hook or equivalent mechanism is installed and running.
 
 ## workflow-state
 
-workflow-state is a lightweight hint injected around each user turn. Based on selected task status, it selects a block from `.trellis/workflow.md`, such as `no_task`, `planning`, `in_progress`, or `completed`.
+workflow-state is a lightweight hint injected around each user turn. Based on selected task status, it selects a block from `.trellis/workflow.md`, such as `no_task`, `planning`, `in_progress`, or `completed`.
 
 If the user wants to change "what the AI should do next in a given state," edit the corresponding state block in `.trellis/workflow.md` first.
 
@@ -35,7 +35,7 @@ If the user wants to change "what the AI should do next in a given state," edit
 Implement and check agents need task context. Trellis has two loading modes:
 
 1. **hook push**: a platform hook injects jsonl-referenced files plus `prd.md`, `design.md` if present, and `implement.md` if present before the agent starts.
-2. **agent pull**: the agent definition instructs the agent to read the selected task, jsonl context, and task artifacts after startup.
+2. **agent pull**: the agent definition instructs the agent to read the selected task, jsonl context, and task artifacts after startup.
 
 In both modes, JSONL files in the task directory are the manifest for spec/research context. Task artifacts are read separately in this order: `prd.md` -> `design.md if present` -> `implement.md if present`.
 
@@ -49,11 +49,11 @@ In both modes, JSONL files in the task directory are the manifest for spec/resea
 
 Readers should skip seed rows without a `file` field. When configuring JSONL, the AI should include only spec/research files, not pre-register code files that will be modified.
 
-## Selected Task And Context Key
-
-Selected task state lives in `.trellis/.runtime/sessions/` and is isolated per session. Hooks try to resolve the context key from platform events, environment variables, transcript paths, or `TRELLIS_CONTEXT_ID`.
-
-If shell commands cannot see the same context key, `task.py selected --source` may report no selected task. In that case, check whether the platform passes session identity into the shell instead of hand-writing a global current-task file.
+## Selected Task And Context Key
+
+Selected task state lives in `.trellis/.runtime/sessions/` and is isolated per session. Hooks try to resolve the context key from platform events, environment variables, transcript paths, or `TRELLIS_CONTEXT_ID`.
+
+If shell commands cannot see the same context key, `task.py selected --source` may report no selected task. In that case, check whether the platform passes session identity into the shell instead of hand-writing a global current-task file.
 
 ## Local Customization Points
 
@@ -63,6 +63,6 @@ If shell commands cannot see the same context key, `task.py selected --source` m
 | Change per-turn workflow-state rules | `[workflow-state:STATUS]` block in `.trellis/workflow.md`. The platform workflow-state hook parses these blocks verbatim and embeds no fallback text. |
 | Change how sub-agents read context | Platform agent definitions, the `inject-subagent-context` hook, or agent preludes. |
 | Change JSONL validation/display | `.trellis/scripts/common/task_context.py`. |
-| Change selected task resolution | `.trellis/scripts/common/active_task.py`. |
+| Change selected task resolution | `.trellis/scripts/common/active_task.py`. |
 
 When modifying context injection, verify two things: new sessions can see the correct task, and sub-agents can see the correct task artifacts/spec/research.

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

@@ -1,83 +1,83 @@
-# Local Files Generated After Init
-
-`trellis init` writes the Trellis runtime into the user project. Later, `trellis update` tries to update Trellis-managed template files, but it uses `.trellis/.template-hashes.json` to determine which files have already been modified by the user.
-
-This page only describes files that are visible and editable inside the user project.
-
-## `.trellis/`
-
-```text
-.trellis/
-├── workflow.md
-├── config.yaml
-├── .developer
-├── .version
-├── .template-hashes.json
-├── .runtime/
-├── scripts/
-├── spec/
-├── tasks/
-└── workspace/
-```
-
-| Path | Usually editable? | Notes |
-| --- | --- | --- |
-| `.trellis/workflow.md` | Yes | Local workflow documentation and AI routing rules. |
-| `.trellis/config.yaml` | Yes | Project configuration, hooks, packages, journal line limits, and related settings. |
-| `.trellis/spec/` | Yes | Project specs, intended to be updated regularly by users and AI. |
-| `.trellis/tasks/` | Yes | Task material and research artifacts, maintained by the task workflow. |
-| `.trellis/workspace/` | Yes | Session records, usually written by `add_session.py`. |
-| `.trellis/scripts/` | Carefully | Local runtime. It can be customized, but only after understanding the call chain. |
-| `.trellis/.runtime/` | No | Runtime state, usually written automatically by hooks/scripts. |
-| `.trellis/.developer` | Carefully | Current developer identity. |
-| `.trellis/.version` | No | Trellis version record used by update/migration logic. |
-| `.trellis/.template-hashes.json` | No | Template hash record. Do not hand-write business rules here. |
-
-## Platform Directories
-
-On a fresh `trellis init --cursor`, the only platform directory created is `.cursor/`. Trellis previously generated per-platform directories for many AI tools (`.claude/`, `.codex/`, `.opencode/`, etc.); those legacy directories are preserved by `trellis update` but new Trellis behavior ships to `.cursor/` only.
-
-Common categories inside `.cursor/`:
-
-| Category | Path | Purpose |
-| --- | --- | --- |
-| hooks | `.cursor/hooks/` | Hook scripts invoked from `.cursor/hooks.json`. Inject session context, workflow-state, and sub-agent context. |
-| settings/registration | `.cursor/hooks.json` | Registers which scripts run on which Cursor events. |
-| rules | `.cursor/rules/*.mdc` (`alwaysApply: true`) | Per-turn policy prepended before every prompt. |
-| agents | `.cursor/agents/` | Define agents such as `trellis-research`, `trellis-implement`, and `trellis-check`. |
-| skills | `.cursor/skills/` | Skills that auto-trigger or can be read by AI. |
-| commands | `.cursor/commands/` | Legacy compatibility-only user-invoked entry points. |
-
-When modifying a platform directory, also confirm whether `.trellis/workflow.md` still describes the same flow.
-
-## Meaning Of Template Hashes
-
-`.trellis/.template-hashes.json` records the content hash from the last time Trellis wrote a template file. `trellis update` uses it to distinguish three cases:
-
-| Case | Update behavior |
-| --- | --- |
-| File was not modified by the user | It can be updated automatically. |
-| File was modified by the user | Prompt the user to overwrite, keep, or generate `.new`. |
-| File is no longer a current template | It may be deleted, renamed, or preserved according to migration rules. |
-
-When an AI customizes local Trellis files, it does not need to maintain hashes manually. It is normal for Trellis update to recognize the result as "modified by the user."
-
-## Local Customization Boundaries
-
-Editable by default:
-
-- `.trellis/workflow.md`
-- `.trellis/config.yaml`
-- `.trellis/spec/**`
-- `.trellis/scripts/**`
-- Platform hooks, settings, agents, skills, commands, prompts, and workflows
-
-Do not edit by default:
-
-- Global npm install directory
-- `node_modules/@blxzer/cursor-trellis`
-- Trellis GitHub repository source code
-- Concrete state files under `.trellis/.runtime/**`
-- Hash contents inside `.trellis/.template-hashes.json`
-
-Switch to the Trellis CLI source-code perspective only when the user explicitly wants to contribute upstream.
+# Local Files Generated After Init
+
+`cstl init` writes the Trellis runtime into the user project. Later, `cstl update` tries to update Trellis-managed template files, but it uses `.trellis/.template-hashes.json` to determine which files have already been modified by the user.
+
+This page only describes files that are visible and editable inside the user project.
+
+## `.trellis/`
+
+```text
+.trellis/
+├── workflow.md
+├── config.yaml
+├── .developer
+├── .version
+├── .template-hashes.json
+├── .runtime/
+├── scripts/
+├── spec/
+├── tasks/
+└── workspace/
+```
+
+| Path | Usually editable? | Notes |
+| --- | --- | --- |
+| `.trellis/workflow.md` | Yes | Local workflow documentation and AI routing rules. |
+| `.trellis/config.yaml` | Yes | Project configuration, hooks, packages, journal line limits, and related settings. |
+| `.trellis/spec/` | Yes | Project specs, intended to be updated regularly by users and AI. |
+| `.trellis/tasks/` | Yes | Task material and research artifacts, maintained by the task workflow. |
+| `.trellis/workspace/` | Yes | Session records, usually written by `add_session.py`. |
+| `.trellis/scripts/` | Carefully | Local runtime. It can be customized, but only after understanding the call chain. |
+| `.trellis/.runtime/` | No | Runtime state, usually written automatically by hooks/scripts. |
+| `.trellis/.developer` | Carefully | Current developer identity. |
+| `.trellis/.version` | No | Trellis version record used by update/migration logic. |
+| `.trellis/.template-hashes.json` | No | Template hash record. Do not hand-write business rules here. |
+
+## Platform Directories
+
+On a fresh `cstl init --cursor`, the only platform directory created is `.cursor/`. Trellis previously generated per-platform directories for many AI tools (`.claude/`, `.codex/`, `.opencode/`, etc.); those legacy directories are preserved by `cstl update` but new Trellis behavior ships to `.cursor/` only.
+
+Common categories inside `.cursor/`:
+
+| Category | Path | Purpose |
+| --- | --- | --- |
+| hooks | `.cursor/hooks/` | Hook scripts invoked from `.cursor/hooks.json`. Inject session context, workflow-state, and sub-agent context. |
+| settings/registration | `.cursor/hooks.json` | Registers which scripts run on which Cursor events. |
+| rules | `.cursor/rules/*.mdc` (`alwaysApply: true`) | Per-turn policy prepended before every prompt. |
+| agents | `.cursor/agents/` | Define agents such as `cstl-research`, `cstl-implement`, and `cstl-check`. |
+| skills | `.cursor/skills/` | Skills that auto-trigger or can be read by AI. |
+| commands | `.cursor/commands/` | Legacy compatibility-only user-invoked entry points. |
+
+When modifying a platform directory, also confirm whether `.trellis/workflow.md` still describes the same flow.
+
+## Meaning Of Template Hashes
+
+`.trellis/.template-hashes.json` records the content hash from the last time Trellis wrote a template file. `cstl update` uses it to distinguish three cases:
+
+| Case | Update behavior |
+| --- | --- |
+| File was not modified by the user | It can be updated automatically. |
+| File was modified by the user | Prompt the user to overwrite, keep, or generate `.new`. |
+| File is no longer a current template | It may be deleted, renamed, or preserved according to migration rules. |
+
+When an AI customizes local Trellis files, it does not need to maintain hashes manually. It is normal for Trellis update to recognize the result as "modified by the user."
+
+## Local Customization Boundaries
+
+Editable by default:
+
+- `.trellis/workflow.md`
+- `.trellis/config.yaml`
+- `.trellis/spec/**`
+- `.trellis/scripts/**`
+- Platform hooks, settings, agents, skills, commands, prompts, and workflows
+
+Do not edit by default:
+
+- Global npm install directory
+- `node_modules/@blxzer/cursor-trellis`
+- Trellis GitHub repository source code
+- Concrete state files under `.trellis/.runtime/**`
+- Hash contents inside `.trellis/.template-hashes.json`
+
+Switch to the Trellis CLI source-code perspective only when the user explicitly wants to contribute upstream.

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

@@ -1,6 +1,6 @@
 # Local Trellis Architecture Overview
 
-`trellis-meta` is for user projects that have already run `trellis init`. The user's machine usually has only the npm-installed `trellis` command plus the Trellis files generated inside the project; it may not have the Trellis CLI source code.
+`cstl-meta` is for user projects that have already run `cstl init`. The user's machine usually has only the npm-installed `cstl` command plus the Trellis files generated inside the project; it may not have the Trellis CLI source code.
 
 Therefore, when an AI uses this skill, the default customization target is local files inside the user project:
 
@@ -38,7 +38,7 @@ All three layers live inside the user project, so an AI can read and modify them
 1. **Find the local source of truth first**: Do not edit from memory. Read `.trellis/workflow.md`, `.trellis/config.yaml`, the relevant platform directory, and related task files first.
 2. **Edit the user project, not the npm package cache**: Modify generated files inside the project, not `node_modules` or the global npm install directory.
 3. **Keep platform files aligned with `.trellis/`**: If workflow routing changes, also check whether platform skills or commands still describe the same flow.
-4. **Put project-specific rules in `.trellis/spec/` or a local skill**: Do not put team conventions into `trellis-meta`.
+4. **Put project-specific rules in `.trellis/spec/` or a local skill**: Do not put team conventions into `cstl-meta`.
 5. **Preserve user changes**: If a file was already modified locally, work from the current content instead of overwriting it with a default template.
 
 ## How To Use This Directory

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

@@ -95,7 +95,7 @@ When the AI learns a new rule during implementation or debugging, it should upda
 | Change monorepo spec mapping | `packages` / `default_package` / `spec_scope` in `.trellis/config.yaml`. |
 | Change which specs AI reads before implementation | The task's `implement.jsonl`. |
 | Change which specs AI reads during checking | The task's `check.jsonl`. |
-| Change when specs should be updated | Phase 3.3 in `.trellis/workflow.md` and the `trellis-update-spec` skill. |
+| Change when specs should be updated | Phase 3.3 in `.trellis/workflow.md` and the `cstl-update-spec` skill. |
 
 ## Boundaries
 

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

@@ -73,17 +73,17 @@ python3 ./.trellis/scripts/task.py remove-subtask <parent-dir> <child-dir>
 
 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
+.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.
 
 ## JSONL Context
 
@@ -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 ./.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>
+```
 
 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.
 

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

@@ -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. |
@@ -68,7 +68,7 @@ After editing, make the AI reread `.trellis/workflow.md`; do not assume the flow
 
 `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

@@ -53,8 +53,8 @@ Planning or review work without a commit can also be recorded by using `--no-com
 | `.trellis/workspace/` | Work records across tasks and sessions. |
 | `.trellis/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
@@ -68,4 +68,4 @@ If information should be followed every time code is written in the future, put
 
 ## 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.
 
@@ -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 `.trellis/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

@@ -13,7 +13,7 @@ Hooks/settings are the entry layer that connects Cursor to Trellis. They decide
 
 > 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 |
 | --- | --- |

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

@@ -9,7 +9,7 @@ When a local AI modifies Trellis, it should distinguish two file categories firs
 
 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/`.

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,7 +22,7 @@ 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.
+3. User only says "my AI": inspect which directories actually exist in the project; on a fresh `cstl 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/`.
 
@@ -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 `.trellis/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
 ```
 
@@ -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`.
+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.