Project Kit Local
Bootstrap a new repo with beads, uv, CLAUDE/AGENTS conventions, CI, and evolving kit tooling research.
Overview
project-kit-local is a plugin marketplace for the Build phase that scaffolds new projects with beads, uv, CLAUDE/AGENTS files, CI, and kit tooling research.
What is this marketplace?
- Single project-kit plugin scaffolds standard beads + uv + CLAUDE/AGENTS + CI layout
- Local marketplace project-kit-local by Rody Vilchez for repeatable new-repo setup
- Includes research flow for evaluating and folding new tooling into the kit
- Source rooted at ./ for bootstrapping and setup-evolution workflows
- 1 plugin: project-kit
- Marketplace name: project-kit-local
- Owner: Rody Vilchez
What problem does it solve?
Every new side project repeats the same boilerplate—agent docs, Python env with uv, task tracking, and CI—and drift accumulates across repos.
Who is it for?
Solo builders who maintain a personal project template and want Claude Code to generate and refine that kit on demand.
Skip if: Teams with an established org-wide template managed outside the agent, or pure app-marketplace distribution with no local marketplace workflow.
What do I get? / Deliverables
After registering the marketplace, you get a standardized scaffold and agent-assisted updates so new work starts on a known beads + uv + CI baseline.
- New repo tree with beads, uv, CLAUDE/AGENTS, and CI stubs
- Documented conventions copied from the project-kit template
- Research notes or kit updates when evaluating new toolchain pieces
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Greenfield project setup happens at the start of build when structure, dependencies, and agent instructions must exist before feature work. project-kit is scaffolding and standards (pm/devops hygiene), not feature frontend/backend implementation skills.
How it compares
Project bootstrap and kit-evolution marketplace, not a cloud deploy pack or payment SDK integration.
Common Questions / FAQ
Who is Project Kit Local for?
Developers using Claude Code who repeatedly start Python/agent-friendly repos and want beads, uv, CLAUDE/AGENTS, and CI applied consistently.
When should I use Project Kit Local?
Use it at the beginning of build when creating a new repository or when upgrading your standard kit after researching better tooling.
How do I add Project Kit Local to my agent?
Register the R0SEWT/project-kit local marketplace in Claude Code, install the project-kit plugin from ./, and run scaffold commands through the agent per your kit docs.