init-project
Skill4 starsChanged 4 months agoMITView on GitHub
Generate a complete pico-boot project using pico-initializer. Use when bootstrapping a new project with specific modules (fastapi, sqlalchemy, celery, pydantic, auth).
- Installs packages
53 other projects use a version of this.
Adopted by
Most recently taken up by
- morochena/skillstheir own version, first seen Nov 15, 2026
- kratocz/skillstheir own version, first seen Nov 15, 2026
- upamune/skillstheir own version, first seen Nov 15, 2026
- vlad-ryzhkov/ai-context-engineering-for-frontendtheir own version, first seen Nov 15, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 15, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 15, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 53
- southliu/south-admin-react★ 582same name
- wataru-maeda/react-native-boilerplate★ 521same name
- flonat/flonat-research★ 150same name
- huangwb8/skills★ 50same name
- jiahao-shao1/sjh-skills★ 43same name
- eugenelim/agent-ready-repo★ 31same name
- freemty/labmate★ 25same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- eranw2000/multi-phase-skills-framework★ 10same name
43 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- add-actuatorSkill
- add-appSkill
- add-authSkill
- add-celery-taskSkill
- add-componentSkill
- add-controllerSkill
- add-repositorySkill
- add-server-authSkill
- add-testsSkill
- add-validationSkill
- pico-conventionsSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
If no modules specified, default to fastapi
- Very specific: line 41
If auth is in modules, also set includeCompose: true and includeAuthServer: true
- Very specific: line 42
If user mentions "docker" or "compose", set includeDocker: true / includeCompose: true
- Very specific: line 43
If user mentions "example" or "crud", set includeExample: true (requires fastapi + sqlalchemy)
- Distinctive: line 108
Do NOT add submodules or pico packages to the modules list — it's redundant and may cause duplicate registration.
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generate Pico Project
Generate a project using pico-initializer: $ARGUMENTS
Also available as a web app: https://dperezcabrera.github.io/pico-initializer/
Steps
- Parse arguments — extract project name and optional modules from
$ARGUMENTS.- First word is the project name (e.g.
my-service) - Remaining words are modules:
fastapi,sqlalchemy,celery,pydantic,auth - If no modules specified, default to
fastapi
- First word is the project name (e.g.
- Locate pico-initializer — find the CLI:
git clone https://github.com/dperezcabrera/pico-initializer.git /tmp/pico-initializer INITIALIZER=/tmp/pico-initializer/cli.js Build config JSON from the parsed arguments:
{ "projectName": "<name>", "modules": ["fastapi", "sqlalchemy"], "includeTests": true, "includeDocker": false, "includeCompose": false, "includeAuthServer": false, "includeExample": false }Rules:
- If
authis in modules, also setincludeCompose: trueandincludeAuthServer: true - If user mentions "docker" or "compose", set
includeDocker: true/includeCompose: true - If user mentions "example" or "crud", set
includeExample: true(requires fastapi + sqlalchemy)
- If
- Run the generator:
node "$INITIALIZER" '<config-json>' # Or with explicit output dir: node "$INITIALIZER" --output-dir ./my-project '<config-json>' - Verify the generated structure:
python3 -m compileall -q <project-name>/
Generated project structure
Base files (always generated):
<project-name>/
├── <package>/
│ ├── __init__.py
│ ├── config.py # @configured AppSettings
│ ├── main.py # pico_boot.init(modules=["<package>"])
│ └── services.py # @component ExampleService
├── application.yaml # Config for all plugins
├── pyproject.toml # Dependencies and build config
├── requirements.txt
├── README.md
└── .gitignoreConditional files by module:
| Module | Files added |
fastapi | <package>/controllers.py — @controller with @get routes |
sqlalchemy | <package>/models.py — AppBase entity, <package>/repositories.py — @repository with @query |
celery | <package>/tasks.py — @component with @task methods |
pydantic | @validate decorator added to services.py (no extra file) |
auth | <package>/secure_controller.py — @requires_role + @allow_anonymous routes |
Optional extras:
| Option | Files added |
includeTests | tests/__init__.py, tests/conftest.py with container + TestClient fixtures |
includeDocker | Dockerfile |
includeCompose | docker-compose.yml with app service |
includeAuthServer | Adds pico-auth service to docker-compose.yml (port 8100, admin auto-created) |
includeExample | examples/products_api/ — full CRUD with models, schemas, repositories, services, controllers, database setup |
How pico-boot wiring works
The generated main.py uses a single root module:
container = init(modules=["myapp"], config=config)This is all that's needed because:
- Recursive scanning — pico-ioc scans
myappand all submodules, discovering every@component,@controller,@repository,@configuredclass. - Plugin auto-discovery — pico-boot loads all installed pico-* packages via
pico_boot.modulesentry points. No need to list them inmodules=[].
Do NOT add submodules or pico packages to the modules list — it's redundant and may cause duplicate registration.
Available modules
| Module | Value | Package | Description |
| FastAPI | fastapi | pico-fastapi | REST API with @controller and route decorators |
| SQLAlchemy | sqlalchemy | pico-sqlalchemy | Database ORM with @repository and @query |
| Celery | celery | pico-celery | Background tasks with @task |
| Pydantic | pydantic | pico-pydantic | Method-level validation with @validate |
| Auth | auth | pico-client-auth | JWT authentication with @requires_role |
Config JSON reference
| Field | Type | Default | Description |
projectName | string | required | Project and directory name |
packageName | string | derived | Python package name (auto-derived from projectName) |
pythonVersion | string | "3.12" | Python version for pyproject.toml |
modules | string[] | [] | Modules to include (see table above) |
includeTests | bool | true | Generate tests/ with conftest.py |
includeDocker | bool | false | Generate Dockerfile |
includeCompose | bool | false | Generate docker-compose.yml |
includeAuthServer | bool | false | Add pico-auth service to compose |
includeExample | bool | false | Add Products CRUD example (requires fastapi + sqlalchemy) |
CLI usage
# Minimal FastAPI project
node cli.js '{"projectName":"my-api","modules":["fastapi"]}'
# Full stack with auth + compose + example
node cli.js '{"projectName":"my-app","modules":["fastapi","sqlalchemy","pydantic","auth"],"includeCompose":true,"includeAuthServer":true,"includeExample":true}'
# Output to specific directory
node cli.js --output-dir ./workspace '{"projectName":"my-app","modules":["fastapi"]}'
# List registered generator tools
node cli.js --listAfter generation
cd <project-name>
python -m venv .venv && source .venv/bin/activate
pip install -e .
# FastAPI projects:
uvicorn <package>.main:app --reload
# With compose + auth:
docker compose upDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

