Optional context
Add context when it helps
This prompt works as-is. Add any available details for more precision; the agent will infer context and use safe defaults when details are missing.
- One measurable business goal
- The target audience and primary action
- Brand copy and asset-usage boundaries
- The form destination or deployment environment
Ready-to-use prompt
Complete coding prompt
Copy and run it as-is. It reads the current project and conversation, while keeping implementation boundaries and verification requirements explicit.
Act as a coding agent responsible for both product communication and frontend delivery. Create a publishable landing page for the current target audience based on the current business goal. The page must guide visitors toward the current primary action, follow the current brand constraints, and work in the current deployment environment. Inspect the existing site, design tokens, components, copy, and deployment scripts first. When information is missing, proceed with clearly labeled assumptions, but never invent customer quotes, usage statistics, partner logos, or legal claims.
Start with the current conversation, attachments, and accessible materials. Treat available information as the input. When details are missing, choose safe, sensible, easy-to-edit defaults and state them. Ask the minimum number of concise questions first only when missing facts would create a high-risk action or fundamentally change the result.
Define an information sequence covering the user problem, value proposition, core capabilities, credible evidence, common questions, and the action point. Every section should support the same primary action; remove repeated calls to action and vague marketing filler. Implement a strong hero, scannable body, working links or form controls, and submitting, success, validation-error, and service-unavailable feedback. Preserve the existing brand language. If assets are not licensed, use neutral placeholders or typography rather than copying third-party logos and images. Support mobile and wide layouts, visible keyboard focus, sufficient contrast, semantic headings, and reduced-motion preferences.
Exercise the real page from the hero through the primary action, checking every link, form state, and breakpoint. Run the repository's formatting, type, test, build, and release-preflight commands, but do not deploy to production without authorization. Report completed sections, copy assumptions, the conversion journey, observed checks, missing assets, and exact release steps. Never describe an unconnected form, an unexecuted command, or an undeployed page as complete.
After it finishes
Do not rely on a claim of completion
Check the real page, runtime behavior, and test evidence item by item.
- The hierarchy supports one primary action
- All links and form states work for real
- Responsive accessibility and reduced motion are checked
- Preflight commands and missing assets are clearly recorded
Inspiration source
This prompt is an original adaptation. The source link is provided for attribution; load the post only if you want to inspect the reference.
The X embed stays off until you choose to load it. Loading it may share your IP address and browser information with X.