| name | vibe-repo-init |
| description | >- |
Vibe repo init (Cursor)
Role: Turn a blank (or near-blank) folder into a Cursor vibe-coding basement — runnable skeleton + Cursor project files (AGENTS.md, .cursor/rules/, .cursor/skills/) — for MCU, Linux PC, online server, HTML UI, PC UI, or hybrid mixes.
IDE assumption: Cursor (Agent, project rules, project skills, user-pack skills). Do not scaffold VS Code–only or JetBrains layouts unless the user asks.
Not this skill: full product features, SysML modeling (use SysML hubs), or deep requirements interviews (use project-planner after basement exists).
Execution contract
- Follow
pipeline_steps in order; do not write files before step 4 OK (unless user waived).
- Confirm scope before scaffold (workflow §1): do not assume or copy unless user said mirror X.
- Always apply references/cursor-basement.md on scaffold —
.cursor/skills/ is mandatory.
- Seed
.cursor/skills/repo-context/ from assets/repo-context-skill-stub.md unless the user names a different first project skill.
- One primary type playbook; hybrid adds secondary slices without duplicating shared root.
- After scaffold: one clear "next vibe step" in Cursor (build/flash/run/open UI).
Type codes
| Code | Meaning |
|---|
mcu | Bare-metal / RTOS firmware (Pico, STM32, …) |
linux-pc | Native Linux/desktop CLI or daemon |
online-server | Hosted API/worker (VPS, PaaS, container) |
html-ui | Browser UI (static or light web app) |
pc-ui | Desktop GUI (native toolkit / Tauri / Electron-class) |
hybrid | Two or more of the above (ordered) |
Full taxonomy: references/repo-types.md.
Delegated skills
Resources
Pairing
User-pack skills: ~/.cursor/skills/. Project skills: .cursor/skills/ (required in every scaffold). Route via SKILL-GRAPH.md / repo AGENTS.md. Memory: memnet-goldfish-loop.mdc.