Each instruction defines a different visitor journey, route system, content model, interaction boundary, and standard of proof.
WEBSITE TYPE
Showing 10 prompts
03 / INSTRUCTION LIBRARY
Prompts that specify an actual website.
Every prompt defines a different information architecture, visitor path, content model, and set of boundaries.
PROMPT 01 / BUSINESS WEBSITE
Turn trust, services, and proof into qualified inquiries.
Create a complete professional website for [BUSINESS], serving [AUDIENCE] in [LOCATION]. The primary goal is [OBJECTIVE]. Build distinct Home, Services, About, Proof, FAQ, and Contact pages. Lead with the customer problem and concrete outcome, not a company biography. Give each service a useful explanation, who it is for, process, and next step. Use [PROOF] without inventing claims. Visual direction: [STYLE]. Tone: [TONE]. Include responsive navigation, accessible forms, local SEO structure, clear calls to action, useful empty and error states, metadata, and a launch checklist. Avoid generic AI copy, fake testimonials, and repetitive sections.
CHANGE: business, audience, services, location, proof, next stepUse this prompt ↗
PROMPT 02 / SAAS WEBSITE
Explain a product quickly and move qualified visitors toward a trial or demo.
Design a focused SaaS site for [PRODUCT], built for [USER]. The product solves [PROBLEM] through [WORKFLOW]. Create a homepage with a precise value proposition, product-in-use visual, outcome-led benefits, workflow, integrations, security or trust notes, FAQ, and [CTA]. Add Product, Solutions, Resources, and Contact routes. Show the interface through original product diagrams rather than decorative dashboards. Distinguish [DIFFERENTIATOR]. Use [STYLE] with [TONE]. Do not invent customer logos, metrics, pricing, or availability.
CHANGE: product, user, problem, workflow, differentiator, CTAUse this prompt ↗
PROMPT 03 / PORTFOLIO
Present work as evidence, not decoration.
Build an editorial portfolio for [NAME], a [DISCIPLINE] seeking [IDEAL CLIENT]. Make selected work the first-class content. Create Home, Work, individual Case Study, About, Services, and Contact routes. Each case study covers context, constraint, role, decisions, result, and reflection using supplied facts. Use [PROJECTS]. Create a restrained [STYLE] visual system. Voice: [VOICE]. Include filters, keyboard-friendly galleries, captions, and a clear inquiry path. Never fabricate outcomes or awards.
Help nearby customers understand, trust, and contact a provider.
Create a local service website for [BUSINESS], providing [SERVICE] across [AREA]. Optimize for fast mobile decisions. Build Home, Services, Service Area, About, FAQ, and Contact routes. Put phone, hours, response expectations, and [CONTACT METHOD] where customers need them. Explain pricing factors without inventing rates. Show [CREDENTIALS] only as provided. Add LocalBusiness schema-ready content, accessible forms, map placeholder, and location links. Style: [STYLE]. Avoid stock-photo clichés and false guarantees.
CHANGE: service, area, urgency, credentials, hours, contactUse this prompt ↗
PROMPT 05 / DIRECTORY
Make a collection browsable, comparable, and scalable.
Build a data-driven directory for [ITEMS]. Visitors compare by [ATTRIBUTES] and filter by [FILTERS]. Create a searchable index, category pages, [GEOGRAPHY] pages, detail profiles, methodology, and a labeled submission flow. Use one central data structure. Include empty, no-result, loading, and error states; accessible filters; shareable URLs; breadcrumbs; structured data; and editorial-versus-sponsored labels for [MONETIZATION]. Use [STYLE]. Do not invent listings or rankings.
CHANGE: items, attributes, filters, geography, submissions, monetizationUse this prompt ↗
PROMPT 06 / PUBLICATION
Build durable topic authority with a real editorial system.
Create an authoritative publication about [TOPIC] for [READER]. Organize around [PILLARS], not a chronological blog feed. Build Home, Topic Hub, Article, Author, About, Editorial Standards, Corrections, and Newsletter-coming-soon routes. Articles need a summary, contents, review dates, author details, sources, related reading, and disclosure for [REVENUE]. Use readable [STYLE] and [TONE]. Include Article and Breadcrumb schema-ready markup. Do not simulate a working signup.
CHANGE: topic, reader, pillars, authors, cadence, revenueUse this prompt ↗
PROMPT 07 / EVENT
Turn interest into attendance with clear logistics.
Create an event website for [EVENT] on [DATE] at [VENUE] for [AUDIENCE]. Build Home, Agenda, Speakers, Venue, FAQ, and Register routes. Answer what, who, when, where, and why in the first screen. Make the agenda scannable by day and track. Use [REGISTRATION] without simulating a transaction. Include travel, accessibility, policy placeholder, calendar links, and Event schema-ready data. Visual direction: [STYLE]. Do not invent speakers, sponsors, or availability.
CHANGE: event, date, venue, audience, agenda, registrationUse this prompt ↗
PROMPT 08 / COMMUNITY
Explain the shared purpose and make joining concrete.
Build a welcoming community site for [COMMUNITY], serving [MEMBERS]. Center [VALUE]. Create Home, About, Activities, Resources, Code of Conduct, and Join routes. Show [ACTIVITIES], explain [NORMS], and make [JOIN METHOD] the primary action. Include clearly labeled example-story placeholders, event patterns, moderation information, privacy notes, and a calm [STYLE] identity. Avoid vague belonging language and fake statistics.
CHANGE: community, members, value, norms, activities, joinUse this prompt ↗
PROMPT 09 / INTERNAL PORTAL
Give a team one dependable place to find and act on information.
Create an internal portal for [TEAM] that helps people [JOBS]. Build a task-first homepage with search, quick actions, updates, owned resources, and escalation paths. Add Resource Library, Playbooks, People, Updates, and Help routes. Every item needs an owner and [FRESHNESS] indicator. Design for [ACCESS MODEL], keyboard navigation, future roles, and useful empty states. Use [STYLE], compact but readable. Do not expose sensitive sample data or imply authentication that is not implemented.
CHANGE: team, jobs, resources, owners, freshness, accessUse this prompt ↗
PROMPT 10 / WEBSITE REDESIGN
Improve an existing site without losing what already works.
Redesign [URL] for [AUDIENCE]. Preserve and inventory content, routes, brand assets, SEO equity, and working functionality. Address [PROBLEMS] using [EVIDENCE] within [CONSTRAINTS]. Propose a revised information architecture, then implement the highest-value templates. Explain what changed and why. Maintain redirects, headings, metadata, analytics hooks, accessibility, and performance. Success means [SUCCESS]. Visual direction: [STYLE]. Do not invent research, silently delete content, or turn every page into the same landing page.
CHANGE: URL, audience, evidence, problems, constraints, successUse this prompt ↗