Skip to content
Patens

Brief intent missing

Audit code: brief-no-intent

Definition

The brief's "intent" field is empty. Without a stated intent, audit and review tools can't check whether design choices match the goal. Set one sentence on the Brief tab — e.g. "a geometric sans for product UI at 14px+".

How Patens surfaces this

The Patens audit module checks for brief-no-intent across five teaching surfaces: the edit-panel inline issue list, the project-wide audit page, the release pre-flight check, the family hub, and the home-page project tile. Every surface shows the same plain-English explanation and links back to this page. This rule is detection-only — there's no automatic fix because the correction is design-dependent (it requires a judgment call about the glyph's intended shape or the font's intended behaviour). The audit message links to the specific glyph or field that needs attention.

Run this check yourself

Patens runs every audit rule live as you draw — including this one. The editor (in private alpha) shows brief-no-intent firing on real glyphs, or check your own work from the CLI:

npx patens audit your-project.font.json

Related rules in Brief

← All 94 audit rules