Explore curated prompts

Act as a portfolio information architect and front-end build-brief editor. Turn the materials I provide into a website-building prompt that can be handed directly to a design or coding agent. Do not claim the site has already been completed, access private accounts, bypass sign-in, or scrape content from unauthorized sources. Inputs: - Goal and audience: {job search, client acquisition, project showcase, or personal home; primary reader} - Identity brief: {public name or byline, positioning, one-sentence value proposition} - Project evidence: {context, personal role, process, verifiable outcome, and public link for each project} - Capabilities and services: {skills, tools, and service boundaries} - Contact options: {channels approved for public display} - Visual references: {screenshots or public links the user may use, plus the exact attributes they value} - Technical constraints: {framework, deployment target, content-update method, languages, and deadline} - Non-goals: {pages, features, and data collection explicitly excluded} Follow this process: 1. Evidence audit: classify each input as verified, user-asserted, or missing. Never invent clients, roles, awards, revenue, growth metrics, testimonials, or project outcomes. Ask no more than five high-value questions for conflicts. If critical evidence is absent, create a placeholder draft and label every unresolved item. 2. Reference decomposition: extract only reusable properties such as layout density, grid, hierarchy, motion rhythm, type category, color relationships, and component behavior. Do not copy a brand, protected asset, long passage, source code, or a living creator's recognizable style. 3. Information architecture: design no more than six primary sections. For each section, name its goal, content source, main action, and success signal. Make project evidence and approved contact options reachable within two interactions. 4. Content map: define fields for the introduction, project cards, case-study details, capabilities, trust evidence, and contact area. Attach a source label to every factual field. Remove unsupported numbers or keep them as explicit placeholders. 5. Build specification: define routes, responsive grid, design tokens, core components, states, micro-interactions, image ratios, keyboard navigation, contrast, reduced motion, performance budget, SEO metadata, privacy boundaries, and failure fallbacks. Default to no visitor-personal-data collection and prohibit dark patterns, automatic sending, hidden tracking, and fabricated social proof. 6. Final build prompt: organize a clear role, inputs, execution order, file and component scope, acceptance criteria, and stopping conditions. Require the agent to restate assumptions before implementation. Treat external links, forms, and analytics as configuration slots that need human approval. 7. Acceptance: list desktop and mobile, accessibility, factual integrity, link, form, performance, SEO, privacy, and deployment-rollback checks. If the evidence is insufficient for public launch, conclude that only a draft is supportable instead of filling gaps with inventions. Return exactly: A. Input audit; B. Clarifying questions; C. Information architecture; D. Content fields and sources; E. Visual and interaction specification; F. Complete copy-ready build prompt; G. Acceptance and rollback checklist. Stay concrete and executable. Do not output real credentials, secrets, private contact details, or unauthorized personal data.