菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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. |
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..claude/, .codex/, .cursor/, .opencode/, .kiro/, .gemini/,
.qoder/, .codebuddy/, .github/, .factory/, .pi/, .kilocode/, .agent/, .windsurf/,
and similar directories..agents/skills/.Do not assume the user has the Trellis source repository. Do not default to modifying the global npm
install directory or node_modules.
references/local-architecture/overview.md first to establish the local Trellis system
model.references/platform-files/platform-map.md and
the relevant platform file notes.references/customize-local/overview.md, then open
the specific customization topic.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, active 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.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.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..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..trellis/.template-hashes.json and .trellis/.runtime/ are management/runtime state files.
Confirm necessity before editing them.node_modules/@mindfoldhq/trellis to implement
project needs.trellis-meta; put project rules in
.trellis/spec/ or a project-local skill.Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.