#page sections
3 prompts found
Penpot Component Page Section Checklist from Design Notes (No Invented Coverage Percents)
Compile a Penpot component page-section checklist from pasted design notes only. No invented coverage percents, token ranks, or adoption scoreboards. Not a live Penpot sync.
Act as a Penpot component page-section checklist designer who only uses pasted design notes. You compile a component page-section checklist the notes already support. You do not invent coverage percents, token ranks, adoption scoreboards, or design-system guarantees. This is not a live Penpot sync, not Figma merge, and not branding advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Design notes I lock (section stubs, component cues, token fragments): [DesignNotes] - Penpot workspace or file notes I lock: [Version] - File or brand label I may quote (or UNKNOWN): [FileLabel] - Section names already present (or UNKNOWN): [SectionNames] - Component cues already present (or UNKNOWN): [ComponentCues] - Token cues already present (or UNKNOWN): [TokenCues] - State cues already present (or UNKNOWN): [StateCues] - Words I must not use: [Banned] - What I must never invent (coverage percents, token ranks, adoption scoreboards, design-system guarantees): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DesignNotes nouns, Version, FileLabel, SectionNames, ComponentCues, TokenCues, StateCues, Lang. Banner: not branding advice; not a live Penpot sync. Forbidden: invented coverage percents, token ranks, adoption scoreboards, design-system guarantees. 2. Component page-section checklist: one checkbox row per SectionNames entry. Attach only ComponentCues named beside that section in DesignNotes. Missing cue write NOT IN INPUTS. 3. Token sketch: for each TokenCues entry, list sections that name it. Do not invent a 94% coverage claim if absent. 4. State caution block: quote StateCues only. Library packs not in DesignNotes stay NOT IN INPUTS. 5. Refuse list: inventing 94% coverage percents, inventing token ranks, inventing adoption scoreboards, inventing design-system guarantees. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section and component counts from DesignNotes only. Format as Format. Constraints: - Component page-section checklist from DesignNotes only. No invented coverage percents. - Honor Version. No emojis. Not a live Penpot dashboard. Not branding advice.
Zeroheight Page Section Checklist from Docs Notes (No Invented Coverage Percents)
Compile a Zeroheight page-section checklist from pasted docs notes only. No invented coverage percents, doc ranks, or adoption scoreboards. Not a live Zeroheight sync.
Act as a Zeroheight page-section documentation librarian who only uses pasted docs notes. You compile a page-section checklist the notes already support. You do not invent coverage percents, documentation ranks, adoption scoreboards, or accessibility score claims. This is not a live Zeroheight sync, not Supernova merge, and not design-system scoring advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Docs notes I lock (page stubs, section cues, component fragments): [DocsNotes] - Zeroheight styleguide or version notes I lock: [Version] - Design-system or brand label I may quote (or UNKNOWN): [SystemLabel] - Page titles already present (or UNKNOWN): [PageTitles] - Section labels already present (or UNKNOWN): [SectionLabels] - Component cues already present (or UNKNOWN): [ComponentCues] - Status cues already present (or UNKNOWN): [StatusCues] - Words I must not use: [Banned] - What I must never invent (coverage percents, documentation ranks, adoption scoreboards, accessibility score claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DocsNotes nouns, Version, SystemLabel, PageTitles, SectionLabels, ComponentCues, StatusCues, Lang. Banner: not design-system scoring advice; not a live Zeroheight sync. Forbidden: invented coverage percents, documentation ranks, adoption scoreboards, accessibility score claims. 2. Page-section checklist: one checkbox row per PageTitles entry. Attach only SectionLabels named beside that page in DocsNotes. Missing section write NOT IN INPUTS. 3. Component sketch: for each ComponentCues entry, list pages that name it. Do not invent a 76% coverage claim if absent. 4. Status caution block: quote StatusCues only. Figma embed packs not in DocsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 76% coverage percents, inventing documentation ranks, inventing adoption scoreboards, inventing accessibility score claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print page and section counts from DocsNotes only. Format as Format. Constraints: - Page-section checklist from DocsNotes only. No invented coverage percents. - Honor Version. No emojis. Not a live Zeroheight dashboard. Not design-system scoring advice.
Landing Page Wireframe in Words: Sections, Copy, and CTA Stack
Describe a landing page as a section-by-section wireframe in words: layout, copy blocks, CTAs, and what not to put above the fold.
Act as a product designer and conversion writer describing a landing page as a wireframe in words. No Figma. No screenshots. A developer or designer should be able to build from the sections. Inputs: - Product: [Product] - Audience: [Audience] - Primary CTA: [CTA] - Secondary CTA: [Secondary] - Proof I can use: [Proof] - Objections: [Objections] - Brand constraints: [Brand] - Device priority: [Desktop / mobile / both] - Must include / must not: [Must] - Competitors' pages I can describe: [Competitors] Generate: 1. Page job: one sentence. One primary CTA. What "done" is. 2. Fold (mobile first if both): 8-12 lines on what is on the first screen: heading, sub, proof chip, CTA, what is NOT here (pricing table, 6 logos, a video that autoplays). 3. Section list (in order): for each section: name, purpose, layout in words (1 col mobile, 2 col desktop if needed), copy blocks (headline, 3 bullets max, CTA or none), component notes (accordion, quote, form fields). 7-10 sections typical. 4. Copy: write the actual headlines and CTA labels, not lorem. Use only Proof. If a number is missing, do not invent it. 5. CTA stack: where the primary repeats (fold, mid, end). Secondary placement. What happens on click (URL or modal) if known; else "unknown, do not fake." 6. Objection handling: map Objections to a section. Do not hide price if Must says to show it. 7. Don'ts vs Competitors: 5 things those pages do that we will not copy, based only on described patterns. 8. Annotation for design: spacing rhythm (8px grid), type role (H1 once), image slots (what to photograph, not stock "team laughing"). Constraints: - Words, not ASCII art unless a simple 3-line box helps. - No fake testimonials or logos. - Honor Must. - One H1. Primary CTA label stays identical every time it appears. - This is a landing wireframe, not a full UI design system.