- Be specific early — one precise first prompt beats ten vague follow-ups.
- One change per turn; reverts beat patches; pin invariants you keep re-saying.
- Use Plan Mode before risky changes. Start a new chat when context goes stale.
Prompting
Prompt shapes that produce production-grade output on the first turn.
Iterating
Stay in flow across many turns without breaking what already works.
Plan Mode
Read-only reasoning pass before risky changes — flat 1 credit per turn.
Memory
Use project memory to pin facts that should never get lost.
Troubleshooting
The most common failure modes and how to recover quickly.
A short philosophy
Three principles run through every page in this section. Be specific early. A precise first prompt is worth ten vague follow-ups. Naming the user, the data, and a reference saves you turns later. Iterate in small turns. Each turn should change one thing. Five small turns beat one big bundled prompt; they’re easier to roll back, faster to land, and produce better code. Pin what matters. Anything you find yourself re-saying — your stack, your tone, a brand colour, an anti-pattern — should live in custom instructions (across all projects) or memory (one project). Repeating yourself is a smell.Where to start
- New to Vibely? Read Prompting first, then Iterating. Most “Vibely isn’t doing what I want” is a prompting issue.
- Got stuck on a turn? Troubleshooting covers the failure modes.
- Building something long-running? Memory explains what persists across compactions and what doesn’t.