菜单
Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain into a more specific active skill.
Use when the user asks about Project Spine hosted workspaces, team sync, shared workspace templates, invites, or commands such as `spine login`, `spine workspace`, `spine publish`, or `spine drift check --push`.
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs `spine init` → edits brief → `spine compile` → reviews outputs. For stale files use project-spine-drift.
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs `spine drift check`, interprets each drift category, and guides resolution. For initial setup use project-spine-kickoff.
Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer".
| name | project-spine-template |
| description | Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter". |
Goal: reuse a team's agreed-upon project structure (brief scaffold + design rules + compile-time contributions) across client projects.
Project Spine resolves templates from these roots (highest priority first):
./.project-spine-templates/<name>/ committed to the current repo.~/.project-spine/templates/<name>/ on this machine.saas-marketing, app-dashboard, design-system, docs-portal, api-service, and monorepo ship with the CLI.Same name in a higher tier overrides lower tiers.
spine template list
Shows all templates reachable from this shell. The [source] column tells the user where each one comes from.
spine init --template <name>
Scaffolds brief.md from the template's starter content. Then follow project-spine-kickoff from Step 3.
Prerequisite: the user already has a brief.md and ran spine compile at least once. The compiled .project-spine/spine.json is used to derive the template's contributes block automatically.
spine template save \
--name my-agency-saas \
--title "My agency SaaS starter" \
--description "Our marketing site template (Acme Inc.)" \
--location user
--location options:
user (default) — saves to ~/.project-spine/templates/<name>/; follows you across projects on this machine.project — saves to ./.project-spine-templates/<name>/; commits to the repo, shared via VCS.Save project-local if:
Save user-local if:
contributes block derives from spine.json; without it the template is just a brief scaffold with empty rules.my-template, template1). spine template save requires lowercase-kebab names; pick something meaningful (my-agency-saas, client-admin-dashboard).If they ask for hosted workspace sync, switch to project-spine-workspace so the agent explains that workspace commands are dormant in the public OSS CLI. If they want to share the template's output (rationale) with a client → switch to project-spine-rationale for local review.