v1.2-prompt-builder

SiteFactory Prompt Builder

Turn a module, miniapp, dashboard, interface or website idea into a structured build prompt for any AI agent.

How to use

This workspace is static for now. Fill the structure mentally or in another document, then copy the prompt to any coding agent.

  • choose what you want to build
  • fill in the project details
  • copy the generated prompt structure manually
  • give it to the coding agent
  • let the project files remain the source of truth

Prompt input structure

Use these fields as cards when turning a module, miniapp, dashboard, interface or website idea into a build prompt.

PROJECT_NAME

Use lowercase kebab-case for folders.

PROJECT_TYPE

Module, component, miniapp, template, project, preview or workspace.

SOURCE_TEMPLATE

The reusable template to start from.

PROJECT_PURPOSE

What the build should prove, support or communicate.

PROJECT_TONE

The voice and feel of the result.

PROJECT_SECTIONS

The required sections, panels, cards or views.

FUNCTIONALITY

Actions, state, persistence, integrations and interactions.

DESIGN_DIRECTION

Visual constraints and layout expectations.

CONSTRAINTS

What not to add and what must be preserved.

OUTPUT_STRUCTURE

Required source files, preview copy and documentation updates.

BUILD_CHECK

The validation command and expected result.

Copy-friendly prompt template

Replace the placeholders before giving this to an AI agent.

Create a new SiteFactory build.

PROJECT_NAME:
PROJECT_NAME

PROJECT_TYPE:
PROJECT_TYPE

SOURCE_TEMPLATE:
SOURCE_TEMPLATE

PROJECT_PURPOSE:
PROJECT_PURPOSE

PROJECT_TONE:
PROJECT_TONE

PROJECT_SECTIONS:
PROJECT_SECTIONS

FUNCTIONALITY:
FUNCTIONALITY

DESIGN_DIRECTION:
DESIGN_DIRECTION

CONSTRAINTS:
CONSTRAINTS

OUTPUT_STRUCTURE:
OUTPUT_STRUCTURE

BUILD_CHECK:
BUILD_CHECK

Before changing anything:
- read README.md
- read AGENTS.md
- read NAMING.md
- read PROJECT_STATE.md
- read projects/sitefactory-test/public/docs/create-project-flow.html
- inspect the current project structure
- check git status

Rules:
- preserve portability
- keep Astro only as the development and preview shell
- create canonical project source
- create browser-accessible preview copy
- update registry
- run build
- summarize changes
- do not deploy manually
- do not add dependencies unless explicitly required

Example prompts

Examples for reusable modules, miniapps and one website-style use case.

PROJECT_NAME:
task-board

PROJECT_TYPE:
app module

PROJECT_PURPOSE:
A portable task board module for organizing task cards by status.

FUNCTIONALITY:
- create task
- move task between statuses
- edit task label
- keep markup portable

PROJECT_NAME:
upload-manager

PROJECT_TYPE:
miniapp

PROJECT_PURPOSE:
A reusable upload manager interface with empty, selected, uploading and complete states.

FUNCTIONALITY:
- choose files
- show selected files
- show upload status
- no backend yet

PROJECT_NAME:
review-panel

PROJECT_TYPE:
interface component

PROJECT_PURPOSE:
A reusable panel for reviewing quality, risks, decisions and next actions.

PROJECT_NAME:
settings-panel

PROJECT_TYPE:
interface module

PROJECT_PURPOSE:
A portable settings panel with grouped fields, toggles and action buttons.

PROJECT_NAME:
dashboard

PROJECT_TYPE:
interface workspace

PROJECT_PURPOSE:
A reusable dashboard shell for status cards, activity panels and next actions.

PROJECT_NAME:
miniapp

PROJECT_TYPE:
miniapp template

PROJECT_PURPOSE:
A portable starter for a small functional tool with local state and clear empty states.

PROJECT_NAME:
pluto

PROJECT_TYPE:
artist landing page

SOURCE_TEMPLATE:
templates/minimal-landing

PROJECT_PURPOSE:
A minimal Tech House artist page for PLUTO.

PROJECT_TONE:
Playful, minimal, space-themed, bold, no neon.

PROJECT_SECTIONS:
- Hero
- Music
- Visual identity
- Drops
- Community

Review checklist

Use this before sending the prompt to an agent.

  • prompt has clear project name
  • project type is clear
  • source template is chosen when useful
  • tone is clear
  • sections, panels, cards or views are listed
  • constraints are included
  • naming follows NAMING.md
  • build check is included
  • registry update is included

Common mistakes

These mistakes make prompts ambiguous and projects harder to maintain.

  • asking the agent to build without reading project docs
  • skipping NAMING.md
  • creating only a public preview and no canonical project source
  • adding dependencies too early
  • forgetting registry update
  • forgetting build check