project-bootstrap
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: project-bootstrap
description: Initialize a brand-new project from scratch with a default full-stack scaffold (Rust core + Reac…
category: devops
runtime: Docker
---
# project-bootstrap output preview
## PART A: Task fit
- Use case: Initialize a brand-new project from scratch with a default full-stack scaffold (Rust core + React Router 7 portal + Docker + Kubernetes). Use when a developer asks to bootstrap an empty repo or start a new project and no specific tech stack is requested. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Quick Start / Workflow / What Gets Generated” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Initialize a brand-new project from scratch with a default full-stack scaffold (Rust core + React Router 7 portal + Docker + Kubernetes). Use when a developer asks to bootstrap an empty repo or start a new project and no specific tech stack is requested. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Quick Start / Workflow / What Gets Generated” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/path`, `/health`, `/ready`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Quick Start / Workflow / What Gets Generated”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: project-bootstrap
description: Initialize a brand-new project from scratch with a default full-stack scaffold (Rust core + Reac…
category: devops
source: tomevault-io/skills-registry
---
# project-bootstrap
## When to use
- Initialize a brand-new project from scratch with a default full-stack scaffold (Rust core + React Router 7 portal + Do…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Quick Start / Workflow / What Gets Generated” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "project-bootstrap" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Quick Start / Workflow / What Gets Generated
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Project Bootstrap
Create a ready-to-run project skeleton with core, portal, docker, and k8s resources. Default stack matches Auth9 (Rust + React Router 7 + TypeScript + Vite).
Quick Start
- Choose a project name and target directory.
- Run the initializer script.
.claude/skills/project-bootstrap/scripts/init_project.py \
--name acme \
--root /path/to/acmeOptional overrides:
.claude/skills/project-bootstrap/scripts/init_project.py \
--name acme \
--root /path/to/acme \
--core-port 8080 \
--portal-port 3000 \
--namespace acmeWorkflow
- Confirm requested stack. If no explicit preference, use default stack.
- Run the initializer script with required parameters.
- Verify local run instructions:
- Core:
cd core && cargo run - Portal:
cd portal && npm install && npm run dev - Docker:
cd docker && docker-compose up -d
- Core:
- Hand off the generated skeleton and next steps.
What Gets Generated
core/Rust service with/healthand/readyportal/React Router 7 + Vite + TypeScript appdocker/Dockerfiles anddocker-compose.ymlk8s/Base manifests for core and portalscripts/Local reset scriptdeploy/K8s deploy/upgrade/cleanup scripts
Script Templates
scripts/reset-docker.sh– reset local Docker environmentdeploy/deploy.sh– apply k8s base manifestsdeploy/upgrade.sh– restart k8s deploymentsdeploy/cleanup.sh– cleanup k8s namespace
Each script supports optional Auth9 extras via ENABLE_AUTH9_EXTRAS=true.
Templates
Templates live in:
assets/template/Use placeholders:
{{project_name}}{{core_port}}{{portal_port}}{{namespace}}
References
references/stack.mdfor optional extensions (Keycloak/DB/Redis/etc.)
Source: c9r-io/auth9 — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review