Vibe bootstrap
Skill roronoazoroshao369/vibe-coding-os/skills/core/vibe-bootstrap
Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description
npx -y skills add roronoazoroshao369/vibe-coding-os --skill vibe-bootstrapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 208 tokens by cl100k_base, as published. Nobody here has run it
Vibe Bootstrap
Purpose
Start a new Vibe Coding OS session with the right context, workflow, and safety rails.
When to use
Use at the beginning of a repo session, after a long pause, or when the assistant lacks context.
Inputs
User goal, repository state, available instructions, known constraints.
Workflow
- Read top-level instructions and registries.
- Summarize the current objective and repo state.
- Identify the smallest safe next workflow phase.
- List assumptions and open questions.
- Select relevant skills or commands.
Outputs
A brief session brief, selected workflow phase, assumptions, and next action.
Failure modes
- Skipping repository inspection.
- Choosing too many skills for a simple task.
- Treating stale context as current truth.
Verification checklist
- Repository instructions were read.
- Goal and next step are explicit.
- Assumptions are visible.
- No secrets or unrelated context were captured.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most project setup skills give in 208 tokens
Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07
- Ask one question at a timein 29 of 999, across 28 files
- Detect the package manager from lockfilesin 28 of 999, across 9 files
- Present findings to the userin 26 of 999, across 5 files
- Explore current repo statein 24 of 999, across 3 files
- Update the agent skills block in place if it existsin 24 of 999, across 3 files
- Install husky lint-staged and prettierin 23 of 999, across 4 files
- Create the lintstagedrc filein 22 of 999, across 3 files
- Commit all changed filesin 22 of 999, across 3 files
- Run lint-staged to verify it worksin 22 of 999, across 3 files
- Create the husky pre-commit filein 21 of 999, across 2 files
- Create a prettierrc file if missingin 21 of 999, across 2 files
- Initialize huskyin 21 of 999, across 2 files
Said here and by no other author read
- read top-level instructions and registries
- summarize the current objective and repository state
- identify the smallest safe next workflow phase
- list assumptions and open questions
- select relevant skills or commands
- produce a brief session brief
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.