vibe-coding
Skill72 starsChanged 45 days agoApache-2.0View on GitHub
Keep an agent disciplined while vibe coding: small shippable slices, verify before done, prefer lean skills over long prompts, and separate UI from API layers. Use this skill when scoping work, starting a vibe-coding session, or the agent is thrashing — for any stack. Not for Sarvam API signatures (use sarvam-mcp, translate, speech-to-text, text-to-speech, chat, or voice-agents).
16 other projects use a version of this.
Adopted by
Most recently taken up by
- xieqiyong/skillstheir own version, first seen Nov 8, 2026
- MUSE-CODE-SPACE/vibe-coding-mcptheir own version, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-Skillstheir own version, first seen Nov 1, 2026
- 200iqlabs/shared-skillstheir own version, first seen Oct 31, 2026
- I-Onlabs/claude-code-skillstheir own version, first seen Oct 25, 2026
- realjaymes/marketingagentskillstheir own version, first seen Oct 21, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- OfficeDev/microsoft-365-agents-toolkit★ 786same name
- realjaymes/marketingagentskills★ 68same name
- Exploration-labs/Nates-Substack-Skills★ 55same name
- 200iqlabs/shared-skills★ 4same name
- I-Onlabs/claude-code-skills★ 4same name
- OpenxIntelligence/Coding-Agent-Skills★ 4same name
- TabithaFanny/claude-skills-collection★ 4same name
- xieqiyong/skills★ 4same name
- HanksChen0110/skills★ 2same name
- adhi-jp/agent-skills★ 1same name
6 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 repository7 other files it gives its agents.
- chatSkill
- doc-aiSkill
- dubbingSkill
- sarvam-mcpSkill
- speech-to-textSkill
- text-to-speechSkill
- voice-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Verify: before you call it done: run tests, a script, a linter, or a reproduction the user can repeat.
- Distinctive: line 25
Iterate: Avoid giant diffs that mix auth, UI, and data in one go unless the user asked for that explicitly.
- Distinctive: line 29
Prefer a short domain skill (or a link to a canonical doc) over pasting the same long instructions every session.
- Distinctive: line 30
If the agent keeps guessing a library’s API, read the current docs (or a dedicated skill) instead of improvising from training data.
“Common” is measured: kept by at least 6 in 10 of the 13 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
Vibe coding
Vibe coding means you steer; the agent helps you ship. You do not need to master everything upfront—you need tight loops, honest checks, and the right small context at the right time. This applies to any project.
Habits
- Slice the smallest shippable change. One feature, one failure mode, one screen—whatever keeps the next step obvious.
- Implement with the right reference in view: a project skill, framework docs, or an official API page—not a wall of ad-hoc rules in the chat.
- Verify before you call it done: run tests, a script, a linter, or a reproduction the user can repeat. If nothing ran, say what should run.
- Iterate. Avoid giant diffs that mix auth, UI, and data in one go unless the user asked for that explicitly.
Skills vs. long prompts
- Prefer a short domain skill (or a link to a canonical doc) over pasting the same long instructions every session.
- If the agent keeps guessing a library’s API, read the current docs (or a dedicated skill) instead of improvising from training data.
Ecosystem: separate your layers
- App and UX (framework, components, a11y, design, routing): use skills or docs for that layer. Browsable examples include skills.sh and whatever your team ships.
- Data and APIs (databases, HTTP clients, model/speech/translation providers): use that product’s official reference or a provider-specific skill. Do not copy example HTTP calls from a UI skill into your real client without matching them to the real spec.
- Model, speech, translation, or vision features: treat them like any other API—vendor docs and provider skills win over generic chat guesses.
Gotchas
| Issue | What to do |
| Stale or invented APIs | Open the current project docs or provider documentation; do not trust memory alone. |
| One skill’s example bleeding into the wrong layer | A React skill’s fetch snippet is not automatically your model API—reconcile with the right spec. |
| Pasting a novel into every request | Shrink to a skill, a doc link, or a few bullets; refresh when the library changes. |
| “Big bang” refactors | Split, verify, repeat. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.