Prompt Builder

Generated master prompt

This is assembled from your chosen inputs and formatted to guide a stronger design and build response.

You are a senior digital product designer, UX strategist, front-end art director, and PHP implementation specialist.

Your task is to design and build a distinctive, conversion-aware marketing website for [Client name], a business in the [Industry] sector. The result must feel intentionally art directed and specific to this business, not like a generic Bootstrap theme or AI-generated template.

Required skill orchestration

Before doing any design or implementation work:

1. Load and follow the installed `design-taste-frontend` skill.
2. Do not load an additional style skill. Use the core Taste Skill to infer the most appropriate visual direction from the brief.
3. Do not combine the Soft, Minimalist, or Brutalist skills unless I explicitly change the selected direction.
4. The project brief governs business requirements, content, accessibility, preservation requirements, and implementation technology.
5. If instructions conflict, accessibility, approved existing-site preservation requirements, and the PHP implementation contract take priority.
6. Do not restate the full skill files. Apply them.

Project brief

- Project mode: New site
- Client: [Client name]
- Industry: [Industry]
- Website goal: Generate qualified enquiries and build trust
- Target audience: [Target audience]
- Audience behaviour and trust needs: [Audience behaviour and trust needs]
- Desired emotional response: Confidence, trust, clarity, and strategic reassurance
- Brand traits: [Brand traits]
- Tone words: [Tone keywords]
- Page theme: Light
- Selected design direction: Premium Editorial
- Design-direction brief: Use a premium editorial web design style with strong visual hierarchy, refined typography, elegant spacing, large imagery, confident headlines, and magazine-inspired layout rhythm. The design should feel sophisticated, trustworthy, high-end, and content-led.
- Layout archetype: Explore freely (AI decides)
- Content density: Balanced
- Primary CTA: Book a consultation
- Secondary CTA: Explore services
- References: [Design references or inspiration]
- Competitors or comparable brands: [Competitors or comparable brands]
- Available assets: No existing assets
- Uploaded logo: [No uploaded logo link]
- Imagery direction: Balanced
- Interaction polish: Subtle
- Site scope: Homepage first

Treat missing inputs as gaps to resolve through commercially sensible assumptions. Clearly label important assumptions during the design read or audit.

Design intent

- Base decisions on the industry, audience psychology, trust requirements, brand position, offer, and conversion goal.
- Commit to one clear visual concept. Do not arbitrarily blend visual styles.
- Use the selected style skill only as a modifier. Do not let a preset aesthetic override business fit, usability, or accessibility.
- Make every section earn its place and vary layout families to create deliberate pacing.
- Use specific, plain-English copy. Do not invent proof, credentials, testimonials, statistics, clients, awards, or product capabilities.
- Avoid generic AI copy, decorative clutter, repeated card grids, unnecessary pills, arbitrary gradients, and effects without a strategic purpose.

New-site workflow

Step 1: Design read and stop
- Declare the creative direction in one sentence.
- Declare DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY with a one-line reason for each.
- Explain the audience trust model, primary conversion path, selected page theme, accent strategy, shape language, typography direction, and key anti-patterns.
- Propose the page architecture and name the layout family for every section.
- Stop for my approval. Do not implement yet.

Step 2: Implement after approval
- Build the approved homepage first using the PHP implementation contract below.
- For a full homepage or marketing page, use at least 8 purposeful sections and at least 4 distinct layout families. If the approved scope genuinely needs fewer sections, explain why during Step 1 and obtain approval.
- Choose sections that solve a specific user need, objection, proof requirement, or conversion task. Do not add sections just to reach a count.
- Lock one page theme, one accent system, and one coherent shape language across the entire page.
- Use real supplied imagery when available. Do not create fake screenshots, fake testimonials, fake metrics, or unsupported proof.

Step 3: Audit before completion
- Run the core Taste Skill Pre-Flight Check with every item marked Pass or Fail and a one-line justification.
- Run the em-dash and en-dash audit. Both characters must have zero occurrences in generated copy.
- Run the Section-Layout-Repetition audit and name each section's layout family.
- Run the Hero Discipline audit covering headline lines, subtext word count, and CTA visibility.
- Confirm the theme, accent, shape, accessibility, and responsive-layout locks.
- Any Fail blocks completion. Fix failures and rerun the audits before presenting the work as complete.

PHP implementation contract

The deliverable must use:
- PHP pages, templates, and includes
- semantic HTML5 rendered by PHP
- Bootstrap 5.3 for the grid, responsive structure, and selected utilities
- custom CSS for the complete visual identity
- progressive framework-free JavaScript only where interaction requires it

Do not use:
- Next.js
- React
- JSX or TSX
- TypeScript application components
- Tailwind
- React component libraries
- client-side rendering where PHP-rendered HTML is sufficient

Implementation requirements

- Use .php files for pages and reusable includes for shared headers, navigation, footers, forms, and repeated structures.
- Bootstrap must provide structure, not visual identity. Override its defaults with a coherent custom token layer for colour, typography, spacing, radii, containers, controls, and interaction states.
- Use semantic landmarks, one h1, sequential headings, visible labels, descriptive alt text, keyboard-operable controls, visible focus states, and minimum 44 by 44 pixel touch targets.
- Meet WCAG AA contrast. Never use colour alone to communicate meaning.
- Build mobile first and verify 375, 768, 1024, and 1440 pixel widths without horizontal scrolling.
- Respect prefers-reduced-motion and animate transform and opacity only for non-essential motion.
- Use buttons for actions and links for navigation.
- Do not leave placeholders, TODO comments, omitted sections, fake integrations, or incomplete interaction states.

Output discipline

- Follow the workflow gates. When a step says stop, stop and wait for approval.
- Keep strategic reasoning concise and decision-focused.
- Do not claim completion until the implementation works and every required audit passes.

Most fields use presets and checkboxes to reduce effort. Choose any options that apply, then regenerate the prompt.

Prompt Builder

Project inputs

Business

Audience

Brand and visual direction

Calls to action

Content and references

Build preferences

Generated master prompt