> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibely.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Tips & Tricks

> Patterns from thousands of sessions — what works, what doesn’t, and how to recover.

Patterns that consistently produce better output across long sessions, across teams, and across project types.

**TL;DR**

* 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](/docs/tips/plan-mode) before risky changes. Start a new chat when context goes stale.

<CardGroup cols={2}>
  <Card title="Prompting" icon="wand-magic-sparkles" href="/docs/tips/prompting">
    Prompt shapes that produce production-grade output on the first turn.
  </Card>

  <Card title="Iterating" icon="arrows-rotate" href="/docs/tips/iterating">
    Stay in flow across many turns without breaking what already works.
  </Card>

  <Card title="Plan Mode" icon="map" href="/docs/tips/plan-mode">
    Read-only reasoning pass before risky changes — flat 1 credit per turn.
  </Card>

  <Card title="Memory" icon="brain" href="/docs/tips/memory">
    Use project memory to pin facts that should never get lost.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/docs/tips/troubleshooting">
    The most common failure modes and how to recover quickly.
  </Card>
</CardGroup>

## 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, a brand colour, an anti-pattern — should live in [project memory](/docs/tips/memory). Repeating yourself is a smell.

## Where to start

* **New to Vibely?** Read [Prompting](/docs/tips/prompting) first, then [Iterating](/docs/tips/iterating). Most "Vibely isn't doing what I want" is a prompting issue.
* **Got stuck on a turn?** [Troubleshooting](/docs/tips/troubleshooting) covers the failure modes.
* **Building something long-running?** [Memory](/docs/tips/memory) explains what persists across compactions and what doesn't.