smithery/day-in-the-country-llc

new-project-setup

Set up a new multi-repo project, including shared project documentation, repo boundaries, and initial architecture scaffolding.

Installation

$ npx skills add smithery/day-in-the-country-llc --skill new-project-setup

Summary

  • Set up a new multi-repo project, including shared project documentation, repo boundaries, and initial architecture scaffolding.
  • Use when creating a new project, adding repos to a project, or organizing ownership across repos.
  • Often requires creating a `project_architecture.md` and symlinking it into all repos.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/day-in-the-country-llc.

npx skills add smithery/day-in-the-country-llc

Browse all from smithery/day-in-the-country-llc

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,557 B
  • docs SUMMARY.md 336 B

History

  1. 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

  1. Gather inputs: project name, repo list, responsibilities, and any shared infra constraints.
  2. Create the shared docs path ~/.project-docs/<project>/project_architecture.md.
  3. Explicitly load and follow the project-architecture-doc skill to draft the architecture doc.
  4. Symlink the shared project_architecture.md into each project repo.
  5. Ensure the shared infra repo /path/to/your/terraform-repo is referenced in the doc but does not contain per-project docs.
  6. 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.