菜单
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`.
用 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 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".
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".
| name | project-spine-workspace |
| description | 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`. |
Goal: prevent agents from inventing or invoking hosted workspace flows that are not routed in the public OSS CLI.
The public Project Spine CLI is OSS-first and local-first. Its routed commands are:
spine init
spine compile
spine inspect
spine export
spine template list|show|save
spine explain
spine drift check|diff
spine tokens pull
spine doctor
Hosted workspace commands are dormant in source but intentionally not exposed from spine --help. Do not instruct users to run:
spine loginspine logoutspine whoamispine workspace ...spine publish ...spine rationale ...spine drift check --pushspine template pullspine template list --workspaceFor team sharing today:
./.project-spine-templates/<name>/.spine template save --location user.AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, .cursor/rules/project-spine.mdc, and .project-spine/exports/* through normal version control.spine drift check --fail-on any in CI without --push.For client-facing summaries:
.project-spine/exports/rationale.md locally.Be explicit:
Hosted workspace code exists in the repository, but it is not part of the public CLI surface right now. The OSS launch is intentionally local-first. Use project-local templates and CI drift checks until a hosted workspace release is intentionally routed and documented.
Then continue with the local workflow that gets them closest to their goal.