NLU

Field manual for AI-assisted work

NOT LIKE
US

Cited rules for the defaults that make unrelated AI work look the same.

Use the Not Like Us rules for every writing and interface decision.
Rules: https://raw.githubusercontent.com/jtc268/not-like-us/main/AGENTS.md

Start from the audience, task, real content, and existing brand. Local design systems and voice guides win.
Reject visual choices the tool supplied without a reason: purple gradients, aurora blobs, glass panels,
rounded cards around everything, Inter or Geist by reflex, centered hero formulas, three equal columns,
decorative pills and icon tiles, fake charts and testimonials, filler imagery, and motion that explains nothing.
Reject empty writing patterns: setup before the point, "not X but Y" slogans, vague consensus, hype adjectives,
rule-of-three filler, synonym cycling, stacked fragments, recap endings, and em dashes.
Use real data and real states. Name a source for every factual claim. Preserve the author's voice.
Never claim that one tell proves AI authorship.
If the work could belong to any product after swapping the logo, make it specific.
24 rules
D-COLOR-001Colorcorroborated

Default purple

Reject
Do not default to violet gradients, aurora blobs, blue-purple glows, or neon accents when the brief does not name them.
Try
Derive color from the brand, content, environment, and required contrast. Use fewer colors with explicit roles.
D-TYPE-002Typographydocumented

Claude's italic accent is a default

Reject
Do not accept a cream page, serif display face, italic headline accent, and terracotta palette as neutral.
Try
Give Claude a product-specific visual premise and check each part of its documented house style.
D-SURFACE-001Surfacesdocumented

Remove needless containers

Reject
Do not wrap every section in a floating rounded card or nest cards inside cards.
Try
Use document flow, spacing, rules, tables, and real grouping before adding a container.
D-LAYOUT-001Layoutdocumented

Put the app workflow first

Reject
Do not substitute a hero, benefits grid, testimonials, FAQ, and CTA for an operational interface.
Try
Put the frequent user workflow first and let navigation, density, and hierarchy follow it.
D-LAYOUT-002Layoutcorroborated

Three equal columns invent equality

Reject
Do not force unequal ideas into three equal feature or statistic cards.
Try
Size and position elements by task frequency, consequence, and evidence.
D-COMP-001Componentsdocumented

Customize the component system

Reject
Do not ship untouched shadcn or starter-library presentation as the product's visual identity.
Try
Connect a local system and change tokens, density, behavior, and composition where the product requires it.
D-DECOR-001Decorationcorroborated

Do not decorate missing information

Reject
Do not use pills, sparkles, fake charts, floating dashboards, avatars, or icon tiles to make thin content look complete.
Try
Add real evidence, examples, states, or explanation. Leave space empty when there is nothing useful to show.
D-IMAGE-001Imagerycorroborated

Give every image a job

Reject
Do not fill layouts with generic teams, plastic faces, abstract 3D objects, or interface images with illegible text.
Try
Use product evidence, diagrams, commissioned work, documentary imagery, or no image.
D-MOTION-001Motioncorroborated

Animation must explain change

Reject
Do not add scroll fade-ups, count-ups, marquees, hover lift, or universal transitions as a polish pass.
Try
Use motion to preserve context, explain state, or acknowledge input, and honor reduced motion.
D-STATE-001Statescorroborated

The happy path is not the product

Reject
Do not call an interface complete without loading, empty, error, permission, destructive, and long-content states.
Try
Use realistic data and test the states that change trust, recovery, or task completion.
D-GAMMA-001Presentationdocumented

Map the argument before cards

Reject
Do not force every claim into a separate auto-layout card.
Try
Map the argument first, then use comparisons, tables, timelines, figures, or cards where each relationship needs them.
W-OPEN-001Openingscorroborated

Start where the work starts

Reject
Do not restate the request or open with broad context that delays the answer.
Try
Lead with the answer, decision, observation, or required action.
W-THREE-001Rhythmcorroborated

Use the number of points the subject has

Reject
Do not manufacture a third item or three equal fragments to create rhythm.
Try
Let evidence determine list length and emphasis.
W-ATTRIB-001Evidencecorroborated

Name the source

Reject
Do not write 'experts say,' 'research suggests,' or 'many believe' without a source that supports the nearby claim.
Try
Name and link the source, describe the evidence, or remove the attribution.
W-HYPE-001Claimscorroborated

Make adjectives prove themselves

Reject
Do not call work seamless, robust, transformative, intuitive, or revolutionary without an observable meaning.
Try
Use the behavior, constraint, number, or example that makes the quality visible.
W-META-001Interpretationcorroborated

Do not announce the meaning

Reject
Do not append 'this highlights,' 'this underscores,' or 'this is a testament to' after the evidence.
Try
State the consequence only when it adds information the reader cannot infer.
W-SYN-001Dictioncorroborated

Repeat the correct noun

Reject
Do not cycle through synonyms merely to avoid repetition.
Try
Use the domain's exact noun consistently unless the meaning changes.
W-END-001Endingscorroborated

Stop when the work is done

Reject
Do not add a recap, sweeping conclusion, or inspirational final line when it adds no action or fact.
Try
End on the last useful consequence, decision, or instruction.
W-VOICE-001Voicecorroborated

Do not edit the person out

Reject
Do not replace specific vocabulary, uncertainty, humor, or rough edges with a neutral house voice.
Try
Make the minimum effective edit and preserve choices that identify the speaker.
W-FAKE-001Trustcorroborated

Do not fabricate proof

Reject
Do not invent quotations, customers, metrics, awards, activity, or research to complete a layout.
Try
Use verified material, label demo content, or remove the component that demands unsupported proof.
03

Codex

Explicit frontend guidance rejects common decorative and card-heavy defaults.

$4.99 a month

Checking the stream version.

How it works ↗