@blxzer/cursor-trellis 0.2.9 → 0.3.2

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/SKILL.md

@@ -1,75 +1,75 @@
----
-name: trellis-meta
-description: "Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, or workflows generated by trellis init."
----
-
-# Trellis Meta
-
-This skill is for local Trellis users who have already run `trellis init` in a project. After reading it, an AI should understand the Trellis architecture, operating model, and customization entry points inside that user project, then modify the generated `.trellis/` and platform directory files according to the user's request.
-
-The default operating scope is local files in the user project:
-
-- `.trellis/`: workflow, config, tasks, spec, workspace, scripts, and runtime state.
-- Platform directory: `.cursor/` — skills, agents, hooks, commands, rules.
-- Shared skill layer: `.agents/skills/` (industry skill-sharing path, kept when present but not extended by new Trellis behavior).
-
-Trellis previously supported many AI-platform adapter directories (`.claude/`, `.codex/`, `.opencode/`, `.kiro/`, `.gemini/`, `.qoder/`, `.codebuddy/`, `.github/`, `.factory/`, `.pi/`, `.kilocode/`, `.agent/`, `.windsurf/`). The project has converged on **Cursor-only**. Legacy adapter directories in upgraded projects are preserved by `trellis update` but new Trellis behavior ships to `.cursor/` only.
-
-Do not assume the user has the Trellis source repository. Do not default to modifying the global npm install directory or `node_modules`.
-
-## How To Use
-
-1. Read `references/local-architecture/overview.md` first to establish the local Trellis system model.
-2. If the request involves a specific AI tool, read `references/platform-files/platform-map.md` and the relevant platform file notes.
-3. If the user wants to change behavior, read `references/customize-local/overview.md`, then open the specific customization topic.
-4. Before editing, read the actual files in the user project and treat local content as authoritative.
-
-## References
-
-### Local Architecture
-
-- `references/local-architecture/overview.md`: The three-layer local Trellis architecture and customization principles.
-- `references/local-architecture/generated-files.md`: Files generated by `trellis init` and their customization boundaries.
-- `references/local-architecture/workflow.md`: Phases, routing, and workflow-state blocks in `.trellis/workflow.md`.
-- `references/local-architecture/task-system.md`: Task directories, selected tasks, JSONL context, and task runtime.
-- `references/local-architecture/spec-system.md`: How `.trellis/spec/` is organized and injected.
-- `references/local-architecture/workspace-memory.md`: `.trellis/workspace/`, journals, and cross-session memory.
-- `references/local-architecture/context-injection.md`: Hooks, sub-agent preludes, and context injection paths.
-
-### Platform Files
-
-- `references/platform-files/overview.md`: How shared `.trellis/` files relate to platform directories.
-- `references/platform-files/platform-map.md`: Platform directories and paths for skills, agents, hooks, and extensions.
-- `references/platform-files/hooks-and-settings.md`: How settings/config files, hooks, plugins, and extensions connect to Trellis.
-- `references/platform-files/agents.md`: Local file responsibilities for `trellis-research`, `trellis-implement`, and `trellis-check`.
-- `references/platform-files/skills-and-commands.md`: Differences between skills, commands, prompts, and workflows, plus how to change them.
-
-### Local Customization
-
-- `references/customize-local/overview.md`: Choose the right local customization entry point for the user's request.
-- `references/customize-local/change-workflow.md`: Change phases, routing, next actions, and workflow-state.
-- `references/customize-local/change-task-lifecycle.md`: Change task creation, status, archive behavior, and hooks.
-- `references/customize-local/change-context-loading.md`: Change how tasks, specs, journals, and hook context are loaded.
-- `references/customize-local/change-hooks.md`: Change platform hooks, settings, and shell session bridges.
-- `references/customize-local/change-agents.md`: Change research, implement, and check agent behavior.
-- `references/customize-local/change-skills-or-commands.md`: Add or modify local skills, commands, prompts, and workflows.
-- `references/customize-local/change-spec-structure.md`: Adjust the project spec structure under `.trellis/spec/`.
-- `references/customize-local/add-project-local-conventions.md`: Put team rules into project-local specs or local skills.
-
-## Current Rules
-
-- `.trellis/workflow.md` is the local workflow source of truth.
-- `.trellis/config.yaml` is the project-level Trellis configuration and task hook configuration entry point.
-- `.trellis/spec/` stores the user's project-specific coding conventions and design constraints.
-- `.trellis/tasks/` stores task PRDs, technical notes, research files, and JSONL context.
-- `.trellis/workspace/` stores developer journals and cross-session memory.
-- Platform settings/config files decide which hooks, agents, skills, commands, prompts, and workflows actually run.
-- `.trellis/.template-hashes.json` and `.trellis/.runtime/` are management/runtime state files. Confirm necessity before editing them.
-
-## Do Not
-
-- Do not treat Trellis upstream source code as the default target for local customization.
-- Do not modify the global npm install directory or `node_modules/@blxzer/cursor-trellis` to implement project needs.
-- Do not overwrite user-modified local files with default templates.
-- Do not put team-private project rules into the public `trellis-meta`; put project rules in `.trellis/spec/` or a project-local skill.
-- Do not describe removed historical mechanisms as current Trellis behavior.
+---
+name: cstl-meta
+description: "Understand and customize the local Trellis architecture inside a user project. Use when modifying .cstl plus platform hooks, settings, agents, skills, commands, prompts, or workflows generated by cstl init."
+---
+
+# Trellis Meta
+
+This skill is for local Trellis users who have already run `cstl init` in a project. After reading it, an AI should understand the Trellis architecture, operating model, and customization entry points inside that user project, then modify the generated `.cstl/` and platform directory files according to the user's request.
+
+The default operating scope is local files in the user project:
+
+- `.cstl/`: workflow, config, tasks, spec, workspace, scripts, and runtime state.
+- Platform directory: `.cursor/` — skills, agents, hooks, commands, rules.
+- Shared skill layer: `.agents/skills/` (industry skill-sharing path, kept when present but not extended by new Trellis behavior).
+
+Trellis previously supported many AI-platform adapter directories (`.claude/`, `.codex/`, `.opencode/`, `.kiro/`, `.gemini/`, `.qoder/`, `.codebuddy/`, `.github/`, `.factory/`, `.pi/`, `.kilocode/`, `.agent/`, `.windsurf/`). The project has converged on **Cursor-only**. Legacy adapter directories in upgraded projects are preserved by `cstl update` but new Trellis behavior ships to `.cursor/` only.
+
+Do not assume the user has the Trellis source repository. Do not default to modifying the global npm install directory or `node_modules`.
+
+## How To Use
+
+1. Read `references/local-architecture/overview.md` first to establish the local Trellis system model.
+2. If the request involves a specific AI tool, read `references/platform-files/platform-map.md` and the relevant platform file notes.
+3. If the user wants to change behavior, read `references/customize-local/overview.md`, then open the specific customization topic.
+4. Before editing, read the actual files in the user project and treat local content as authoritative.
+
+## References
+
+### Local Architecture
+
+- `references/local-architecture/overview.md`: The three-layer local Trellis architecture and customization principles.
+- `references/local-architecture/generated-files.md`: Files generated by `cstl init` and their customization boundaries.
+- `references/local-architecture/workflow.md`: Phases, routing, and workflow-state blocks in `.cstl/workflow.md`.
+- `references/local-architecture/task-system.md`: Task directories, selected tasks, JSONL context, and task runtime.
+- `references/local-architecture/spec-system.md`: How `.cstl/spec/` is organized and injected.
+- `references/local-architecture/workspace-memory.md`: `.cstl/workspace/`, journals, and cross-session memory.
+- `references/local-architecture/context-injection.md`: Hooks, sub-agent preludes, and context injection paths.
+
+### Platform Files
+
+- `references/platform-files/overview.md`: How shared `.cstl/` files relate to platform directories.
+- `references/platform-files/platform-map.md`: Platform directories and paths for skills, agents, hooks, and extensions.
+- `references/platform-files/hooks-and-settings.md`: How settings/config files, hooks, plugins, and extensions connect to Trellis.
+- `references/platform-files/agents.md`: Local file responsibilities for `cstl-research`, `cstl-implement`, and `cstl-check`.
+- `references/platform-files/skills-and-commands.md`: Differences between skills, commands, prompts, and workflows, plus how to change them.
+
+### Local Customization
+
+- `references/customize-local/overview.md`: Choose the right local customization entry point for the user's request.
+- `references/customize-local/change-workflow.md`: Change phases, routing, next actions, and workflow-state.
+- `references/customize-local/change-task-lifecycle.md`: Change task creation, status, archive behavior, and hooks.
+- `references/customize-local/change-context-loading.md`: Change how tasks, specs, journals, and hook context are loaded.
+- `references/customize-local/change-hooks.md`: Change platform hooks, settings, and shell session bridges.
+- `references/customize-local/change-agents.md`: Change research, implement, and check agent behavior.
+- `references/customize-local/change-skills-or-commands.md`: Add or modify local skills, commands, prompts, and workflows.
+- `references/customize-local/change-spec-structure.md`: Adjust the project spec structure under `.cstl/spec/`.
+- `references/customize-local/add-project-local-conventions.md`: Put team rules into project-local specs or local skills.
+
+## Current Rules
+
+- `.cstl/workflow.md` is the local workflow source of truth.
+- `.cstl/config.yaml` is the project-level Trellis configuration and task hook configuration entry point.
+- `.cstl/spec/` stores the user's project-specific coding conventions and design constraints.
+- `.cstl/tasks/` stores task PRDs, technical notes, research files, and JSONL context.
+- `.cstl/workspace/` stores developer journals and cross-session memory.
+- Platform settings/config files decide which hooks, agents, skills, commands, prompts, and workflows actually run.
+- `.cstl/.template-hashes.json` and `.cstl/.runtime/` are management/runtime state files. Confirm necessity before editing them.
+
+## Do Not
+
+- Do not treat Trellis upstream source code as the default target for local customization.
+- Do not modify the global npm install directory or `node_modules/@blxzer/cursor-trellis` to implement project needs.
+- Do not overwrite user-modified local files with default templates.
+- Do not put team-private project rules into the public `cstl-meta`; put project rules in `.cstl/spec/` or a project-local skill.
+- Do not describe removed historical mechanisms as current Trellis behavior.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/customize-local/add-project-local-conventions.md

@@ -1,16 +1,16 @@
 # Add Project-Local Conventions
 
-Often the user does not need to change Trellis mechanics; they need local AI to understand their team's conventions. In that case, prefer `.trellis/spec/` or a project-local skill instead of editing `trellis-meta`.
+Often the user does not need to change Trellis mechanics; they need local AI to understand their team's conventions. In that case, prefer `.cstl/spec/` or a project-local skill instead of editing `cstl-meta`.
 
 ## Where To Put Things
 
 | Content type | Location |
 | --- | --- |
-| Rules code must follow | `.trellis/spec/<layer>/` |
-| Cross-layer thinking methods | `.trellis/spec/guides/` |
+| Rules code must follow | `.cstl/spec/<layer>/` |
+| Cross-layer thinking methods | `.cstl/spec/guides/` |
 | AI capability for a project-specific flow | Platform-local skill |
-| One-off task material | `.trellis/tasks/<task>/` |
-| Session summary | `.trellis/workspace/<developer>/journal-N.md` |
+| One-off task material | `.cstl/tasks/<task>/` |
+| Session summary | `.cstl/workspace/<developer>/journal-N.md` |
 
 ## Create A Project-Local Skill
 
@@ -50,34 +50,34 @@ This skill documents this repository's Trellis customizations only.
 
 For multi-platform projects, place equivalent versions in other platform skill directories, or use `.agents/skills/` for platforms that support the shared layer.
 
-## Write To `.trellis/spec/`
+## Write To `.cstl/spec/`
 
 If the content is a coding convention, write it to spec. Examples:
 
 ```text
-.trellis/spec/backend/error-handling.md
-.trellis/spec/frontend/components.md
-.trellis/spec/guides/cross-platform-thinking-guide.md
+.cstl/spec/backend/error-handling.md
+.cstl/spec/frontend/components.md
+.cstl/spec/guides/cross-platform-thinking-guide.md
 ```
 
 After writing it, update the corresponding `index.md` so AI can find the new rule from the entry point.
 
-## Make The Selected Task Use New Conventions
-
-After writing a spec, add it to the selected task context:
+## Make The Selected Task Use New Conventions
+
+After writing a spec, add it to the selected task context:
 
 ```bash
-python3 ./.trellis/scripts/task.py add-context <task> implement ".trellis/spec/backend/error-handling.md" "Error handling conventions"
-python3 ./.trellis/scripts/task.py add-context <task> check ".trellis/spec/backend/error-handling.md" "Review error handling"
+python3 ./.cstl/scripts/task.py add-context <task> implement ".cstl/spec/backend/error-handling.md" "Error handling conventions"
+python3 ./.cstl/scripts/task.py add-context <task> check ".cstl/spec/backend/error-handling.md" "Review error handling"
 ```
 
-## Do Not Store Project-Private Rules In `trellis-meta`
+## Do Not Store Project-Private Rules In `cstl-meta`
 
-`trellis-meta` is a public skill for understanding Trellis architecture and local customization entry points. Put project-private content in:
+`cstl-meta` is a public skill for understanding Trellis architecture and local customization entry points. Put project-private content in:
 
-- `.trellis/spec/`
+- `.cstl/spec/`
 - a project-local skill
-- the selected task
+- the selected task
 - workspace journal
 
-This prevents future updates to Trellis's built-in `trellis-meta` from overwriting the team's own conventions.
+This prevents future updates to Trellis's built-in `cstl-meta` from overwriting the team's own conventions.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/customize-local/change-agents.md

@@ -1,11 +1,11 @@
 # Change Local Agents
 
-When the user wants to change `trellis-research`, `trellis-implement`, or `trellis-check` behavior, edit platform agent files in the user project.
+When the user wants to change `cstl-research`, `cstl-implement`, or `cstl-check` behavior, edit platform agent files in the user project.
 
 ## Read These Files First
 
 1. Target platform agent directory
-2. `.trellis/workflow.md` Phase 2 / research routing
+2. `.cstl/workflow.md` Phase 2 / research routing
 3. Selected task `prd.md`
 4. Selected task `implement.jsonl` / `check.jsonl`
 5. Relevant hook or agent prelude
@@ -14,7 +14,7 @@ When the user wants to change `trellis-research`, `trellis-implement`, or `trell
 
 | Platform | Path |
 | --- | --- |
-| Cursor | `.cursor/agents/trellis-*.md` |
+| Cursor | `.cursor/agents/cstl-*.md` |
 
 If a user project still contains legacy platform agent directories (`.claude/agents/`, `.codex/agents/`, etc.), inspect them but route new agent definitions to `.cursor/agents/`.
 
@@ -24,19 +24,19 @@ Use the actual paths in the user project as authoritative.
 
 | Need | Which agent to edit |
 | --- | --- |
-| Research must write files, not only reply in chat | `trellis-research` |
-| Certain local specs must be read before implementation | `trellis-implement` + `implement.jsonl` configuration rules |
-| Specific commands must run during checking | `trellis-check` |
+| Research must write files, not only reply in chat | `cstl-research` |
+| Certain local specs must be read before implementation | `cstl-implement` + `implement.jsonl` configuration rules |
+| Specific commands must run during checking | `cstl-check` |
 | Agent must not modify certain directories | The corresponding agent's write boundary instructions |
 | Agent output format must be fixed | The corresponding agent's final/reporting instructions |
 
 ## Modification Principles
 
 1. **Preserve role boundaries**: research investigates and persists; implement writes implementation; check reviews and fixes.
-2. **Do not hard-code project specs into agents**: long-term specs belong in `.trellis/spec/`; agents are responsible for reading them.
+2. **Do not hard-code project specs into agents**: long-term specs belong in `.cstl/spec/`; agents are responsible for reading them.
 3. **Make read order explicit**: selected task -> PRD -> info -> JSONL -> spec/research.
 4. **Make write boundaries explicit**: which directories may be written and which may not.
-5. **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.
+5. **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.
 
 ## Agent Pull Mode
 

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/customize-local/change-context-loading.md

@@ -1,29 +1,29 @@
 # Change Local Context Loading
 
-Context loading determines when AI reads workflow, task, spec, research, workspace, and git status. Read this page when the user says "AI does not know the selected task," "the agent did not read specs," or "there is too much/too little context."
+Context loading determines when AI reads workflow, task, spec, research, workspace, and git status. Read this page when the user says "AI does not know the selected task," "the agent did not read specs," or "there is too much/too little context."
 
 ## Read These Files First
 
-1. `.trellis/workflow.md`
-2. `.trellis/scripts/get_context.py`
-3. `.trellis/scripts/common/session_context.py`
-4. `.trellis/scripts/common/task_context.py`
-5. `.trellis/scripts/common/active_task.py`
+1. `.cstl/workflow.md`
+2. `.cstl/scripts/get_context.py`
+3. `.cstl/scripts/common/session_context.py`
+4. `.cstl/scripts/common/task_context.py`
+5. `.cstl/scripts/common/active_task.py`
 6. Current platform hooks or agent files
-7. The selected task's `implement.jsonl` / `check.jsonl`
+7. The selected task's `implement.jsonl` / `check.jsonl`
 
 ## Context Sources
 
 | Source | Purpose |
 | --- | --- |
-| `.trellis/workflow.md` | Workflow and next-action hints. |
-| `.trellis/tasks/<task>/prd.md` | Selected task requirements. |
-| `.trellis/tasks/<task>/design.md` | Complex task technical design. |
-| `.trellis/tasks/<task>/implement.md` | Complex task execution plan. |
-| `.trellis/tasks/<task>/implement.jsonl` | Spec/research to read before implementation. |
-| `.trellis/tasks/<task>/check.jsonl` | Spec/research to read during checking. |
-| `.trellis/spec/` | Project specs. |
-| `.trellis/workspace/` | Session records. |
+| `.cstl/workflow.md` | Workflow and next-action hints. |
+| `.cstl/tasks/<task>/prd.md` | Selected task requirements. |
+| `.cstl/tasks/<task>/design.md` | Complex task technical design. |
+| `.cstl/tasks/<task>/implement.md` | Complex task execution plan. |
+| `.cstl/tasks/<task>/implement.jsonl` | Spec/research to read before implementation. |
+| `.cstl/tasks/<task>/check.jsonl` | Spec/research to read during checking. |
+| `.cstl/spec/` | Project specs. |
+| `.cstl/workspace/` | Session records. |
 | git status | Current working tree changes. |
 
 ## Common Needs And Edit Points
@@ -31,9 +31,9 @@ Context loading determines when AI reads workflow, task, spec, research, workspa
 | Need | Edit point |
 | --- | --- |
 | Inject more/less information in new sessions | `session_context.py` or the platform `session-start` hook. |
-| Change hints on each user input | `[workflow-state:STATUS]` block in `.trellis/workflow.md`. The `inject-workflow-state` hook is parser-only and reads the block verbatim. |
+| Change hints on each user input | `[workflow-state:STATUS]` block in `.cstl/workflow.md`. The `inject-workflow-state` hook is parser-only and reads the block verbatim. |
 | Agent did not read specs | Task JSONL, agent prelude, `inject-subagent-context` hook. |
-| Selected task is lost | `active_task.py` and platform session identity propagation. |
+| Selected task is lost | `active_task.py` and platform session identity propagation. |
 | Change JSONL validation rules | `task_context.py`. |
 
 ## JSONL Rules
@@ -41,8 +41,8 @@ Context loading determines when AI reads workflow, task, spec, research, workspa
 `implement.jsonl` / `check.jsonl` are the key context loading interface:
 
 ```jsonl
-{"file": ".trellis/spec/backend/index.md", "reason": "Backend conventions"}
-{"file": ".trellis/tasks/04-28-x/research/api.md", "reason": "API research"}
+{"file": ".cstl/spec/backend/index.md", "reason": "Backend conventions"}
+{"file": ".cstl/tasks/04-28-x/research/api.md", "reason": "API research"}
 ```
 
 Include only spec/research files. Do not put code files that will be modified into these manifests; agents read code files themselves during implementation.
@@ -51,7 +51,7 @@ Include only spec/research files. Do not put code files that will be modified in
 
 If the user wants every new session to see more project state, edit:
 
-- `.trellis/scripts/common/session_context.py`
+- `.cstl/scripts/common/session_context.py`
 - the corresponding platform `session-start` hook
 
 Context cannot grow without bound. Prefer injecting indexes and paths so the AI can read detailed files on demand.
@@ -61,11 +61,11 @@ Context cannot grow without bound. Prefer injecting indexes and paths so the AI
 First determine which mode the platform uses:
 
 - hook push: edit the `inject-subagent-context` hook.
-- agent pull: edit the read steps in the corresponding `trellis-implement` / `trellis-check` agent file.
+- agent pull: edit the read steps in the corresponding `cstl-implement` / `cstl-check` agent file.
 
 In both modes, make sure the agent ultimately reads:
 
-1. selected task
+1. selected task
 2. the corresponding JSONL
 3. spec/research referenced by the JSONL
 4. `prd.md`
@@ -75,10 +75,10 @@ In both modes, make sure the agent ultimately reads:
 ## Troubleshooting Order
 
 ```bash
-python3 ./.trellis/scripts/task.py selected --source
-python3 ./.trellis/scripts/task.py list-context <task>
-python3 ./.trellis/scripts/task.py validate <task>
-python3 ./.trellis/scripts/get_context.py --mode packages
+python3 ./.cstl/scripts/task.py selected --source
+python3 ./.cstl/scripts/task.py list-context <task>
+python3 ./.cstl/scripts/task.py validate <task>
+python3 ./.cstl/scripts/get_context.py --mode packages
 ```
 
 Confirm the task and JSONL are correct before editing hooks/agents.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/customize-local/change-hooks.md

@@ -6,9 +6,9 @@ Hooks are the automation layer that connects a platform to Trellis. When the use
 
 1. Target platform settings/config: `.cursor/hooks.json`
 2. Target platform hooks directory
-3. `.trellis/scripts/common/active_task.py`
-4. `.trellis/scripts/common/session_context.py`
-5. `.trellis/workflow.md`
+3. `.cstl/scripts/common/active_task.py`
+4. `.cstl/scripts/common/session_context.py`
+5. `.cstl/workflow.md`
 
 ## Common Hook Types
 
@@ -23,9 +23,9 @@ Hooks are the automation layer that connects a platform to Trellis. When the use
 
 1. Find the hook registration in settings/config.
 2. Confirm the registered script path exists.
-3. Read the hook script and identify inputs, outputs, and called `.trellis/scripts/`.
+3. Read the hook script and identify inputs, outputs, and called `.cstl/scripts/`.
 4. Modify hook behavior.
-5. If the hook depends on workflow content, synchronize `.trellis/workflow.md`.
+5. If the hook depends on workflow content, synchronize `.cstl/workflow.md`.
 
 ## Example: Change New-Session Injection Content
 
@@ -36,15 +36,15 @@ First find the session-start hook:
 .cursor/hooks/session-start.py
 ```
 
-If the hook ultimately calls `.trellis/scripts/get_context.py` or `session_context.py`, editing the local script is usually more robust than hard-coding content in the hook.
+If the hook ultimately calls `.cstl/scripts/get_context.py` or `session_context.py`, editing the local script is usually more robust than hard-coding content in the hook.
 
 ## Example: Agent Did Not Read JSONL
 
 First confirm:
 
 ```bash
-python3 ./.trellis/scripts/task.py selected --source
-python3 ./.trellis/scripts/task.py validate <task>
+python3 ./.cstl/scripts/task.py selected --source
+python3 ./.cstl/scripts/task.py validate <task>
 ```
 
 If the task and JSONL are correct, determine whether the platform uses hook push or agent pull. For hook push, edit `inject-subagent-context`; for agent pull, edit the agent file.
@@ -53,5 +53,5 @@ If the task and JSONL are correct, determine whether the platform uses hook push
 
 - Settings handle registration, hook scripts handle behavior; inspect both together.
 - Cursor's hook event surface has changed between releases; confirm against the current Cursor build before wiring a new event.
-- Hooks should read project-local `.trellis/`; they should not depend on Trellis upstream source paths.
+- Hooks should read project-local `.cstl/`; they should not depend on Trellis upstream source paths.
 - Hook failures should produce visible errors so AI does not silently lose context.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/customize-local/change-skills-or-commands.md

@@ -4,10 +4,10 @@ When the user wants to change AI entry points, auto-trigger rules, or explicit c
 
 ## Read These Files First
 
-1. `.trellis/workflow.md`
+1. `.cstl/workflow.md`
 2. Target platform skill/command/prompt/workflow directory
 3. Related agent or hook files
-4. Whether project rules already exist in `.trellis/spec/`
+4. Whether project rules already exist in `.cstl/spec/`
 
 ## Which Entry Type To Choose
 
@@ -15,8 +15,8 @@ When the user wants to change AI entry points, auto-trigger rules, or explicit c
 | --- | --- |
 | AI should automatically know a capability | Add or modify a skill. |
 | User wants to trigger manually with a command | Add or modify a command/prompt/workflow. |
-| Team project conventions | Prefer `.trellis/spec/` or a project-local skill. |
-| Change Trellis flow semantics | Synchronize `.trellis/workflow.md`. |
+| Team project conventions | Prefer `.cstl/spec/` or a project-local skill. |
+| Change Trellis flow semantics | Synchronize `.cstl/workflow.md`. |
 
 ## Modify A Skill
 
@@ -30,7 +30,7 @@ A skill is usually:
 
 `SKILL.md` should be short and responsible for triggering/routing. Put long content in `references/` so AI can read it on demand.
 
-For detailed skill authoring and review rules, use `trellis-skill-creator`. This `trellis-meta` page only identifies where local Trellis skill, command, prompt, and workflow changes belong.
+For detailed skill authoring and review rules, use `cstl-skill-creator`. This `cstl-meta` page only identifies where local Trellis skill, command, prompt, and workflow changes belong.
 
 The frontmatter description should specify when to use the skill. Example:
 
@@ -45,11 +45,11 @@ Do not write vague descriptions such as "helpful project skill"; they can trigge
 Explicit entry points should state:
 
 - How the user triggers it.
-- Which `.trellis/` files to read.
+- Which `.cstl/` files to read.
 - Which scripts to run.
 - How to report after completion.
 
-If a command only repeats workflow rules, prefer making it reference/read `.trellis/workflow.md` instead of maintaining a second copy of the flow.
+If a command only repeats workflow rules, prefer making it reference/read `.cstl/workflow.md` instead of maintaining a second copy of the flow.
 
 ## Common Paths
 
@@ -74,4 +74,4 @@ For shared skill layers across tools, consider `.agents/skills/` on platforms th
 
 - Do not mix platform-specific syntax from removed adapters into the Cursor skill files.
 - Do not change only the dogfooded `.cursor/skills/` copy while forgetting to mirror the published template `packages/cli/src/templates/cursor/skills/` (and vice versa); see `cross-layer-thinking-guide.md.txt` → Cross-Package Template Consistency.
-- Do not hide long-term engineering conventions inside a command; write them to `.trellis/spec/`.
+- Do not hide long-term engineering conventions inside a command; write them to `.cstl/spec/`.

package/dist/templates/common/bundled-skills/{trellis-meta → cstl-meta}/references/customize-local/change-spec-structure.md

@@ -1,23 +1,23 @@
 # Change Local Spec Structure
 
-When the user wants to change the engineering conventions AI follows, add new spec layers, or adjust monorepo package mapping, edit `.trellis/spec/` and `.trellis/config.yaml`.
+When the user wants to change the engineering conventions AI follows, add new spec layers, or adjust monorepo package mapping, edit `.cstl/spec/` and `.cstl/config.yaml`.
 
 ## Read These Files First
 
-1. `.trellis/config.yaml`
-2. `.trellis/spec/`
-3. `.trellis/workflow.md` planning artifact guidance and Phase 3.3
-4. Selected task `implement.jsonl` / `check.jsonl`
+1. `.cstl/config.yaml`
+2. `.cstl/spec/`
+3. `.cstl/workflow.md` planning artifact guidance and Phase 3.3
+4. Selected task `implement.jsonl` / `check.jsonl`
 
 ## Common Needs
 
 | Need | Edit location |
 | --- | --- |
-| Add backend/frontend/docs/test spec layer | `.trellis/spec/<layer>/` or `.trellis/spec/<package>/<layer>/` |
-| Add shared thinking guides | `.trellis/spec/guides/` |
-| Adjust monorepo packages | `packages` in `.trellis/config.yaml` |
-| Change default package | `default_package` in `.trellis/config.yaml` |
-| Control spec scanning scope | `spec_scope` in `.trellis/config.yaml` |
+| Add backend/frontend/docs/test spec layer | `.cstl/spec/<layer>/` or `.cstl/spec/<package>/<layer>/` |
+| Add shared thinking guides | `.cstl/spec/guides/` |
+| Adjust monorepo packages | `packages` in `.cstl/config.yaml` |
+| Change default package | `default_package` in `.cstl/config.yaml` |
+| Control spec scanning scope | `spec_scope` in `.cstl/config.yaml` |
 | Make a task read a new spec | Task `implement.jsonl` / `check.jsonl` |
 
 ## Add A Spec Layer
@@ -25,7 +25,7 @@ When the user wants to change the engineering conventions AI follows, add new sp
 Single-repository example:
 
 ```text
-.trellis/spec/security/
+.cstl/spec/security/
 ├── index.md
 └── auth.md
 ```
@@ -33,7 +33,7 @@ Single-repository example:
 Monorepo example:
 
 ```text
-.trellis/spec/webapp/security/
+.cstl/spec/webapp/security/
 ├── index.md
 └── auth.md
 ```
@@ -47,16 +47,16 @@ Monorepo example:
 
 ## Update Context
 
-Adding a spec does not mean every task automatically reads it. The selected task must reference it in JSONL:
+Adding a spec does not mean every task automatically reads it. The selected task must reference it in JSONL:
 
 ```bash
-python3 ./.trellis/scripts/task.py add-context <task> implement ".trellis/spec/webapp/security/index.md" "Security conventions"
-python3 ./.trellis/scripts/task.py add-context <task> check ".trellis/spec/webapp/security/index.md" "Security review rules"
+python3 ./.cstl/scripts/task.py add-context <task> implement ".cstl/spec/webapp/security/index.md" "Security conventions"
+python3 ./.cstl/scripts/task.py add-context <task> check ".cstl/spec/webapp/security/index.md" "Security review rules"
 ```
 
 ## Change Monorepo Packages
 
-Example `.trellis/config.yaml`:
+Example `.cstl/config.yaml`:
 
 ```yaml
 packages:
@@ -70,7 +70,7 @@ default_package: webapp
 After editing, run:
 
 ```bash
-python3 ./.trellis/scripts/get_context.py --mode packages
+python3 ./.cstl/scripts/get_context.py --mode packages
 ```
 
 Use this output to confirm AI can see the correct packages and spec layers.