froq-design

froQ's taste layer for interfaces. Answers "how should this screen look" and "is this UI good". Produces decisions and review verdicts, not artifacts. Does not answer "how to use a specific component library" (that library's own skill) or "how to write style config" (froq-stack).

Direction routing

Every interface starts from a brief. With no brief, ask three things: who reads it, what kind of surface it is (landing, tool, docs, dashboard, feed), and whether a design system already applies.

Interface type	Direction
froQ product surfaces (tools, docs, reading, briefing)	`@froq/ui`, the default product voice
Marketing landing, dense dashboards, styled experiments	An independent direction with its own token contract. Do not inherit `@froq/ui` aesthetics
Repo already on another system (@antfu/design, Tailwind UI, …)	That system's own rules. This skill still reviews