Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md1,557 B
docsSUMMARY.md336 B
History
First recorded snapshot · 0 installs
SKILL.md
New Project Setup
Overview
Initialize a new project across multiple repos and standardize documentation and ownership boundaries from day one.
Workflow
Gather inputs: project name, repo list, responsibilities, and any shared infra constraints.
Create the shared docs path ~/.project-docs/<project>/project_architecture.md.
Explicitly load and follow the project-architecture-doc skill to draft the architecture doc.
Symlink the shared project_architecture.md into each project repo.
Ensure the shared infra repo /path/to/your/terraform-repo is referenced in the doc but does not contain per-project docs.
Apply global guardrails:
- Use uv only for Python package management; do not use pip or uv pip. - Store secrets in GCP Secret Manager; manage via Terraform when possible. - Keep a single system of record per resource (avoid Terraform + app repos managing the same thing).
Notes
If the user asks only for the architecture doc, stop after completing that and do not perform additional repo setup.
If repo-specific standards are provided (frameworks, ownership rules, tooling), include them in the doc under the relevant repo section.