Skip to main content
Everyone prompts a little differently. A founder validating an idea has different goals than a developer scaffolding a client project. This page maps the six personas to prompting advice that fits how each one works, with a starter prompt you can adapt.
These tips build on Prompting Best Practices — be specific, describe the outcome, build one feature at a time. Here we tune that framework to your goals.

​
Non-Technical Founders

You have a product vision but not an engineering background. Your goal is to get from idea to a working prototype fast — for validation, for an investor demo, for iteration without a dev team. You tend to build: MVPs, investor demos, product validation prototypes. Prompting tips:
  • Describe the product and the user, never the code. “Users can do X” is exactly the right level of detail.
  • Lead with the one thing your app must prove. Strip everything that isn’t core to the first build.
  • Ask questions to scope the idea before you build — say you only want advice for now. Questions use credits, like any message.
State your goal in the prompt — “the goal is to validate ___.” It keeps the agent (and you) focused on the smallest thing worth building.

​
Indie Hackers & Bootstrappers

You ship fast and own your work. You want the boilerplate — auth, CRUD, dashboards — handled, so your time goes to what makes your product unique. You tend to build: SaaS products, side projects, revenue-generating apps. Prompting tips:
  • Ask for the standard scaffolding explicitly — authentication and a dashboard — so it’s in place from message one. Payments aren’t built in; see Payments before you add Stripe.
  • Then spend your follow-up prompts on your differentiator, the feature competitors don’t have.
  • Build in focused increments so you can deploy early and start getting users.
Name the next features at the end of your prompt (“I’ll add ___ next”). It signals scope for now without losing the roadmap.

​
Designers & Product Managers

You have wireframes, specs, and user flows. You want to turn them into something interactive — real working code, not another static mockup — without waiting on an engineering backlog. You tend to build: interactive prototypes, user-testing flows, design-to-code handoffs. Prompting tips:
  • Attach your wireframes or mockups. Fabricate accepts images and will use them as a layout reference.
  • Describe flows step by step — what the user sees, what they tap, what happens next.
  • Be precise about layout, spacing, and hierarchy. You know exactly how it should look; say so.
When the look matters as much as the flow, an attached image communicates more in one upload than a paragraph of description.

​
Professional Developers

You can read and write code. You use Fabricate to skip the boilerplate — scaffold a project quickly, generate the parts you’d rather not hand-write — then take the code where you need it. You tend to build: rapid prototypes, client projects, internal tools. Prompting tips:
  • Be precise with technical requirements — the data model, the relationships, the API behavior. The agent handles technical detail well.
  • Generate a solid scaffold first, then iterate on specifics; you can read the output and target follow-ups exactly.
  • Ask questions to sanity-check architecture decisions before building.
On a paid plan, you can export the generated code and continue in your own environment — see Push to GitHub. Changes you make there aren’t brought back into Fabricate.

​
Agency Teams

You deliver client projects and need consistent, well-architected output, fast. Quality and time-to-demo both matter, and the work has to fit your existing process. You tend to build: client sites, internal dashboards, rapid-delivery projects. Prompting tips:
  • Put the client brief into the prompt — audience, brand direction, required pages — so the first build already reflects the spec.
  • Be explicit about visual identity: colors, typography feel, and tone, ideally with a brand reference image attached.
  • Build to the brief, then iterate against client feedback in focused follow-ups for fast review cycles.
Capturing the brief precisely in the first prompt means your follow-ups are small, fast tweaks — ideal for client review rounds.

​
Students & Learners

You’re learning how real full-stack apps fit together. You want projects for your portfolio and a chance to learn by reading and modifying generated code. You tend to build: portfolio projects, learning exercises, hackathon apps. Prompting tips:
  • Pick a project scoped to learn one thing well — auth, working with a database, a CRUD flow — rather than something sprawling.
  • Ask questions about how things work: “How is authentication set up here?” or “What does this API route do?” Questions use credits, like any message.
  • After it builds, read the code, then make small changes and watch what happens. Modifying is how the concepts stick.
After your app builds, ask the agent to walk you through any file, and say you don’t want changes. It uses credits like any message, but it’s a patient way to learn what real full-stack code looks like.

​
Find Your Fit

Who is Fabricate For?

The full breakdown of all six personas.

Prompting Best Practices

The core framework behind every tip on this page.

Prompt Examples

Starter prompts grouped by app type.

Iterating on Your App

Refine your build with follow-ups, planning, and version history.