| name | vibe-coding |
| description | 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). |
| license | Apache-2.0 |
| metadata | {"author":"sarvam-ai","version":"2.1"} |
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 (or a link to a canonical doc) over pasting the same long instructions every session.
