> ## Documentation Index > Fetch the complete documentation index at: https://fabricate.build/docs/llms.txt > Use this file to discover all available pages before exploring further. # Prompting by Persona > Tailored prompting tips for each kind of Fabricate user — from non-technical founders to professional developers — with an example prompt for each. 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](/introduction/who-its-for) to prompting advice that fits how each one works, with a starter prompt you can adapt. These tips build on [Prompting Best Practices](/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. * Use [Discuss Mode](/build/discuss-mode) freely — it's free, and it's like having a senior developer help you scope the idea before you build. ```text theme={null} Build an MVP for a meal-planning app for busy parents. Users sign up, answer a few questions about household size and dietary restrictions, and get a weekly meal plan of seven dinners. They can swap any meal for another suggestion. Show the week as a clean list of meals. The goal is to validate that people want auto-generated meal plans, so keep it to this core flow only. ``` 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, billing — 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, a dashboard, Stripe billing — so it's in place from message one. * 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. ```text theme={null} Build a SaaS app for freelancers to send and track invoices. Users sign up, then create an invoice with a client name, line items, and due date, and see all invoices in a table with status (draft, sent, paid). Include a dashboard with total outstanding and total paid this month. Use Stripe so clients can pay an invoice online. Get this core in place — I'll add recurring invoices and reminders next. ``` 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. ```text theme={null} Build an interactive prototype from the attached wireframes. It's an onboarding flow for a habit-tracking app: screen 1 welcomes the user, screen 2 asks them to pick up to three habits from a list, screen 3 asks what time of day they want reminders, and screen 4 shows their new habit dashboard. Match the layout and spacing in the wireframes. Generous whitespace, a calm pastel palette, one screen at a time with a progress indicator. ``` 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 in seconds, 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. * Use [Discuss Mode](/build/discuss-mode) to sanity-check architecture decisions before building. ```text theme={null} Scaffold a project-management tool. Data model: a Project has a name and description and many Tasks; a Task has a title, status (todo / doing / done), assignee, and due date. Build a projects list, a project detail page with a kanban board of its tasks grouped by status, and the ability to create and edit projects and tasks. Include email-and-password auth. I'll refine the board interactions after the scaffold is up. ``` You can export the generated code and continue in your own environment — see [GitHub Sync](/build/github-sync) to connect a repo. ## 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. ```text theme={null} Build a marketing site for a client — a boutique accounting firm called Ledgerline. Pages: home (hero, services overview, a short "why us" section, client logos, call-to-action), a services page, an about page with team bios, and a contact page with an inquiry form. Professional and trustworthy: a navy and warm-gold palette, classic serif headlines, plenty of whitespace. Use the attached brand colors. ``` 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. * Use [Discuss Mode](/build/discuss-mode) to ask how things work: "How is authentication set up here?" or "What does this API route do?" It's free and unlimited. * After it builds, read the code, then make small changes and watch what happens. Modifying is how the concepts stick. ```text theme={null} Build a portfolio project: a movie watchlist app. Users sign up and log in, add movies to their watchlist with a title, genre, and a personal rating out of five, and see their list with a filter by genre. Marking a movie as "watched" moves it to a separate watched section. Keep it clean and simple — I want to study how the auth and database pieces work. ``` After your app builds, switch to Discuss Mode and ask the agent to walk you through any file. It's a free, patient way to learn what real full-stack code looks like. ## Find Your Fit The full breakdown of all six personas. The core framework behind every tip on this page. Starter prompts grouped by app type. Refine your build with follow-ups, planning, and version history.