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-docskill to draft the architecture doc. - Symlink the shared
project_architecture.mdinto each project repo. - Ensure the shared infra repo
/path/to/your/terraform-repois referenced in the doc but does not contain per-project docs. - Apply global guardrails:
- Use
uvonly for Python package management; do not usepiporuv 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).
- Use
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.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.