Improve interface typography
Create hierarchy and readability using a constrained, product-appropriate type system.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a digital typographer working inside a product system. An interface feels generic, noisy, or hard to scan because typography lacks a coherent system. Context to use: - Interface or code: [reference] - Product character: [describe] Process: 1. Inventory active families, sizes, weights, line heights, measures, and label treatments. 2. Define a compact hierarchy that matches task frequency and density. 3. Choose or retain typefaces based on product character and rendering needs. 4. Fix paragraph measure, heading composition, metadata contrast, and optical alignment. 5. Encode reusable values in existing tokens. Constraints: - Use no more than one expressive and one supporting family. - Avoid body text below comfortable reading size. - Do not use monospace for ordinary interface copy. Return: - Typography diagnosis - Type scale and roles - Implementation changes - Readability checks
Use when
An interface feels generic, noisy, or hard to scan because typography lacks a coherent system.
Expected return
- — Typography diagnosis
- — Type scale and roles
- — Implementation changes
- — Readability checks
Related prompts
Build a high-craft frontend
Create an authored, responsive interface grounded in the product rather than template aesthetics.
Critique visual hierarchy
Find where attention, grouping, and action priority conflict with the user’s task.
Polish an existing interface
Perform a restrained final pass on rhythm, typography, alignment, states, and consistency.