Prompting best practices

This playbook brings together the most effective techniques, strategies, and principles for getting the best possible results with Cenate.

Make Cenate ask clarifying questions

One of the most effective ways to get better results from Cenate is to let it fill in the gaps before writing code. If something depends on user goals, tone, or workflow details, ask for a short round of clarification first.

Cenate will respond with focused follow-up questions. This helps clarify requirements up front and prevents misunderstanding or wasted effort later.

Phase 1: Lay the foundation

1. Plan before you prompt

Before using Cenate, define what you're building. Use a quick planning session to answer: what is this product, who is it for, why will they use it, and what is the one key action they should take?

2. Map the user journey visually

Think in transitions: what does the user see first, what builds trust, what gives them confidence to act, and where does that action lead?

3. Get the design right first

Choose a direction early. Cenate needs to know the look and feel you want up front: calm and elegant, bold and disruptive, or premium and sleek.

Phase 2: Think in systems

4. Prompt by component, not page

Cenate works best when you build your UI in modular parts, not full pages at once. Each block should have one clear purpose and structure.

5. Design with real content

Cenate does not work well with placeholder content. Use copy that reflects your real message as early as possible.

6. Speak atomic: buttons, cards, modals

Think like a system. Describe cards, badges, toggles, chips, form fields, and modals directly instead of vague requests for a generic interface.

7. Use buzzwords to dial in aesthetic

Terms like minimal, expressive, cinematic, playful, premium, and developer-focused help Cenate understand tone, spacing, border radius, and typography direction.

Phase 3: Build with precision

8. Use prompt patterns for layouts

Prompts are easier to write and more effective when you use repeatable patterns rather than describing everything from scratch every time.

9. Add visuals via URL

If you want a layout to feel grounded, point Cenate to real screenshots, media, or image URLs and specify where they should be placed.

10. Layer context with the Edit button

Use targeted edits instead of rewriting whole prompts. This keeps your project modular and reduces the risk of losing working parts.

Phase 4: Iterate and ship

11. Build with Cenate Cloud in mind

When designing a layout, think about how it will actually work: auth logic, dynamic content, and state handling.

12. Version control is your friend

Cenate autosaves, but that does not replace intentional iteration. Make one meaningful change at a time and review before moving forward.