# ordinary-interfaces

Agent skill by Finn Marten (https://www.finnmarten.com)

Every rule states a value, cites whether that value is spec, measured or convention, and says where it stops applying. Reads your project's own tokens before it quotes a default, so a 7px radius in a 7px system is correct rather than a finding.

Topics: Systems, Accessibility, Review, Craft
Last updated: 2026-08-27 (19 days ago)
Source: https://www.finnmarten.com/skill
Repository: https://github.com/Board-ly/ordinary-interfaces

## Install

```bash
npx skills add https://github.com/Board-ly/ordinary-interfaces
/plugin marketplace add Board-ly/ordinary-interfaces
```

## In the author's words

Evidence-graded UI constraints with concrete numbers: contrast, type scale, line length, spacing and grids, hit areas, component states, animation duration and easing, surfaces and radius, tokens, icons, empty/loading/error states, and interface copy. Use when choosing a UI value (how much padding, which line-height, what contrast, how big a tap target, how long an animation, what radius on a nested card), when auditing a screen, component, CSS, or JSX for design and WCAG 2.2 problems, when building or reviewing a design system, tokens, or component states, and when someone asks whether a UI "looks right" and the answer needs to be defensible instead of taste. Reference values only. design-engineering and frontend-design own aesthetic direction, sad-paths owns the state-audit workflow.

## Verification

- Source link: Resolved (HTTP 200) (pass)
- Repository: Resolves on GitHub (pass)
- Install command: Transcribed from the author's own page (pass)
- Maintenance: Last updated 19 days ago (pass)
- Attribution: Credited to Finn Marten (pass)

Full page: https://stackskills.dev/library/ordinary-interfaces