Skip to content
Back to search

majestic-ui

SkillWorks with Claude CodeGitHub

Use for any website, landing page, app screen, dashboard or UI component you build, redesign, polish, unslop, review or audit, for turning a design image or screenshot into code, and for consolidating an existing codebase's design. Copies one of 38 reference pages, defaults to the Geist family, a gallery palette and a flat look when the user states no preferences, and holds every page to a premium floor and a 12-point gate checked in a real browser.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aayan15728--majestic-ui-skill/badge.svg)](/listings/aayan15728--majestic-ui-skill)

HTML

<a href="/listings/aayan15728--majestic-ui-skill"><img src="/api/listings/aayan15728--majestic-ui-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The root of this repo **is** the skill, so installing it means putting this folder where your agent looks for skills.

**With npm** (easiest, no clone needed):

npx majestic-ui-skill install

That copies the skill into `~/.claude/skills/majestic-ui`. Add `--agent codex`, `--agent factory` or `--agent all` for other agents, and `--project` to install into the current project instead of your home folder.

**With git** (Claude Code):

git clone https://github.com/Aayan15728/majestic-ui-skill ~/.claude/skills/majestic-ui

Or with the [skills CLI](https://github.com/vercel-labs/skills):

npx skills add https://github.com/Aayan15728/majestic-ui-skill

<details> <summary><b>Other agents and project-only installs</b></summary>

<br />

The skill is a plain folder with a `SKILL.md` file, so any agent that supports skills can use it.

| Agent | Personal (all projects) | Project only | |---|---|---| | Claude Code | `~/.claude/skills/majestic-ui/` | `<repo>/.claude/skills/majestic-ui/` | | Codex | `~/.codex/skills/majestic-ui/` | `<repo>/.codex/skills/majestic-ui/` | | Factory Droid | `~/.factory/skills/majestic-ui/` | `<repo>/.factory/skills/majestic-ui/` |

Windows (PowerShell):

git clone https://github.com/Aayan15728/majestic-ui-skill "$HOME\.claude\skills\majestic-ui"

For an agent without skill support, point it at `SKILL.md` (or the shorter `SUMMARY.md`) and ask it to follow it.

Restart your agent session so it picks up the new skill.

</details>

<br />

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 299 lines
  1. ---
  2. name: majestic-ui
  3. description: Use for any website, landing page, app screen, dashboard or UI component you build, redesign, polish, unslop, review or audit, for turning a design image or screenshot into code, and for consolidating an existing codebase's design. Copies one of 38 reference pages, defaults to the Geist family, a gallery palette and a flat look when the user states no preferences, and holds every page to a premium floor and a 12-point gate checked in a real browser.
  4. ---
  5. # Majestic UI
  6. **The bar:** every page holds up next to the best indie and startup sites. "Clean" isn't enough; a clean page can still look like the default.
  7. | § | Section | | § | Section |
  8. |---|---|---|---|---|
  9. | 1 | [How to work](#1-how-to-work) | | 9 | [Layout and density](#9-layout-and-density) |
  10. | 2 | [Undecided defaults](#2-undecided-defaults) | | 10 | [Badge, CTA, proof](#10-badge-cta-proof) |
  11. | 3 | [Choosing a look](#3-choosing-a-look) | | 11 | [Product preview](#11-product-preview) |
  12. | 4 | [Copy](#4-copy) | | 12 | [Signature, motion, mobile](#12-signature-motion-mobile) |
  13. | 5 | [Color](#5-color) | | 13 | [Craft floor](#13-craft-floor) |
  14. | 6 | [Depth](#6-depth) | | 14 | [Refuse list](#14-refuse-list) |
  15. | 7 | [Atmosphere](#7-atmosphere) | | 15 | [Quality gate](#15-quality-gate) |
  16. | 8 | [Typography](#8-typography) | | | |
  17. | Open | When |
  18. |---|---|
  19. | `SUMMARY.md` | context is short or time is tight: every shared rule on one page |
  20. | `references/modes.md` | always: work modes, project context files, audits (P0–P3, usability score) |
  21. | `references/direction.md` | a new look: visitor modes, finding the world, color strategy, overused faces, generated looks, refine moves |
  22. | `references/design-to-code.md` | the user gives an image, screenshot or mockup to build |
  23. | `references/default-theme.md` | nothing decided: Geist scale, Gallery tokens, converting an example, light/dark tokens |
  24. | `references/sections.md` | anything below the hero: pricing, comparison, calculator, FAQ, footer… |
  25. | `references/interactions.md` | anything that toggles, expands, switches or calculates |
  26. | `references/shadcn.md` | React with Tailwind: prebuilt components, re-themed |
  27. | `references/nextjs.md` | Next.js or React: where each part goes, fonts, server/client, CI |
  28. | `references/app-ui.md` · `components.md` | product screens (dashboard, docs, tool) and states · reusable components |
  29. | `references/aiunslopper.md` | an existing screen looks machine-made |
  30. | `references/interface-rules.md` | while building, and as the audit checklist |
  31. | `examples/README.md` | the 38 reference pages with briefs |
  32. | Script (Node 22+, no install) | Does |
  33. |---|---|
  34. | `scripts/verify-render.mjs` | real-browser check: contrast over painted art, fonts drawn, overflow, focus, widget keys; `--dark`; `--app` for product screens; writes `compare.png` with a look code |
  35. | `scripts/extract-spec.mjs` | reads a design image into numbers: bands, boxes, radii, text sizes, colors; zoomable tiles |
  36. | `scripts/compare-image.mjs` | scores a build against a design image and names the regions that differ and why |
  37. | `scripts/inventory.mjs` | measures design sprawl in a codebase and proposes the tokens to consolidate to |
  38. | `scripts/slop-lint.mjs` | code lint; `--defaults` when nothing was decided |
  39. | `scripts/vendor-fonts.mjs` | puts a page's fonts next to it, or inlines them |
  40. | `scripts/score-pages.mjs` | ranks many pages or two skill versions |
  41. If a file is missing, carry on with this one. Generated pages fail four ways, and every rule below stops one: **flat** (nothing behind the headline), **clumsy headline**, **weak proof**, **forgettable or crowded**.
  42. ---
  43. ## 1. How to work
  44. 0. **Read the project and name the target.** Pick the work mode and the visitor mode (`modes.md`, `direction.md`). Read the code, tokens, assets, `PRODUCT.md` and `DESIGN.md`; write those two files when missing and the work is more than a one-off. Work on one page, section, component or state at a time. **The user's request and the project's system outrank this skill**; additions inherit the existing look.
  45. - **An image to build?** Follow `design-to-code.md`: extract the spec, build in passes, compare until it matches.
  46. - **An existing codebase to improve?** Run `inventory.mjs` first and consolidate tokens before restyling.
  47. - **Looks machine-made?** Follow `aiunslopper.md`.
  48. - **A product screen** (dashboard, docs, tool)? Follow `app-ui.md`, start from `field-analytics`, `dither-docs` or `dither-workspace`, and check with `--app`.
  49. - **React with Tailwind?** Use shadcn's prebuilt components for controls (`shadcn.md`).
  50. 1. **Check what's decided:** fonts, colors and style, separately. Undecided falls back to section 2.
  51. 2. **Look first:** open the chosen example's `web.jpg` and `mobile.jpg`. That's what done means.
  52. 3. **Copy, don't invent:** read its `principles.md`, `design.md`, `style.md`; copy `index.html`; replace brand, copy, data, tokens and fonts; keep structure, spacing and details. Build from scratch only when nothing fits.
  53. 4. **Write the angle** (section 4) and, for a new look, the direction contract (`direction.md` §10) before CSS. With an identity-less product and the user present, offer two or three directions with one trade-off each; otherwise pick one and say why.
  54. 5. **Build** (sections 4–14; below the hero `sections.md`; widgets `interactions.md`), then **pass the gate** (section 15).
  55. 6. **Deliver with fonts:** `vendor-fonts.mjs <page>` (or `next/font` in Next.js). Update `DESIGN.md` when the system changed.
  56. ## 2. Undecided defaults
  57. Recommendations for the ~99% of cases where the user stated no preference. A choice the user made or the project already has (brand guide, `DESIGN.md`, tokens, a fixed logo) always wins, including over the avoid list. A design image is a choice. Details: `default-theme.md`.
  58. - **Fonts: the Geist family.** Geist for UI and most headlines (600, or 300 for an airy oversized one, −0.035 to −0.045em); Geist Serif for editorial display (its single 400, −0.02 to −0.03em); Geist Mono for code and data. Body 17/1.47. No italics exist: emphasis is two-tone (second phrase `#6e6e73`), 300 against 600, or serif over sans. Swap an example's Newsreader or Instrument Serif to Geist Serif. **Not Inter:** it's the face generated UI lands on by default, so an undecided page never uses it; take Inter only when the user or the project already chose it.
  59. - **Colors: the Gallery palette.** Canvas `#ffffff`, parchment `#f5f5f7`, pearl `#fafafc`, ink `#1d1d1f`, muted `#6e6e73`, hairline `#e0e0e0`, dark tiles `#272729` / `#2a2a2c` / `#252527`, black; one action blue `#0066cc` (focus `#0071e3`, links on dark `#2997ff`) only for links, the primary pill and focus. Pills `11px 22px`, press `scale(.95)`; radii 8 / 11 / 18 / pill.
  60. - **Avoid unless asked:** Inter; drop shadows; Bricolage Grotesque; purple or violet; blue gradients (solid blue is fine); gradient backgrounds of any hue; more than six things in the first screen or four competing anywhere.
  61. - **Start from** `gallery-tiles` (sans) or `serif-globe` (serif, dark); convert other looks with the example's `principles.md`. Lint with `--defaults`.
  62. ## 3. Choosing a look
  63. Each `examples/<name>/` holds `index.html`, `web.jpg` (1440×900), `mobile.jpg` (390×844), `design.md`, `style.md`, `principles.md`. Pick by what the product is, and say why in one line. Examples marked as departing from the defaults are used as-is only when the user chose that look.
  64. | Folder | Look | For |
  65. |---|---|---|
  66. | `gallery-tiles` | **default**: white / near-black / parchment tiles, blue pills, product render | hardware, consumer, undecided |
  67. | `serif-globe` | **default family, dark**: Geist Serif, glyph globe, real checkout | payments, commerce, dev platforms |
  68. | `sections-kit` | **the lower page, light and dark**: board, split, band, bento, pricing, table, calculator, add-ons, FAQ, footer | every section under any hero |
  69. | `warm-wash` | peach wash, brackets, URL capture, browser dashboard | light SaaS, analytics |
  70. | `cinematic-black` | black, serif two-tone, lit desktop scene | premium desktop apps |
  71. | `serif-stats` | serif with italic word, sourced stat cards, live board | directories, media |
  72. | `playful-warm` | cream dune, icon tiles in headline, glossy button | creator tools |
  73. | `dark-split` | dark split, highlight, laurel, drawn blob of contents | kits, courses |
  74. | `ascii-workspace` | glyph art, integration tiles, diff and terminal | developer tools |
  75. | `serif-phone` | serif + italic, phone with a real conversation | consumer, assistants |
  76. | `pixel-panel` | orange panel, pixel blinds, window breaking out | Mac productivity |
  77. | `bold-yellow` | announcement bar, heavy headline, yellow pill + price | services, offers |
  78. | `voice-ribbon` | messy input → clean output ribbon | writing, voice |
  79. | `dark-highlight-pill` | pill nav, highlight pill + app icon, editor | Mac creative apps |
  80. | `pastel-dreamscape` | illustrated landscape, airy Geist 300 | studios, portfolios |
  81. | `glyph-heritage` | dark brown, amber italic, glyph landmarks | culture, courses |
  82. | `gradient-frame` | gradient frame, phone with data chips | fintech, mobile |
  83. | `mountain-dawn` | drawn dawn ridges, condensed serif, rect buttons | outdoor, travel |
  84. | `serif-cursors` | phone on arcs, multiplayer cursor tags | collaboration |
  85. | `warm-grey-glow` | tight heavy grotesk, price-in-CTA, serif-number dashboard | finance, B2B |
  86. | `electric-swirl` | electric-blue stipple, floating nav | dev tools, observability |
  87. | `shape-flanks` | geometric confetti from both edges | crafted B2B, agencies |
  88. | `stream-lines` | glyph lanes into one card | AI infrastructure, APIs |
  89. | `pixel-photo` | scene dissolving into pixels, mono link box | lifestyle APIs |
  90. | `riso-hills` | risograph grain, halftone, hatching | creative, media |
  91. | `fluted-glow` | fluted glass glow, lime bar | security, infra |
  92. | `peak-agency` | snowfield, dotted rails, highlight block | agencies |
  93. | `dusk-range` | alpenglow range, editor rising | prosumer desktop |
  94. | `rock-dashboard` | rails, dot matrices, boulders and fog over a dashboard | B2B with real UI |
  95. | `pixel-forge` | blue pixel field, Geist Pixel, dithered grove | creative AI, games |
  96. | `paper-canvas` | paper grain, lifted ruler corner, design-tool window | design and writing tools |
  97. | `clear-sky` | painted sky, low sun, lit peaks, serif headline, desktop preview | assistants, consumer apps |
  98. | `inset-panel` | cream page, hero inside a dark rounded panel, cards hanging from the CTA on connectors, tabs, highlighted testimonials | B2B SaaS, CRMs, sales tools |
  99. | `crimson-mesa` | painted night scene: mesas, crimson plain, lone figure; centered logo; run log | dev platforms, automation |
  100. | `paper-stack` | papers leaning in from the corners, pixel-word headline, search + filter finder, coupon dialog | courses, libraries, content |
  101. | `field-analytics` | **product screen**: sidebar, KPIs, line chart with tooltip, flow bands, heatmap, rings, folder tiles | dashboards, admin, analytics |
  102. | `dither-docs` | **product screen**: pill nav, section tree, article with a live dither demo, light and dark | docs, references |
  103. | `dither-workspace` | **product screen**: sessions rail, prompt composer and glass cards over dithered art | agent and tool home screens |
  104. ## 4. Copy
  105. - **Headline** 5–12 words in the product's own nouns; passes the swap test (a competitor couldn't paste it). Shapes: outcome + audience · imperative pair · the object itself · promise + qualifier · a category claim of three words or fewer.
  106. - **Lead** starts concrete (a number, an action, a mechanism) with one or two facts bolded. **Fine print** under the CTA: price, trial, platforms or guarantee.
  107. - **Avoid** autopilot phrases (without the noise · all in one place · supercharge · seamless · unlock · effortless · revolutionize · built for modern teams · Welcome back), exclamation marks, periods on buttons, and invented claims. Demo data may be invented; list every placeholder number in the report.
  108. ## 5. Color
  109. - Decide a strategy first: Restrained, Committed (one color owns 30–60%), Drenched, or Full palette. Undecided means Restrained Gallery. Light or dark comes from one sentence of physical scene, never the category.
  110. - Canvas has a temperature (`#fffdfb`, `#fbf6ea`, `#f6f5f1`; dark `#000`, `#141414`, `#191919`), except Gallery's white tiles. Ink is near-black; on dark, headings `rgb(237 237 237)` and body `rgb(163–170 …)`.
  111. - Muted text is ink mixed into the canvas (`color-mix(in oklab, var(--ink) 62–68%, var(--canvas))`), tinted from the hue on colored surfaces; never stock greys like `#888`.
  112. - **One accent** on the primary CTA, one data highlight and the signature: coral `#f0623a`, ember `#c2410c`, yellow `#fcc419`, forest `#1e6b45` or solid blue `#1d4ed8` work well. No purple, blue or purple-to-pink gradients, neon borders or rainbow charts.
  113. - Every color a token on `:root`; 4.5:1 for body text and text on the accent, measured on what's painted behind it.
  114. ## 6. Depth
  115. - Flat by default: no drop shadows, no `text-shadow`. Structure from 1px hairlines (`color-mix(in oklab, var(--ink) 9–14%, transparent)`, or `rgb(255 255 255 / .1)` on dark), surface steps and tile contrast; a glass edge `inset 0 1px 0 rgb(255 255 255 / .07)` on dark.
  116. - When shadows are wanted: exactly one, on the preview, offset and soft, tinted to the canvas (`0 30px 80px -28px rgb(80 40 20 / .28)`). Never a colored halo; hard offset blocks only in a truly neobrutalist look.
  117. ## 7. Atmosphere
  118. Never nothing behind the headline. One atmosphere, visible at 1440×900, calm right behind the text.
  119. - **Flat (fine undecided):**
  120. - gallery tiles (`gallery-tiles`)
  121. - glyph art (`ascii-workspace`, `glyph-heritage`, `serif-globe`)
  122. - a colored panel (`pixel-panel`)
  123. - a text ribbon (`voice-ribbon`)
  124. - a dark split (`dark-split`)
  125. - hairline arcs (`serif-cursors`)
  126. - shape flanks (`shape-flanks`)
  127. - glyph lanes (`stream-lines`)
  128. - print texture (`riso-hills`, `paper-canvas`)
  129. - a pixel field (`pixel-forge`)
  130. - terrain in front (`rock-dashboard`)
  131. - an illustrated scene on a solid ground (`crimson-mesa`)
  132. - an inset panel: the hero inside one dark rounded field (`inset-panel`)
  133. - objects leaning in from the corners (`paper-stack`)
  134. - dithered art behind panels (`dither-workspace`)
  135. - a lit scene (`cinematic-black`)
  136. - editorial plain, only with a strong headline move plus stat cards or a live board (`serif-stats`, `serif-phone`, `bold-yellow`)
  137. - **Gradient and color fields (only when chosen):** `warm-wash`, `playful-warm`, `dark-highlight-pill`, `mountain-dawn`, `gradient-frame`, `warm-grey-glow`, `electric-swirl`, `pixel-photo`, `fluted-glow`, `peak-agency`, `dusk-range`, `clear-sky`.
  138. - `overflow-x: clip` on `main` when a layer is wider than the viewport.
  139. ## 8. Typography
  140. - **Hero headline:** 56–88px desktop (max 6rem), 40–48px at 390, line height 0.98–1.1, 2 lines (3 max); `max-width` in `ch`.
  141. - **Weight by face:**
  142. - book and condensed serifs and display grotesks: 400–500 (Geist Serif only 400);
  143. - neutral grotesks: 500 calm, 600 Gallery, 700 conversion;
  144. - chunky grotesks: 700–800.
  145. - **Tracking:** −0.02 to −0.05em for display; 0 under 16px.
  146. - **One emphasis move:** two-tone, an italic serif word, a highlight block, a drawn underline, an inline icon, or a grey kicker. No gradient text.
  147. - **Text details:** `text-wrap: balance` on headings, `pretty` on paragraphs, `tabular-nums` on figures; measure 45–75ch; lead 16–19px (21–28 in Gallery), muted.
  148. - **Font budget:** 1–3 families per project (hard max 5, and 4–5 need a stated reason); about 4 weights; 6–8 sizes.
  149. - **Consistency:** one face per role everywhere; each heading level and component has one type spec as a token, reused on every page; reuse the project's faces before adding any.
  150. - **Fonts are real, self-hosted webfonts.** Overused faces (`direction.md` §6) need a reason. No system font as the brand face, no mono as a costume.
  151. ## 9. Layout and density
  152. - 4px grid; `flex`/`grid` with `gap`; tight inside groups, generous between.
  153. - Hero rhythm: nav 52–88 · top padding 72–148 · badge→h1 20–32 · h1→lead 20–28 · lead→CTA 28–40 · CTA→fine print 16–24 · hero→preview 56–96.
  154. - **Viewport budget:** first screen at most six things (nav, one badge, headline, lead, one CTA group, one visual); about four competing anywhere; one job and focal point per section.
  155. - Hero centered at ≤ 1200px unless split. One nav style. Below the hero: one section-heading spec, one container idea, 96–128px between sections, every card holding a real artifact (`sections.md`).
  156. ## 10. Badge, CTA, proof
  157. - **Badge:** at most one, only with real news or data (version + news, live counter, laurel, 6–9 integration tiles, dated chip). No category eyebrow, ✨, 🚀, "Introducing".
  158. - **CTA:** one primary, at most one quiet secondary.
  159. - Capture: input + inset button, 52px tall, 440–480 wide, radius 12.
  160. - Pills: 44–52px, plus a grey, outline or glass secondary. Gallery pills: `#0066cc` + outline, `11px 22px`.
  161. - Big block: 260–280 × 56 with real scarcity only.
  162. - Price inside: a dark CTA with the price in a capsule.
  163. - Pill + "From $9 ›" link + guarantee.
  164. - **Proof:** one or two, real or flagged: avatar stack + count, sourced stat cards, stat row between hairlines, press quote, logo strip, download count.
  165. ## 11. Product preview
  166. 56–96px below the hero, 1040–1200 wide (phone 280–340), radius 16–24, crossing the fold, framed by a hairline and surface step. One frame (browser, OS scene, app window, phone, split editor, live board, render). Inside: plausible names and numbers that prove the headline, 13–15px text, one accent highlight. No lorem, grey bars, fake sparklines, 11px dashboards, greetings, or floating "Trending ↗" toasts.
  167. ## 12. Signature, motion, mobile
  168. - **Signature:** one detail repeated 2–3 times (brackets, rails, glyph art, pixel blinds, cursor tags, rings, confetti, halftone, handles, a lime accent on dark…).
  169. - **Motion:** one curve `cubic-bezier(.22, 1, .36, 1)`; hero children rise 14px over 640ms, staggered 70ms; preview last at ~380ms; content visible by default. Hover is a 150ms color step; press `scale(.97)` (`.95` on pills). No `transition: all`, loops, floats, bounce or parallax (a live dot that is the signature gets `/* slop-ok: reason */`). `prefers-reduced-motion` turns it off.
  170. - **At 390:**
  171. - no sideways scroll and no overlap;
  172. - headline 40–48px and full-width CTAs;
  173. - rows stacked, chips `nowrap`, long names truncated;
  174. - colliding decoration hidden, previews simplified;
  175. - nothing under 12px.
  176. Restructure, don't shrink.
  177. ## 13. Craft floor
  178. The full list is `interface-rules.md`.
  179. - **Semantics:**
  180. - `<button>` for actions, `<a href>` for destinations;
  181. - a skip link to `<main id="main">`;
  182. - headings in order;
  183. - a visible `:focus-visible` everywhere;
  184. - `aria-label` on icon-only buttons and `aria-hidden` on decoration.
  185. - **Touch and forms:**
  186. - targets 24px desktop, 44px touch; never disable zoom;
  187. - real labels, the right `type`, `inputmode` and `autocomplete`;
  188. - placeholders end in `…`; paste is never blocked;
  189. - errors sit at the field and say how to fix it.
  190. - **Text, media and theming:**
  191. - `…`, curly quotes, `10&nbsp;MB`, `tabular-nums`;
  192. - images with `width`, `height` and `alt` (hero `fetchpriority="high"`, the rest lazy);
  193. - `theme-color`, plus `color-scheme: dark` on dark pages;
  194. - `::selection`, `caret-color` and `accent-color` from the palette.
  195. - **Content and states:**
  196. - containers survive long values;
  197. - designed empty, loading and error states;
  198. - status never conveyed by color alone;
  199. - labels say what happens.
  200. ## 14. Refuse list
  201. Legitimate only when the brief asks; reaching for one freely means rewrite it:
  202. - rows of same-size icon + heading + line cards, or cards nested in cards;
  203. - the hero-metric template;
  204. - a category eyebrow above the headline;
  205. - 01 / 02 / 03 without meaning;
  206. - gradient text, decorative glass;
  207. - side stripes thicker than 1px;
  208. - hard offset shadows;
  209. - emoji as icons;
  210. - a rounded icon tile above every heading;
  211. - grey text on a colored surface;
  212. - skipped heading levels or cramped padding;
  213. - an unneeded modal;
  214. - landing in a generated look (`direction.md` §7) when the brief left the look open.
  215. ## 15. Quality gate
  216. **Premium floor.** All eight, or the page isn't done:
  217. 1. Authored art in the first screen.
  218. 2. One material idea carried through.
  219. 3. A confident 64–104px headline in two lines.
  220. 4. Restraint: one accent, the viewport budget.
  221. 5. Specific proof.
  222. 6. Exact details: hairlines, one radius scale, one icon stroke, tabular figures, styled focus.
  223. 7. Quiet motion.
  224. 8. Equal care on mobile.
  225. The fastest fix is restarting from the closest example.
  226. **Step 1: measure.** `node <skill>/scripts/verify-render.mjs <page or url> --ref <skill>/examples/<closest> --out ./majestic-check` (add `--dark` for dark mode and `--app` for a product screen; `--cdp` reuses a running Chrome). It must report **0 errors**; fix warnings or say why they stay. Exit code 3 means no browser: say the visual points are unchecked. For a design image, also run `compare-image.mjs` until it scores 90+ (`design-to-code.md`).
  227. **Step 2: look.** Open `compare.png` and quote its 4-character look code in the report; the code exists only in the image. Open `desktop.png` and `mobile.png`, and crop details.
  228. **Step 3: judge, yes or no.** Any "no" means fix and re-run, up to three rounds; name anything still failing.
  229. 1. **Atmosphere** visible (or a justified editorial plain).
  230. 2. **Headline:** 2–3 lines, the right weight, one emphasis move, passes the swap test.
  231. 3. **Specific copy** with fine print and no invented claims.
  232. 4. **Preferences and defaults:** the user's applied exactly; otherwise Geist, Gallery, nothing avoided, one accent, 1–3 families, one spec per role.
  233. 5. **Preview** proves the headline.
  234. 6. **Signature** seen twice.
  235. 7. **Depth:** flat, or one soft shadow if wanted.
  236. 8. **Rhythm:** spacing, budget, squint order.
  237. 9. **Mobile:** no overflow, full-width CTAs, 40–48px headline.
  238. 10. **Craft floor:** keyboard, names, theme color.
  239. 11. **States** designed and reachable.
  240. 12. **Premium and side by side:** the eight floor items, same league as the example, one memorable thing; name the weakest and fix it.
  241. Then `node <skill>/scripts/slop-lint.mjs <files>` (`--defaults` when undecided): 0 errors. In a real project, wire both checks into a `check:ui` script and CI (`nextjs.md`).
  242. **Honesty.** The lint reads code and the render check measures pixels; neither judges taste. Never report an unchecked point as passed. Stop once the request is met.
  243. **Report** in 4–6 lines:
  244. - the mode and the look, and why;
  245. - the render result and the look code;
  246. - which preferences were the user's and which were defaults;
  247. - the signature;
  248. - what changed between renders, and what was verified;
  249. - the lint score and the placeholders to confirm.
  250. **Redesign or polish:** gate the current page first and fix only failed points. **Audit:** change nothing unless asked; rank findings P0–P3 as `file:line: problem → smallest fix`, with the usability score (`modes.md`).
README.md · README · 430 lines
  1. <div align="center">
  2. # Majestic-ui-skill
  3. **Ask your AI agent for a website. Get one that looks designed, not generated.**
  4. An agent skill that teaches Claude Code, Codex and other coding agents to build landing pages, app screens and dashboards
  5. that hold up next to the best indie and startup sites, and then checks its own work in a real browser before calling it done.
  6. [![Web](https://img.shields.io/badge/Web-aayansharma.netlify.app-111111?style=flat-square)](https://aayansharma.netlify.app)
  7. [![X](https://img.shields.io/badge/@aayanships-000000?style=flat-square&logo=x)](https://x.com/aayanships)
  8. [![License: MIT](https://img.shields.io/badge/license-MIT-2563eb?style=flat-square)](LICENSE)
  9. [![Agent Skill](https://img.shields.io/badge/agent-skill-f97316?style=flat-square)](SKILL.md)
  10. [![Examples](https://img.shields.io/badge/examples-38-16a34a?style=flat-square)](examples/README.md)
  11. [![Next.js 16 starter](https://img.shields.io/badge/starter-Next.js%2016-000000?style=flat-square&logo=nextdotjs)](starters/nextjs)
  12. [![npm](https://img.shields.io/npm/v/majestic-ui-skill?style=flat-square&color=cb3837&logo=npm)](https://www.npmjs.com/package/majestic-ui-skill)
  13. [![Node 22+](https://img.shields.io/badge/node-22%2B-339933?style=flat-square&logo=nodedotjs&logoColor=white)](scripts)
  14. [![Stars](https://img.shields.io/github/stars/Aayan15728/majestic-ui-skill?style=flat-square&color=eab308)](https://github.com/Aayan15728/majestic-ui-skill/stargazers)
  15. <br />
  16. <table>
  17. <tr>
  18. <td width="50%"><a href="examples/cinematic-black/"><img src="examples/cinematic-black/web.jpg" alt="cinematic-black example" /></a></td>
  19. <td width="50%"><a href="examples/clear-sky/"><img src="examples/clear-sky/web.jpg" alt="clear-sky example" /></a></td>
  20. </tr>
  21. <tr>
  22. <td width="50%"><a href="examples/inset-panel/"><img src="examples/inset-panel/web.jpg" alt="inset-panel example" /></a></td>
  23. <td width="50%"><a href="examples/pixel-forge/"><img src="examples/pixel-forge/web.jpg" alt="pixel-forge example" /></a></td>
  24. </tr>
  25. <tr>
  26. <td width="50%"><a href="examples/pixel-panel/"><img src="examples/pixel-panel/web.jpg" alt="pixel-panel example" /></a></td>
  27. <td width="50%"><a href="examples/rock-dashboard/"><img src="examples/rock-dashboard/web.jpg" alt="rock-dashboard example" /></a></td>
  28. </tr>
  29. <tr>
  30. <td width="50%"><a href="examples/serif-globe/"><img src="examples/serif-globe/web.jpg" alt="serif-globe example" /></a></td>
  31. <td width="50%"><a href="examples/sections-kit/"><img src="examples/sections-kit/web.jpg" alt="sections-kit example" /></a></td>
  32. </tr>
  33. </table>
  34. <sub>8 of the 38 reference pages that ship with the skill. Click any one to open its folder.</sub>
  35. </div>
  36. <br />
  37. ## The problem
  38. Ask an AI agent for a landing page and you usually get the same page: Inter everywhere, a purple-to-blue gradient,
  39. three feature cards, a drop shadow on every box, and "Supercharge your workflow" as the headline.
  40. It's clean, but it looks generated, and people can tell.
  41. **majestic-ui fixes that by giving the agent three things it doesn't have on its own:**
  42. - **Good taste to copy.** 38 complete, hand-tuned reference pages, so the agent starts from something great instead of from a blank file.
  43. - **Rules that remove the slop.** What to avoid, what to add, and what to keep, with sensible defaults for when you haven't picked a style.
  44. - **A gate it must pass.** A 12-point quality checklist plus scripts that open the page in a real browser and measure it, so "done" means checked, not guessed.
  45. <br />
  46. ## Install
  47. The root of this repo **is** the skill, so installing it means putting this folder where your agent looks for skills.
  48. **With npm** (easiest, no clone needed):
  49. ```bash
  50. npx majestic-ui-skill install
  51. ```
  52. That copies the skill into `~/.claude/skills/majestic-ui`. Add `--agent codex`, `--agent factory` or `--agent all` for other agents, and `--project` to install into the current project instead of your home folder.
  53. **With git** (Claude Code):
  54. ```bash
  55. git clone https://github.com/Aayan15728/majestic-ui-skill ~/.claude/skills/majestic-ui
  56. ```
  57. Or with the [skills CLI](https://github.com/vercel-labs/skills):
  58. ```bash
  59. npx skills add https://github.com/Aayan15728/majestic-ui-skill
  60. ```
  61. <details>
  62. <summary><b>Other agents and project-only installs</b></summary>
  63. <br />
  64. The skill is a plain folder with a `SKILL.md` file, so any agent that supports skills can use it.
  65. | Agent | Personal (all projects) | Project only |
  66. |---|---|---|
  67. | Claude Code | `~/.claude/skills/majestic-ui/` | `<repo>/.claude/skills/majestic-ui/` |
  68. | Codex | `~/.codex/skills/majestic-ui/` | `<repo>/.codex/skills/majestic-ui/` |
  69. | Factory Droid | `~/.factory/skills/majestic-ui/` | `<repo>/.factory/skills/majestic-ui/` |
  70. Windows (PowerShell):
  71. ```powershell
  72. git clone https://github.com/Aayan15728/majestic-ui-skill "$HOME\.claude\skills\majestic-ui"
  73. ```
  74. For an agent without skill support, point it at `SKILL.md` (or the shorter `SUMMARY.md`) and ask it to follow it.
  75. Restart your agent session so it picks up the new skill.
  76. </details>
  77. <br />
  78. ## Use it
  79. You don't need to call it by name. The skill switches on for any UI work. Just ask:
  80. ```text
  81. Build a landing page for my habit-tracking app.
  82. ```
  83. ```text
  84. This dashboard looks AI-generated. Make it look designed.
  85. ```
  86. ```text
  87. Here's a screenshot. Build it in Next.js and make it work on mobile.
  88. ```
  89. ```text
  90. Audit the UI in this repo and list the worst problems.
  91. ```
  92. ```text
  93. Make the pricing section bolder, but keep our brand colors.
  94. ```
  95. It works with plain HTML, React, Next.js, Tailwind, shadcn/ui, or whatever stack your project already uses.
  96. **Your own fonts, colors and brand always win** over anything in the skill.
  97. <br />
  98. ## How it works
  99. The skill turns "make it look good" into a repeatable process the agent follows step by step.
  100. 1. **Read the project first.** The agent looks at your code, colors, fonts and assets before designing anything, so new work fits what you already have. It can write a short `PRODUCT.md` and `DESIGN.md` so later requests stay on-brand.
  101. 2. **Pick the work mode.** Building something new is different from polishing or auditing. The mode decides how much the agent is allowed to change (see [Work modes](#work-modes)).
  102. 3. **Choose a look from the examples.** It picks the reference page that fits your product and tells you in one line why. For a brand-new product it can offer you two or three directions to choose from.
  103. 4. **Look before reading.** It opens the example's desktop and mobile screenshots first, because the screenshots define what "done" looks like.
  104. 5. **Copy, don't invent.** It copies the example's real HTML and swaps in your brand, copy, data and fonts, keeping the structure, spacing and small details that make it work.
  105. 6. **Write the angle.** Before touching CSS, it writes down the headline idea, the one "signature" detail, and what happens on mobile.
  106. 7. **Build, then pass the gate.** It renders the page in a real browser, measures it, fixes what fails (up to three rounds), and runs the slop linter.
  107. 8. **Report honestly.** It tells you what was checked, what was a default, and what it couldn't verify. It never marks an unchecked point as passed.
  108. <br />
  109. ## Features
  110. ### 38 reference pages
  111. Every example in [`examples/`](examples/README.md) is a complete page, not a snippet: 34 landing pages, 3 product screens
  112. (docs, an agent workspace and an analytics dashboard) and a kit of every common lower-page section. Each folder has:
  113. | File | What it's for |
  114. |---|---|
  115. | `index.html` | The full page, ready to copy |
  116. | `web.jpg` / `mobile.jpg` | Screenshots at 1440px and 390px, so the agent knows what "done" looks like |
  117. | `design.md` | Who it's for, how the first screen is composed, the page structure and mobile behavior |
  118. | `style.md` | The exact values: colors, fonts, weights, radii, motion |
  119. | `principles.md` | Why it works, which rules must survive, and how to adapt it |
  120. The [examples index](examples/README.md) maps each look to the kind of product it suits, so the agent picks a
  121. cinematic dark page for a Mac utility and a calm dashboard for analytics, not the other way around.
  122. ### Work modes
  123. The agent reads your request and picks a mode. Each mode limits what it may change, so "polish" never turns into a surprise redesign.
  124. | You say | Mode | What it changes |
  125. |---|---|---|
  126. | "build / design a landing page" | **Build** | Everything, inside your brief |
  127. | "redesign", "make it look less AI" | **Redesign** | The visual style, never your product facts or brand assets |
  128. | "polish", "clean up", "tighten" | **Polish** | Details only: spacing, focus, hover, contrast |
  129. | "simplify", "too busy" | **Simplify** | Removes and merges clutter, keeps every feature |
  130. | "review", "audit my UI" | **Audit** | Nothing. Gives you a ranked list of problems |
  131. | a screenshot + "build this" | **Recreate** | Nothing about the design. It matches the image |
  132. | "add a wow moment" | **Showpiece** | One focused interaction you choose from 2–3 ideas |
  133. | "unslop this" | **Unslop** | Fixes AI-looking craft, keeps the product |
  134. | "bolder", "quieter", "animate", "clarify"… | **Refine** | Only the thing you named |
  135. | a dashboard, docs page or tool | **App screen** | Follows product-screen rules for density and every state |
  136. ### Smart defaults when you don't pick a style
  137. Most people never say which font or color they want. When you don't, the skill uses tasteful defaults instead of the usual AI look:
  138. - **Fonts:** the Geist family (Geist, Geist Serif, Geist Mono), never Inter by default.
  139. - **Colors:** a calm "Gallery" palette of whites, greys and near-black, with one blue used only for links, the main button and focus rings.
  140. - **Depth:** flat. No drop shadows unless you ask.
  141. - **Avoided by default:** purple, gradient backgrounds, Bricolage Grotesque, and crowded first screens with more than six things competing.
  142. Anything you or your project already decided overrides these.
  143. ### Design image to code
  144. Give the agent a screenshot, mockup or Figma export and it switches to **Recreate** mode. It reads the image into
  145. real numbers (layout, sizes, spacing, colors), builds the page in passes, then scores its build against the image
  146. and keeps fixing until the match scores 90 or higher. The result is real HTML, not a screenshot pasted behind the page.
  147. ### Fixing AI-looking UI
  148. For an existing screen that looks machine-made, [`references/aiunslopper.md`](references/aiunslopper.md) gives the agent a triage
  149. step, a direction, ten focused passes, and a catalogue of the tell-tale signs to hunt down.
  150. ### Audits with a usability score
  151. In **Audit** mode the agent changes nothing. It returns a list of problems ranked by impact, each with the file
  152. and line and the smallest fix:
  153. | Severity | Meaning |
  154. |---|---|
  155. | **P0** | Blocks a task or excludes people (no keyboard access, unreadable contrast, sideways scrolling on phones) |
  156. | **P1** | Hurts most visitors (lost main button, missing loading or error states, fonts not loading) |
  157. | **P2** | Inconsistency or friction (two button styles, broken dark mode, tiny tap targets) |
  158. | **P3** | Polish (alignment, sharper copy) |
  159. It can also score the page against the ten classic usability heuristics, out of 40.
  160. ### The quality gate
  161. Before the agent says it's finished, the page has to pass. The **premium floor** is eight things every page needs:
  162. 1. Real art in the first screen, not an empty hero
  163. 2. One material idea carried through the page
  164. 3. A confident headline in two lines
  165. 4. Restraint: one accent color, a limited number of things on screen
  166. 5. Specific proof, not vague claims
  167. 6. Exact details: hairlines, one radius scale, tabular numbers, styled focus
  168. 7. Quiet motion
  169. 8. Equal care on mobile
  170. Then a **12-point yes/no check** covers atmosphere, headline, copy, your preferences, the product preview,
  171. the signature detail, depth, rhythm, mobile, accessibility, every state (loading, empty, error), and a final
  172. side-by-side comparison with the reference. Any "no" means fix and re-run.
  173. ### Accessible interactions
  174. [`references/interactions.md`](references/interactions.md) gives plain-JavaScript, keyboard-correct versions of the widgets landing pages
  175. need: accordions, tabs, switches, calculators, theme toggles, SVG charts, menus and dialogs.
  176. ### Light and dark mode
  177. Every token has a light and dark value, `sections-kit` shows every section in both, and the render check can test dark mode with `--dark`.
  178. ### Next.js 16 starter
  179. [`starters/nextjs/`](starters/nextjs) is the `sections-kit` example rebuilt as a real Next.js 16 + React 19 app: Geist through
  180. `next/font`, light and dark themes, server components by default with four small client islands,
  181. and an `npm run check:ui` command that runs the skill's checks.
  182. ```bash
  183. cd starters/nextjs
  184. npm install
  185. npm run dev
  186. ```
  187. <br />
  188. ## Command line
  189. The npm package ships one command, `majestic-ui`, that installs the skill and runs every checking script from anywhere.
  190. Use it with `npx` (nothing to install), or install it once with `npm install -g majestic-ui-skill`.
  191. | Command | What it does |
  192. |---|---|
  193. | `npx majestic-ui-skill install` | Install the skill for Claude Code. Options: `--agent claude\|codex\|factory\|all`, `--project`, `--dir <path>`, `--force` |
  194. | `npx majestic-ui-skill uninstall` | Remove the installed skill (same options) |
  195. | `npx majestic-ui-skill starter my-site` | Copy the Next.js 16 starter into `my-site` |
  196. | `npx majestic-ui-skill examples` | List the 38 reference pages and what each suits; add a name for one example's files |
  197. | `npx majestic-ui-skill lint page.html --defaults` | Run the slop linter |
  198. | `npx majestic-ui-skill verify page.html --ref gallery-tiles` | Run the real-browser check (example names work for `--ref`) |
  199. | `npx majestic-ui-skill compare design.png page.html` | Score a page against a design image |
  200. | `npx majestic-ui-skill extract design.png` | Read a design image into a spec |
  201. | `npx majestic-ui-skill fonts page.html` | Copy or inline a page's fonts |
  202. | `npx majestic-ui-skill score runs/` | Rank many pages |
  203. | `npx majestic-ui-skill inventory src` | Measure design sprawl in a codebase |
  204. | `npx majestic-ui-skill help` | Show every command and option |
  205. After a global install, drop the `npx` and use `majestic-ui <command>`.
  206. ## Scripts
  207. Seven checking tools. They need only **Node 22 or newer** and nothing to install. The browser ones use the
  208. Chrome, Chromium or Edge you already have.
  209. | Script | What it does |
  210. |---|---|
  211. | `slop-lint.mjs` | Scans your HTML and CSS for tell-tale AI-design habits, interface red flags and missing font files. `--defaults` also flags the default avoid list (Inter, shadows, purple, gradients). |
  212. | `verify-render.mjs` | Opens the page in a real browser at 1440px and 390px. Checks contrast over images, that fonts really load, overflow, keyboard focus and widget keys. Writes a side-by-side `compare.png`. |
  213. | `compare-image.mjs` | Renders your page at a design image's size and scores how closely they match, with the regions that differ and why. |
  214. | `extract-spec.mjs` | Reads a design image into numbers: sections, boxes, corner radii, text sizes, colors, plus zoomable tiles. |
  215. | `vendor-fonts.mjs` | Copies a page's fonts next to it (or inlines them) so it looks right wherever the file goes. |
  216. | `score-pages.mjs` | Runs the lint and render check over many pages and prints one ranked table, to compare design options. |
  217. | `inventory.mjs` | Measures design sprawl in an existing codebase (how many colors, sizes, radii, shadows, button styles) and suggests a consolidated set of tokens. |
  218. ```bash
  219. node scripts/slop-lint.mjs page.html --defaults
  220. ```
  221. ```bash
  222. node scripts/verify-render.mjs page.html --ref examples/gallery-tiles --out ./majestic-check
  223. ```
  224. `verify-render.mjs` also takes `--dark` (check dark mode), `--app` (dashboards and other product screens) and
  225. `--cdp http://127.0.0.1:9222` (reuse a running Chrome). If no browser is found it exits with code 3 and marks the
  226. visual checks as unverified instead of pretending they passed.
  227. <br />
  228. ## What makes the output different
  229. | Typical AI output | With majestic-ui |
  230. |---|---|
  231. | Inter, purple gradient, three cards | A look chosen from 38 real references to fit your product |
  232. | Invented from scratch every time | Copied from a proven page, then adapted |
  233. | Drop shadows on everything | Flat by default, one soft shadow only if wanted |
  234. | "Done!" with no proof | Rendered in a real browser, measured, and compared |
  235. | Looks fine at one width | Checked at desktop and mobile, with full-width buttons and no overflow |
  236. | Missing focus, labels and states | Keyboard, focus, contrast, and loading / empty / error states all checked |
  237. | "Polish" quietly redesigns everything | Work modes limit what may change |
  238. <br />
  239. ## What's in this repo
  240. ```text
  241. majestic-ui-skill/
  242. ├── SKILL.md the main workflow the agent follows
  243. ├── SUMMARY.md every rule on one page, for short context
  244. ├── references/ playbooks the agent opens only when needed
  245. │ ├── modes.md work modes, audits, usability score
  246. │ ├── direction.md choosing a look, color strategy
  247. │ ├── default-theme.md Geist + Gallery defaults, light/dark tokens
  248. │ ├── design-to-code.md turning an image into code
  249. │ ├── sections.md pricing, comparison, FAQ, footer…
  250. │ ├── interactions.md accessible widgets
  251. │ ├── app-ui.md dashboards and product screens
  252. │ ├── components.md reusable components
  253. │ ├── interface-rules.md keyboard, focus, forms, performance
  254. │ ├── aiunslopper.md fixing AI-looking screens
  255. │ ├── nextjs.md building in Next.js
  256. │ └── shadcn.md re-theming shadcn/ui
  257. ├── examples/ 38 reference pages + shared fonts
  258. ├── starters/nextjs/ Next.js 16 starter
  259. ├── scripts/ 7 zero-install checking tools
  260. ├── bin/majestic-ui.mjs the npx / npm command line
  261. └── package.json npm package setup
  262. ```
  263. <br />
  264. ## FAQ
  265. <details>
  266. <summary><b>Do I have to tell it which example to use?</b></summary>
  267. <br />
  268. No. The agent picks the example that fits your product and tells you why. You can name one if you have a favorite.
  269. </details>
  270. <details>
  271. <summary><b>Will it override my brand?</b></summary>
  272. <br />
  273. No. Your fonts, colors, logo and existing design system always win. The defaults only apply to things you haven't decided.
  274. </details>
  275. <details>
  276. <summary><b>Which frameworks does it support?</b></summary>
  277. <br />
  278. Any. The examples are plain HTML, and there are guides for Next.js, React with Tailwind, and shadcn/ui. In an existing project it uses your stack.
  279. </details>
  280. <details>
  281. <summary><b>Do the scripts need a browser?</b></summary>
  282. <br />
  283. The lint doesn't. The render checks use an installed Chrome, Chromium or Edge. Without one, they say the visual checks are unverified rather than passing them.
  284. </details>
  285. <details>
  286. <summary><b>Which agents does it work with?</b></summary>
  287. <br />
  288. Any agent that supports the skills format, such as Claude Code, Codex and Factory Droid. The rules are plain Markdown, so you can also point any agent at <code>SKILL.md</code>.
  289. </details>
  290. <details>
  291. <summary><b>Can I use the example pages commercially?</b></summary>
  292. <br />
  293. Not as-is. The code is MIT, but the designs, brand names and logos they're based on belong to their owners. Use them to learn the technique, and use the skill to build your own designs.
  294. </details>
  295. <br />
  296. ## License
  297. [MIT](LICENSE) for the skill, references, examples and scripts.
  298. The bundled fonts in [`examples/fonts/`](examples/fonts) (Geist, Geist Mono, Geist Serif, Geist Pixel, Funnel Display,
  299. Newsreader, Instrument Serif and Bricolage Grotesque) use the **SIL Open Font License 1.1**, not MIT. Their license
  300. files are in `examples/fonts/licenses/`; keep them with the fonts if you redistribute them.
  301. ## Disclaimer
  302. The example websites are study reconstructions of publicly visible designs, made to show what the skill can do. All product names, logos, and brand designs belong to their respective owners. This project is not affiliated with or endorsed by any of them.
  303. <br />
  304. <div align="center">
  305. ### Made by Aayan Sharma
  306. If this skill saved you time, a star on the repo helps a lot.
  307. [![Portfolio](https://img.shields.io/badge/portfolio-aayansharma.netlify.app-111111?style=for-the-badge)](https://aayansharma.netlify.app)
  308. [![X](https://img.shields.io/badge/X-@aayanships-000000?style=for-the-badge&logo=x)](https://x.com/aayanships)
  309. <sub>Questions, ideas, or something you built with it? Reach out on <a href="https://x.com/aayanships">X</a>.</sub>
  310. <br />
  311. <br />
  312. <sub>MIT License · Copyright (c) 2026 Aayan Sharma</sub>
  313. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.