Guidance & exceptions
Understand requirements, patterns and design judgment.
Instruction roles
- Requirements
- Protect functionality, truthful claims and accessibility. State conflicts and limitations.
- Patterns
- Adaptable starting points. Change them when the task or evidence calls for it.
- Taste hypotheses
- Design judgments to inspect in context. They are not high-confidence research findings.
When to break a pattern
Consistency means coherent roles and behavior, not identical layouts. A data-heavy dashboard, expressive landing and personal portfolio should not inherit the same hero and card grid.
Meaningful categorical colors and expressive brand palettes are valid. Poppins, purple gradients and familiar layouts can be considered choices. Font pairing should follow content, language, brand and legibility.
Research with references
For reference-led landing work, use a bounded study of accessible sources such as Mobbin or Lapa Ninja. Record what was actually visible, what principle transfers, what to reject and any access limits.
Glyph does not bundle a paid library integration. Public screenshots do not grant permission to redistribute assets or copy artwork and code. Build an original composition suited to the product.