vibe-coding
/vibe-coding
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).
- Author
- sarvamai ↗
- Repository
- skills ↗
- Licence
- Apache-2.0
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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).
Original author 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).
How it works
- Habits
- Skills vs. long prompts
- Ecosystem: separate your layers
- Gotchas
SKILL.md preview
--- 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 1. **Slice** the smallest shippable change. One feature, one failure mode, one screen—whatever keeps the next step obvious. 2. **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. 3. **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. 4. **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](https://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. |
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sarvamai/skills | 100 | Apache-2.0 |
| TerminalSkills/skills | 100 | Apache-2.0 |
| jamditis/claude-skills-journalism | 100 | MIT |
| dtyq/magic | 100 | Apache-2.0 |
| realjaymes/marketingagentskills | 100 | MIT |
| LeadMagic/gtm-skills | 100 | MIT |
| x-school-academy/skill-pilot | 100 | MIT |
| shareai-lab/kode-cli | 95 | Apache-2.0 |
| andreibesleaga/gabbe | 90 | CC-BY-4.0 |
Database snapshot: 13.11.2026 · package version 229c143ca6a4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95text-translation
Write correct Sarvam text translation code (sarvam-translate:v1, mayura:v1) — mode/script/numeral options and silent parameter failures. Use this skill when building text translation or localization features in Python or JS/TS. For whole-document (PDF, Word, Excel) translation,… - 100sarvam-mcp
Run Indic speech and language tasks through the Sarvam MCP server: translate text, transcribe or dub audio, TTS, localize i18n files, LLM complete, vision extract, or fetch Sarvam API docs/snippets while coding. Use this skill when the user wants Sarvam to act in chat, when… - 100vibe-delegate
Delegate a coding task to the Mistral Vibe CLI (`vibe`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Vibe — phrasings like "have Vibe implement X", "delegate this to Vibe", "run it through… - 100karpathy-vibe-to-agentic
Transition from vibe coding (fast prototyping) to agentic engineering (rigorous iteration). Use this skill when the user has a rough prototype and wants to level it up, needs to go from "it kind of works" to production-quality, wants to understand the difference between vibe… - 100vibe
Use when working in a vibe-coded repository, where the user never reads the code and only runs the product and gives feedback, or when the user wants to start building a project that way. - 100de-vibe
Audit and fix the tells that software was vibe-coded / AI-generated, then give it a small distinctive identity, so it ships looking handcrafted and professional. Use whenever the user says "de-vibe", "does this look AI-generated / vibe coded?", "make this look shippable /…