designesy-org: Instructions file for Codex

Designesy Agent Rules

You are operating inside Designesy.

This is not a typical web project.

Designesy is design intelligence infrastructure.

Core Understanding

Designesy turns: sources → principles → contracts → tools → systems → better designed work

Do Not

• Do not generate generic AI SaaS layouts.
• Do not assume this is a normal startup project.
• Do not build UI before structure and contracts exist.
• Do not invent design systems without source or rationale.
• Do not treat Labs as a blog or gallery.

Always

• Start from purpose, context, and system role.
• Use contracts (DESIGN.md) before inventing decisions.
• Prefer structure over surface.
• Encode reusable rules instead of one-off styling.
• Separate observed facts from derived design decisions.
• Verify outputs when visual quality matters.

Public Copy

• No em dashes in visible copy. A colon sits between a label and its description; a period, comma, semicolon or parentheses carries the rest; a middot joins a name to its descriptor.
• State the positive claim. Keep a negative when it carries a fact (a privacy guarantee, a scope limit, a prohibition, a disclaimer); rewrite "not X, but Y" pivots.
• Number ranges read "to" (5 to 10), in prose and in tables.
• Say a missing value in words. In a dense table use NotMeasured from apps/site/app/lib/data/figure.tsx: a dash for the eye, words for a screen reader.
• Quotations stay verbatim. Contract text changes only with its contract: the *-contract.ts modules and the /contracts pages move together.
• The build holds the line: scripts/check-voice.js fails a page that gains em dashes or pivots beyond scripts/voice-baseline.json, and scripts/check-jsx-glue.js fails a sentence that wraps so JSX glues two words together, and a space that can drop out of an accessible name. Keep the space inside a text run: wrap one word earlier, or write it into the neighbouring text or string (Fixes <span>, {` ${value}`}). In inline content, a {' '} (or a lone space between two children) beside text can be dropped from a name computed from content: links, buttons, summaries, headings, table headers and cells, a label's control. In a flex or grid container Chrome keeps it, and the gate flags it there too. Between two host elements (<span>, <b>) it is safe; a component that returns text, such as a number in a fragment, counts as text.