Skip to main content
Custom instructions are the single most useful customization in Vibely. Anything you’d otherwise paste into every prompt — your stack, your conventions, your name, your tone — lives here once and is injected into every conversation automatically. If you set nothing else from this section, set this.

​
Two layers

Vibely separates “who you are as a builder” from “who the agent is to you.” Both compose; both ship to the model on every turn.
LayerWhat it isMax length
Custom instructionsFacts and preferences about you and how you like the agent to work.4000 chars
Customize VibelyThe agent’s persona, intro line, personality tags, extra info.~2000 chars
Both live under Settings → Customize Vibely. Both are optional.

​
Custom instructions — write them like a colleague handover

The agent reads this on every turn, in every project, forever. Treat it like the handover note you’d give a new contractor on day one:
  • What you’re building (one line)
  • The stack you prefer when it’s not specified
  • Anti-preferences (don’t suggest X, don’t use Y)
  • How verbose you want explanations
  • Your name and what to call you
A good one is short. Three to five lines is plenty. Walls of text dilute the signal.

​
Example that works

I build B2B SaaS in TypeScript. Default to Next.js App Router unless I say otherwise.
Use Drizzle, not Prisma. Use shadcn/ui for components.
Skip the recap at the end of responses — I read the diff.
Call me Nishant.

​
Example that doesn’t

Please be helpful and respond clearly. I like good code. Make sure everything works
and follows best practices. Use modern frameworks. Don't break things.
The second one is true of every user; it adds nothing the agent didn’t already assume.

​
What to put in (and what not to)

Put in:
  • Stack preferences when “default to X” actually changes behaviour
  • Anti-patterns you’ve been bitten by (“don’t use useEffect to derive state”)
  • Conventions specific to your projects (“commit messages in conventional commits format”)
  • Personal context only relevant to how the agent talks (“I’m dyslexic, prefer code blocks over prose”)
Leave out:
  • Generic best-practice (“write clean code”) — the model already tries to
  • Per-project file paths or function names — those belong in project memory, not your account
  • Secrets or anything you don’t want shipped to every model provider on every turn

​
Customize Vibely — the agent’s persona

This is the smaller sister panel. It changes how the agent introduces itself and speaks, not what it knows about you.
  • Intro line — what the agent opens new chats with. Defaults to a friendly Vibely line; replace with something terser if you want.
  • Personality tags — pick from a chip list (e.g. “concise”, “playful”, “technical”). The agent tries to match the picked vibe.
  • Additional info — a small free-form field the agent reads as system context. Use it for anything that doesn’t fit the tags.
  • Enable for new chats — when off, the persona only applies to chats where you explicitly turn it on. Default is on.
For most people, custom instructions do the heavy lifting and Customize Vibely is left alone.

​
How it reaches the model

Both layers are merged into a memory block that prepends every turn — same priority as the system prompt. The agent sees them before it sees your message. This means:
  • Conflicts resolve in your favour. If you said “don’t use Tailwind” and the prompt asks “build a Tailwind page”, the agent will surface the conflict instead of silently picking one.
  • The block is not model-visible across providers — it lives on Vibely’s backend and is injected per turn.
  • Editing instructions takes effect on the next turn, not retroactively to the conversation so far.

​
When to update

Every time you catch yourself typing the same correction twice (“don’t write summaries”, “use Bun not npm”, “Hindi for casual chat please”) — that’s a custom instruction. The whole point is that the second time should be unnecessary. Once a quarter, re-read what’s in the field. Stale instructions (“we’re migrating to React 18” — you migrated last year) drag down quality more than they help.