Auto Prompt Generator

Build reusable, detailed prompts for future code generation requests using PHP in a single editable file.

Profile

Output Mode

Version Control Mode

Selected profile summary

Best for UI cloning, landing pages, portal pages, and lightweight PHP/HTML/CSS/JS sites.

Goal

Stack preference

Existing files or code to preserve

Domain / subdomain

Database / schema

Asset / CDN URLs

Required pages / endpoints

UI / layout edits

Security / auth needs

Must remain unchanged

Expected file structure

Environment standard

API contract

Testing

Extra requirements

Reset

The prompt updates after submit. Copy it and reuse it in future code-generation chats.

Where to edit design quickly:
Main background: :root --bg
Card color: :root --card
Main text: :root --text
Borders: :root --border
Primary button / icon box: :root --accent
Button text: :root --button-text
Corner radius: :root --radius

Generated Prompt

Use this output directly as your master instruction block for future projects.

MASTER PROMPT FOR CODE GENERATION

Use the selected profile below as the default baseline unless overridden by the project-specific inputs.

SELECTED PROFILE:
Profile 1 - Human-Editable UI Clone / PHP Website

PROFILE DESCRIPTION:
Best for UI cloning, landing pages, portal pages, and lightweight PHP/HTML/CSS/JS sites.

OUTPUT MODE:
FULL

VERSION CONTROL MODE:
LOCKED BASE VERSION

GLOBAL DEFAULTS:
1. Generate full working code, not snippets.
2. Keep code human-editable and easy to maintain.
3. Do not change unrelated functionality.
4. Keep the file structure simple unless a larger structure is necessary.
5. State exactly where colors, text, URLs, logos, ports, paths, keys, and other common variables can be changed.
6. Assume Ubuntu hosting by default.
7. Prefer Apache/Nginx, PHP/PHP-FPM, PostgreSQL, Node.js, or simple frontend stacks when appropriate.
8. Include setup steps, deployment notes, and test commands.
9. Include config-file or env-var guidance where relevant.
10. Keep the output practical and ready to use.

PROFILE DEFAULT REQUIREMENTS:
1. Generate full working code, not snippets.
2. Keep code human-editable, compact, and easy to maintain.
3. Replicate layout, colors, spacing, and box structure as closely as requested.
4. Do not change unrelated functionality.
5. Use CDN-based assets when URLs are provided.
6. State exactly where to change background colors, container colors, logo size, text labels, and links.
7. Prefer minimal dependencies and simple file structure.
8. Make it suitable for Ubuntu hosting with Apache or Nginx.
9. Provide deployment steps and file placement instructions.

PROFILE OVERRIDES:
1. Build a close visual match to the provided site, image, or layout.
2. Keep code compact and easy for humans to edit.
3. Use provided CDN assets for images/video/text where possible.
4. Provide an edit map for main background, container colors, text labels, logo size, button colors, and navigation links.
5. Keep dependencies minimal.

PROJECT-SPECIFIC INPUTS:
- Goal: [add goal]
- Stack preference: [add stack preference]
- Existing files or code to preserve: [add existing files/code]
- Domain/subdomain: [add domain/subdomain]
- Database/schema: [add database/schema]
- Asset/CDN URLs: [add asset/CDN URLs]
- Required pages/endpoints: [add required pages/endpoints]
- UI/layout edits: [add UI/layout edits]
- Security/auth needs: [add security/auth needs]
- Anything that must remain unchanged: [add unchanged requirements]

EXPECTED FILE STRUCTURE:
public, config, api, assets

ENVIRONMENT STANDARD:
Use getenv() or config files; never hardcode secrets.

API CONTRACT:
Use consistent JSON request/response format. Include versioning if applicable.

TESTING:
Include curl/browser test examples, expected results, and common failure checks.

SUGGESTED OUTPUT FILES:
index.php or index.html, optional assets folder, optional styles.css, optional script.js

RESPONSE FORMAT I PREFER:
- Full code
- Short explanation of file purpose
- Exact setup/deployment steps
- Exact places to edit common settings
- Test commands/examples