openai-aesthetic
Skill0 starsChanged 56 days agoMITView on GitHub
Apply the OpenAI visual design language to web pages, UI components, and documents. Use when asked to "make it look like OpenAI", "apply OpenAI design", "OpenAI style", or similar.
In this repository7 other files it gives its agents.
- ai-light-explainerSkill
- blind-reviewSkill
- chinese-web-typographySkill
- distill-agents-mdSkill
- rapportSkill
- test-guide-htmlSkill
- test-handoff-guideSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. About 0 are common, 18 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Use this skill when the user asks for:
- Distinctive: line 38
Use at most one accent color (see Accent & Graphics).
- Distinctive: line 50
Use these exact values. Do not introduce colors beyond the single accent below.
- Distinctive: line 73
Never use the accent as a large-area fill, on the primary button (stays black), or for headings.
- Distinctive: line 76
No gradients, no decorative photos or illustrations.
- Very specific: line 105
Shadows: avoid. If absolutely needed: rgba(0,0,0,0.08) 0px 1px 2px -1px
- Distinctive: line 118
Use sparingly. The only filled element on the page.
- Distinctive: line 137
No shadow. Structure comes from surface and whitespace.
- Distinctive: line 146
No colored left border. Use a light surface or a subtle hairline border.
- Very specific: line 151
Use #000000 only for the filled primary button.
- Very specific: line 152
Use #181818 for primary text and section headings.
- Very specific: line 153
Use rgba(0,0,0,0.12) for all borders.
- Distinctive: line 154
Use 9999px radius for pills, tags, buttons, inputs.
- Distinctive: line 155
Use 8px radius for cards (6px only for consumer marketing cards).
- Very specific: line 156
Use #3b5bdb only for links, focus rings, and small monoline icons.
- Distinctive: line 157
Use weight changes for hierarchy.
- Distinctive: line 161
Don't introduce a second accent color, and never use gradients.
- Distinctive: line 162
Don't use the accent as large-area fills or on the primary button.
- Distinctive: line 163
Don't reproduce OpenAI's wordmark or the Blossom icon.
- Distinctive: line 164
Don't use shadows on cards.
- Distinctive: line 165
Don't use weight 700/800.
- Distinctive: line 166
Don't use colored left borders for alerts.
- Distinctive: line 167
Don't use lifestyle illustrations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenAI Aesthetic
Apply the OpenAI visual design language. This is a monochrome-first, editorial, restrained system. Trust whitespace and typography; avoid decoration. One muted accent color is permitted — use it sparingly.
When to Use
Use this skill when the user asks for:
- "make it look like OpenAI"
- "OpenAI style"
- "OpenAI design"
- "apply OpenAI aesthetic"
- Clean, research-lab, documentation-style UI
Application Workflow
When triggered:
- Determine the surface: consumer/marketing (openai.com) or developers/docs/report (developers.openai.com).
- Consumer: larger display type, 6px card radius, full-bleed imagery, 1200px max-width.
- Developers/docs: smaller compressed scale, 8px card radius, #f9f9f9 cards, 900–1200px max-width.
- Apply the color tokens and type scale below.
- Build components using the prescribed radii and borders.
- Use at most one accent color (see Accent & Graphics). Never introduce gradients or heavy shadows.
- Output the result (CSS snippet, HTML file, or component code) and mention that it follows OpenAI aesthetic.
Design Philosophy
- Minimalism: pure white canvas, near-black type, at most one accent color.
- Restraint: the only filled black element is the single primary button.
- Editorial Canvas: typography and whitespace do the work.
- Geometric signature: pills (9999px radius) for interactive elements; 6–8px radius for cards.
Color Tokens
Use these exact values. Do not introduce colors beyond the single accent below.
| Name | Value | Role |
| Obsidian | #000000 | filled primary button only |
| Carbon | #181818 | primary text, section headings |
| Graphite | #282828 | nav text, links, icons |
| Ash Gray | #5d5d5d | secondary body text |
| Smoke | #8f8f8f | tertiary text, placeholders |
| Paper | #ffffff | page canvas |
| Fog White | #f9f9f9 | card backgrounds |
| Linen | #f3f3f3 | hover states |
| Mist Gray | #ededed | borders, dividers |
| Hairline | rgba(0,0,0,0.12) | all borders |
| Whisper | rgba(0,0,0,0.04) | hover tints |
| Accent Blue | #3b5bdb | links, focus rings, small monoline icons — the only color allowed |
| Accent Tint | rgba(59,91,219,0.06) | rare subtle highlight background (e.g., active link) |
Accent & Graphics
The base stays monochrome. Color and graphics are seasoning, not the dish.
- Exactly one accent color:
#3b5bdb. Use it only for text links, focus rings, small monoline icons, and tiny status dots. - Never use the accent as a large-area fill, on the primary button (stays black), or for headings.
- Graphics are limited to thin monoline icons and simple geometric marks (dots, rings, hairline rules).
- Never reproduce OpenAI's wordmark, the Blossom icon, or anything that imitates them.
- No gradients, no decorative photos or illustrations.
Typography
- Font stack:
"OpenAI Sans", Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Microsoft YaHei", sans-serif- Note: "OpenAI Sans" is OpenAI's custom typeface. Use it only if the project already has it loaded; otherwise fall back to Inter/system fonts.
- Weights: 400 (body), 500 (nav/labels/subheads), 600 (section headings). Never 700/800.
Type Scale
| Role | Size | Weight | Line Height | Letter Spacing | Use |
| display | 48px | 500 | 1.16 | -1.44px | hero headline only |
| heading | 28px | 600 | 1.21 | 0.31px | section headings |
| subheading | 22px | 500 | 1.26 | -0.22px | card titles, subsection heads |
| body-lg | 18px | 400 | 1.32 | -0.18px | hero subtitle |
| body | 16px | 400 | 1.6 | -0.01em | body copy |
| label | 14px | 500 | 1.5 | — | nav, tags, buttons |
| caption | 13px | 500 | 1.51 | -0.13px | metadata, footnotes |
Spacing & Shapes
- Base unit: 4px
- Page max-width: 1200px (consumer/marketing), 800–900px (docs/reports)
- Section gap: 32–64px
- Card radius: 8px (developers/docs), 6px (consumer)
- Pill/button/input radius: 9999px
- Link radius: 4px
- Border: 1px solid
rgba(0,0,0,0.12)— semi-transparent black, not gray hex - Shadows: avoid. If absolutely needed:
rgba(0,0,0,0.08) 0px 1px 2px -1px
Components
Filled Primary Button
background: #000000;
color: #ffffff;
font-size: 14px;
font-weight: 500;
border-radius: 9999px;
padding: 10px 16px;Use sparingly. The only filled element on the page.
Outlined Pill / Tag
background: transparent;
border: 1px solid rgba(0,0,0,0.12);
color: #000000;
font-size: 14px;
font-weight: 500;
border-radius: 9999px;
padding: 8px 16px;Card
background: #f9f9f9;
border-radius: 8px;
padding: 24px;No shadow. Structure comes from surface and whitespace.
Callout / Note
background: #f9f9f9;
border-radius: 8px;
padding: 16px 20px;
font-size: 15px;No colored left border. Use a light surface or a subtle hairline border.
Do's and Don'ts
Do
- Use
#000000only for the filled primary button. - Use
#181818for primary text and section headings. - Use
rgba(0,0,0,0.12)for all borders. - Use 9999px radius for pills, tags, buttons, inputs.
- Use 8px radius for cards (6px only for consumer marketing cards).
- Use
#3b5bdbonly for links, focus rings, and small monoline icons. - Use weight changes for hierarchy.
- Trust whitespace over dividers.
Don't
- Don't introduce a second accent color, and never use gradients.
- Don't use the accent as large-area fills or on the primary button.
- Don't reproduce OpenAI's wordmark or the Blossom icon.
- Don't use shadows on cards.
- Don't use weight 700/800.
- Don't use colored left borders for alerts.
- Don't use lifestyle illustrations; keep it text-first.
Example Prompts
- Hero section: white background, centered. Headline 48px weight 500 #181818, letter-spacing -1.44px. Subtitle 18px weight 400 #5d5d5d, 16px gap. Below: row of outlined pill tags spaced 8px.
- Feature card grid: 3 columns, 20px gap. Card #f9f9f9, 8px radius, 24px padding. 20px monoline icon #282828 top-left, 16px gap to 16px weight 500 #181818 title, 8px gap to 14px weight 400 #5d5d5d body.
- Report page: max-width 800px, white canvas. Section headings 22px weight 600 #181818 with bottom hairline border. Body 16px weight 400 #181818. Callouts use #f9f9f9 surface, no left border.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

