new-project
Scaffolds a fresh project from a workspace variant template (templates/<variant>) into a self-contained, platform-wired workspace. Use when: starting a new engagement or project from an existing co-* team, creating a tenant project, spinning up a workspace-standard project from a template. NOT for creating new variant templates (use create-variant) or converting external repositories (use adopt-project).
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- new-project
- owner
- scaffolding-expert
- scope
- common
- status
- active
- version
- 1.0.0
- metadata
- { "type": "process", "triggers": [ "new project", "create project", "scaffold project", "project from template", "start a new engagement" ] }
- relates_to
- [ { "type": "follows", "skill": "upgrade-project" }, { "type": "relates_to", "skill": "adopt-project" } ]
- description
- Scaffolds a fresh project from a workspace variant template (templates/<variant>) into a self-contained, platform-wired workspace. Use when: starting a new engagement or project from an existing co-* team, creating a tenant project, spinning up a workspace-standard project from a template. NOT for creating new variant templates (use create-variant) or converting external repositories (use adopt-project).
- l2_propagate
- false
- last_reviewed
- 1794096000000
03 SKILL.md 正文
Skill: new-project
When to Use
Use this skill to create a new project INSTANCE from an existing variant template
(templates/co-*) — for example, a new strategy-consulting engagement from co-consult,
or a new development workspace from co-develop.
Boundary (pick the right skill):
| Situation | Skill |
|---|---|
New project instance from an existing templates/<variant> |
this skill |
| Author a NEW variant template (domain does not exist yet) | create-variant |
| Convert an existing external repository into a workspace-standard project | adopt-project |
| Refresh an existing project to a newer template release | upgrade-project |
Prerequisites:
- Workspace root access (a clone of
ai_workspace);bunandgitinstalled - The target variant template exists and is
stable(templates/<variant>/variant.json→status)
Process
Step 1: Pick the variant
- [ ] List available variants:
ls templates/ | grep '^co-' - [ ] Confirm the variant fits the engagement (read
templates/<variant>/variant.json→description,agents,country_config) - [ ] Confirm
status: stable(non-stable variants require an interactive confirmation; avoid for tenants)
Step 2: Decide name, platform, and identity
- [ ] Project name: unique in
Projects/(bare name lands atProjects/<name>) - [ ] Platform profile:
claude|antigravity|codex|hermes|all, or a comma-separated list such asclaude,codex(hermesdelivers.hermes/skills/+ AGENTS.md only;alldelivers every platform surface; a list delivers the union of its profiles, e.g.claude,codex= CLAUDE.md + CODEX.md +.codex/) - [ ] Optional:
--description "<one sentence>"and--type web|cli|api|mcpfilldocs/project.mdidentity - [ ] Optional:
--country <CODE>when the variant declarescountry_configand the engagement is jurisdiction-specific
Step 3: Scaffold (non-interactive)
cd <workspace-root> && CI=true bun scripts/new-project.ts "<project-name>" \
--variant <co-variant> \
--platform hermes \
--description "<one sentence>" \
--type web \
--yes
Notes:
- The engine runs pre-flight gates (variant readiness, template validation) and rolls back partial directories on failure — fix the reported cause and re-run.
--version X.Y.Zpins the template snapshot to git tagtemplate-vX.Y.Z. Currently unavailable: the pinned path is defective on main (T-20260927-019) — omit the flag until it is fixed.
Step 4: Verify
- [ ] Project tree exists at
Projects/<project-name>withAGENTS.md,package.json,skills/, and the platform directory matching the profile (.hermes/skills/for hermes) - [ ] Smoke:
cd Projects/<project-name> && bun scripts/verify-scripts.ts --verify - [ ] Template provenance recorded:
.claude/template-version.txt+docs/<variant>.context.md
Step 5: Wire the runtime
- [ ] Hermes profile: trust the project so its skills load —
hermes skills trust <project-dir>(or add the dir toskills.trusted_project_dirs) - [ ] First session: open the platform CLI in the project directory; the PM agent is the entry point (AGENTS.md §3)
- [ ] Template upgrades later:
upgrade-projectskill (accepts relocated/absolute project paths)
References
- Engine:
scripts/new-project.ts(lifecycle record:docs/lifecycle/scripts/new-project.md) - E2E harness:
scripts/test-new-project.ts; pipeline smoke:simulate-pipelineskill (--mode project-creation) - Template releases:
templates/VERSION+template-v*tags (ADR-0089) - Sibling skills:
adopt-project,upgrade-project,create-variant
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.