zl-q
04b493ed09
- Remove legacy .opencode/ directory and configuration - Update .trellis/ to v0.5.0-rc.6 structure - Refactor scripts: modularize common/, remove multi_agent/ - Add new common modules: git.py, io.py, log.py, types.py, etc. - Update workflow.md and AGENTS.md - Archive completed migration tasks
2.6 KiB
Change Local Skills, Commands, Prompts, And Workflows
When the user wants to change AI entry points, auto-trigger rules, or explicit command behavior, edit skills, commands, prompts, or workflows in local platform directories.
Read These Files First
.trellis/workflow.md- Target platform skill/command/prompt/workflow directory
- Related agent or hook files
- Whether project rules already exist in
.trellis/spec/
Which Entry Type To Choose
| Goal | Recommendation |
|---|---|
| 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. |
Modify A Skill
A skill is usually:
<skill-name>/
├── SKILL.md
└── references/
SKILL.md should be short and responsible for triggering/routing. Put long content in references/ so AI can read it on demand.
The frontmatter description should specify when to use the skill. Example:
description: "Use when customizing this project's deployment workflow and release checklist."
Do not write vague descriptions such as "helpful project skill"; they can trigger incorrectly.
Modify A Command/Prompt/Workflow
Explicit entry points should state:
- How the user triggers it.
- Which
.trellis/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.
Common Paths
| Platform | Entry directories |
|---|---|
| Claude Code | .claude/skills/, .claude/commands/ |
| Cursor | .cursor/skills/, .cursor/commands/ |
| OpenCode | .opencode/skills/, .opencode/commands/ |
| Codex | .agents/skills/, .codex/skills/ |
| GitHub Copilot | .github/skills/, .github/prompts/ |
| Kilo / Antigravity / Windsurf | workflows + skills |
Add A Project-Local Skill
If the user wants to document team-private customizations, create a project-local skill, for example:
.claude/skills/project-trellis-local/
└── SKILL.md
For multi-platform projects, add equivalent versions in each platform skill directory, or use .agents/skills/ on platforms that support the shared layer.
Notes
- Do not mix every platform's syntax into one file.
- Do not change only one platform entry point while claiming all platforms are supported.
- Do not hide long-term engineering conventions inside a command; write them to
.trellis/spec/.