Build a content-first wireframe specification

Generate a structured wireframe copy specification with strict character counts and layout hierarchy before visual design begins.

Prompt

Prompt
Act as a principal UX content strategist. First, ask me 3 numbered questions in one message and wait for my response:
1. What is the specific page or modal being designed, and its primary user goal?
2. What are the key content blocks or components needed (e.g., hero, value props, form)?
3. What viewport is being targeted (mobile, desktop, or responsive)?

Once I answer, create a content-first wireframe specification:
- Break the interface into a logical vertical hierarchy from top to bottom.
- Define strict maximum character limits (with spaces) for every UI copy element to prevent layout breaks.
- Include realistic draft copy that follows standard usability guidelines.
- Flag copy risks such as translation expansion and truncation zones.

Output format:
Markdown table with columns: Hierarchy Order | Component Name | UI Element | Max Character Limit | Draft Copy | UX Rationale & Constraints.
Follow with a short bulleted list of Edge Cases to Test.

Example output

Example for: mobile checkout cancellation confirmation modal

Hierarchy OrderComponent NameUI ElementMax Character LimitDraft CopyUX Rationale & Constraints
1.0Modal HeaderTitle35 charsLeave checkout?Keep direct and concise; must fit on a single line on 320px screens.
2.0Body ContentExplanatory Text110 charsItems in your cart are not reserved and prices may change if you exit now.Plain statement of consequence without guilt-tripping or dark patterns.
3.1Action GroupPrimary Action (Keep)20 charsContinue orderClear affirmative action; style as high-contrast button.
3.2Action GroupSecondary Action (Cancel)20 charsExit and clear cartExplicitly states the destructive result; style as text link or low-emphasis button.
Edge Cases to Test
  • German translation expansion: The primary action may expand by up to 35%, potentially forcing text wrap on small mobile viewports.
  • Screen readers: Ensure focus shifts directly to the modal title upon trigger, followed by the body text before announcing actions.
  • Truncation: Never allow ellipsis on button copy; force container wrapping or dynamic font scaling if limits are exceeded.
Written by AI from this prompt. Your results will vary.

Paste into ChatGPT, Claude, or Gemini. The model will prompt you with three quick questions about your interface, target screen size, and required components before drafting the spec. Follow up by asking to adjust limits for German localization.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Design