⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
unslop-ui
Cut AI tells from interface and chart copy: eyebrow labels, 01/02/03 numbering, redundant subtitles, captions that explain what is already visible, leaked design notes, decorative badges, status dots, chart clutter and legends a direct label could replace. Applies /pstack:unslop to every string it keeps. With --surface it also fixes gradients and glows, off-scale spacing, extra-heavy weights and decorative motion.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
Agents decorate everything they build: a tiny uppercase label over every heading, 01 // before each feature, a subtitle that repeats the title, a caption explaining the button you are looking at, a green "LIVE" dot wired to nothing. unslop-ui finds those patterns, removes them, and tells you what it cut and what it left for you to decide.
It is the interface companion to /pstack:unslop, which cleans prose. unslop-ui loads unslop's rules when it runs and applies them to every string it keeps.
What it removes
| Id | Pattern | Example |
|---|---|---|
| U1 | Eyebrow labels | INTRODUCING LEDGER above the H1 |
| U2 | Decorative numbering | 01 //, 02 // on features with no real order |
| U3 | Subtitle reflex | "Analytics" with "Understand your data better" under it |
| U4 | Botsplaining | "Click the button above to get started" |
| U5 | Leaked design notes | "(updates in real time)", "This card shows..." |
| U6 | Status strings | Live · v2.4 · Synced · Updated just now |
| U7 | Labeling everything | Label, placeholder and helper text that all say "email" |
| U8 | Staccato slogans | "Finance. Simplified. Finally." |
| U9 | Badges without state | NEW, AI, Beta added for flavor |
| U10 | Status dots | animate-pulse dot next to static data |
| U11 | Decorative emojis | 🚀 Get started, 💰 Revenue |
| U12 | Chart titles that name the chart | "Line chart of weekly active users" |
| U13 | Reading instructions | "Each point represents one week. Hover for details." |
| U14 | Saying it twice | A value on every point plus axis plus gridlines; ▲ 12% up plus "Revenue grew 12%..." |
| U15 | Chart scaffolding | Frame box around the plot, dark or dense gridlines, thick axes, shadows, 3D |
| U16 | Legend instead of a label | A legend box when each line could carry its name at its end |
Surface rules (opt-in)
Add --surface and the skill also fixes four visual tells, each with a concrete replacement value from references/tokens.md:
| Id | Pattern | Fix |
|---|---|---|
| U17 | Hue-to-hue gradients, gradient text, colored glows, blurred blobs | Solid neutral surface, hairline border, shadow no stronger than 0 1px 2px rgb(0 0 0 / 0.05) |
| U18 | Off-scale spacing: mt-[13px], gap: 7px | Nearest step of 4, 8, 12, 16, 20, 24, 32, 40, 48, 64 |
| U19 | font-extrabold, font-black, weights 800 and 900 | 500 or 600 |
| U20 | transition-all, hover:scale-* on cards, animate-bounce | Named properties at 150ms ease-out |
/unslop-ui src/pages/dashboard.tsx --surface
Without the flag these four never run, so a plain /unslop-ui behaves as before. They replace a value with a better value. They don't change the palette, the type family or the layout. For that, see Pairs well with.
Every run ends with a verdict: heavy (work through every rule), light (fix only what was found) or none (edit nothing, say so). A screen with nothing to cut is left alone.
Without --surface it leaves logic, data, colors and layout alone. It keeps aria-label, alt and screen-reader text, and moves a cut label into aria-label when it was the only accessible name. Anything that reflects real state (a live connection, a real step order) stays, and the report says why.
Examples
All three come from examples/: the files in before/ were written to be full of tells, and after/ is the unedited output of one /unslop-ui run in a fresh Claude Code session. The drawings show those files rendered with sample data, and each tell carries the id of the rule that removed it.
A dashboard
- <p className="... uppercase tracking-[0.2em] ...">Overview</p>
<h1 className="text-2xl font-semibold">Dashboard</h1>
- <p className="text-muted-foreground">A real-time overview of your key business metrics, all in one place.</p>
- <CardTitle>💰 Total revenue</CardTitle>
+ <CardTitle>Total revenue</CardTitle>
- <span className="text-green-600">▲ 12% up</span>
- <CardDescription>Revenue grew 12% compared to last month, showing strong momentum.</CardDescription>
+ <span className="text-green-600">+12% vs last month</span>
- <span ...><span className="size-2 rounded-full bg-emerald-500 animate-ping" />Live</span>
- <CardDescription>This card shows the number of users active right now (updates in real time).</CardDescription>
- <span className="text-xs">Last 30 days · All plans · Excl. trials</span>
+ <span className="text-xs">Last 30 days</span>
A chart
plugins: {
- title: { display: true, text: "📈 Line chart of weekly active users" },
- subtitle: { display: true, text: "Each point represents one week — hover over a point to see the exact value." },
- legend: { display: true, position: "bottom" },
- datalabels: { display: true },
+ title: { display: true, text: "Weekly active users" },
+ legend: { display: false },
+ datalabels: {
+ display: (ctx) => ctx.dataIndex === ctx.dataset.data.length - 1,
+ formatter: (value, ctx) => `${ctx.dataset.label} ${value}`,
+ align: "right",
+ offset: 8,
+ },
},
scales: {
- x: { grid: { color: "#9ca3af", lineWidth: 2 }, border: { display: true, width: 2, color: "#111827" } },
- y: { grid: { color: "#9ca3af", lineWidth: 2 }, border: { display: true, width: 2, color: "#111827" }, ticks: { stepSize: 25 } },
+ x: { grid: { color: "#e5e7eb", lineWidth: 1 }, border: { display: true, width: 1, color: "#d1d5db" } },
+ y: { grid: { color: "#e5e7eb", lineWidth: 1 }, border: { display: false }, ticks: { stepSize: 25 } },
},
A landing page
The page from the drawing at the top, rendered in a browser. Full files: before, after.

By the numbers
The counter only sees the patterns a regex can find. The run also removes the ones that need reading, such as subtitles, botsplaining, slogans and chart titles, and its report counts those separately.
Install
With the skills CLI, for Claude Code, Cursor, Codex and other agents:
npx skills add felipebasurto/unslop-ui -g
As a Claude Code plugin:
claude plugin marketplace add felipebasurto/unslop-ui
claude plugin install unslop-ui@unslop-ui
By hand:
git clone https
// HOW IT'S BUILT
// FILES
7 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/unslop-ui/SKILL.md10 KB89a96ddd61b5upstream ↗
--- name: unslop-ui description: "Cut AI tells from interface and chart copy: eyebrow labels, 01/02/03 numbering, redundant subtitles, captions that explain what is already visible, leaked design notes, decorative badges, status dots, chart clutter and legends a direct label could replace. Applies /pstack:unslop to every string it keeps. With --surface it also fixes gradients and glows, off-scale spacing, extra-heavy weights and decorative motion." disable-model-invocation: true argument-hint: "[file, folder or component] [--surface]" allowed-tools: Bash(python3 *) --- # Unslop UI Edit the visible text and decorative chrome of a web page, app screen, chart or dashboard so it stops reading as AI-generated. A good interface is used, not read: keep the words a person needs to act, and cut the rest. Target: $ARGUMENTS (if empty, use the files changed in this conversation, or ask). Scope: copy, decoration and charts by default (U1 to U16). If the arguments include `--surface`, also apply U17 to U20 (gradients and glows, off-scale spacing, heavy weights, motion), using the values in [references/tokens.md](references/tokens.md). Strip `--surface` from the target before reading paths. ## Writing rules from /pstack:unslop Apply these to every string you keep. Cite them by their number. !`python3 ${CLAUDE_SKILL_DIR}/scripts/load_unslop.py` If the line above still shows a command instead of rules (agents other than Claude Code), run `python3 scripts/load_unslop.py` from this skill's folder and apply what it prints. ## UI rules Ids are stable. Cite them as U1 to U20 in the report. ### Interface copy - **U1. Eyebrow labels.** Small uppercase or letter-spaced text above a heading ("PASSPORT", "FEATURES", "HOW IT WORKS"). Delete it. The heading already says what the section is. - **U2. Decorative numbering.** "01 02 03", "01 // Features", "§", "//" prefixes. Delete unless the order is real and the user follows it (steps of a checkout, a numbered install guide). - **U3. Subtitle reflex.** A subtitle under every heading, or a line above the H1. Keep one only when it states a fact the heading doesn't. "Analytics / Understand your data better" loses the second line. - **U4. Botsplaining.** Captions, helper text and descriptions that narrate what the element visibly does ("Click the button below to get started", "This chart shows revenue over time"). Delete. Headings and captions stay at 5 words or fewer. Exempt: empty states, error messages, and confirmations of destructive actions, which may use a full sentence. - **U5. Leaked design notes.** Text about how the screen works or why it was designed that way, long parentheticals, "(updates in real time)", "(powered by AI)". Delete it, or move it to a tooltip if a user would genuinely look for it. - **U6. Status strings.** Facts chained with "·" or "|" ("12 items · Updated 2m ago · Synced · v2.1"). Keep the one fact the user acts on. Put others where they're needed, or drop them. - **U7. Labeling everything.** A label that repeats the placeholder, the icon, the button text, or the section heading. Pick one cue. A search field with a magnifier icon needs neither a "Search" label nor a "Search..." placeholder beyond one of them. - **U8. Staccato and empty slogans.** "One. Big. Thing.", "Built different.", "Ship faster. Think less." Rewrite as one sentence that names the thing and what it does, or delete. ### Decoration - **U9. Badges and pills without real state.** "LIVE", "NEW", "AI", "Beta", "Pro", "🔥 Popular" added for flavor. Keep a badge only if it reflects data the app actually tracks (a real stream is live, an item is actually new since the last visit). - **U10. Status dots.** Pulsing or colored dots (`animate-pulse`, small `rounded-full` dots) next to text. Keep only if bound to a real live status. - **U11. Decorative emojis and icons.** In headings, buttons, KPI labels and list items. Delete. An icon stays only if it is the control itself (icon button with an `aria-label`) or if it carries meaning the text does not. ### Charts and dashboards - **U12. Chart titles that name the chart type.** "Bar chart of monthly revenue" becomes "Monthly revenue", or the finding: "Revenue doubled since March". - **U13. Reading instructions.** Subtitles or captions that explain how to read the chart ("Each bar represents one month", "Hover for details"). Delete. - **U14. Saying it twice.** Each quantity gets one encoding. A bar, a number on the bar, a gridline at its height and an axis tick all saying the same value is three too many; a KPI with arrow plus percent plus the word "up" plus a sentence under it ("Revenue grew 12% compared to last month") is the same mistake in text. Keep the encoding the reader needs: axis and gridlines for shape, a printed value for the number that matters (often only the last point or the max). - **U15. Chart scaffolding that competes with the data.** A frame box around the plot area, dark or dense gridlines, minor ticks, thick axis borders, 3D, drop shadows and glows on marks, background fills behind the plot. Delete them, or make what must stay (a few gridlines, one baseline) a hairline in a light gray. Data on top, labels next, scaffolding faintest. Do not redesign the chart: same type, same data, same series colors. - **U16. Legend where a direct label works.** A legend box that makes the reader match colors to names, when the name could sit at the end of the line or next to the bar. Label the series directly, ideally with its latest value ("This year 1,150"), and remove the legend. Keep a legend for more than four series or when the marks are too close to label. ### Surface (only with `--surface`) Each rule pairs the tell with its fix. Read [references/tokens.md](references/tokens.md) for the values. - **U17. Gradients and glows.** A gradient from one hue to another on a surface, button or active item, gradient text (`bg-clip-text`), colored glows (`shadow-[0_0_20px_...]`, `shadow-purple-500/50`), blurred color blobs behind content. Fix: a solid neutral surface, solid text color, a neutral shadow no stronger than `0 1px 2px rgb(0 0 0 / 0.05)`, or a hairline border. A gradient that is only a tone shift inside one neutral can stay. - **U18. Off-scale spacing.** One-off values such as `mt-[13px]`, `py-[11px]`, `gap: 7px`. Fix: the nearest step of 4, 8, 12, 16, 20, 24, 32, 40, 48, 64. Siblings that do the same job (rows of one list, cards of one row) get the same value. Keep a 2px nudge inside a small control and an odd value that exactly centers something. - **U19. Extra-heavy weights.** `font-extrabold`, `font-black`, `font-weight: 800` or `900`. Fix: 500 or 600, and let size and color carry the hierarchy. - **U20. Decorative motion.** `transition-all`, `hover:scale-*` on cards, `animate-bounce`, springs and overshoot on simple UI. Fix: transition named properties (`transition-colors`) at 150ms ease-out, keep a press scale of 0.97 to 0.98 if the control has one. Motion that explains something stays. Pulsing dots are U10. U17 to U20 never change the palette, the type family, the layout structure or the order of sections. They replace a value with a better value, they don't redesign. For before/after pairs, read [references/examples.md](references/examples.md) when unsure how far to cut. ## Guardrails - Change visible text and decorative elements only. Do not touch logic, data, colors, spacing tokens or layout structure. The exceptions are chart scaffolding under U15, which may be thinned or lightened, and U17 to U20 when `--surface` is on. - If the project already has tokens (Tailwind theme, CSS variables, a design-system package), fix toward those and not toward the fallback values in `references/tokens.md`. - Never change a screen that has nothing to cut. See the verdict in step 3. - When you delete an element, delete its now-empty wrapper and any margin or gap that existed only for it. A wrapper left holding a single child it only existed to group goes too. - Never delete `aria-label`, `alt`, `title` on icon buttons, or screen-reader-only text. If cut visible text was the only accessible name, move it into `aria-label`. - Text that comes from data, props, i18n files or a CMS: edit it at its source (the translation file, the fixture) or report it, don't hard-code a replacement in the component. - If a flagged case earns its place (real state, real order, legal text), keep it and say why in the report. ## Procedure Copy this checklist and track it: ``` - [ ] 1. Count: python3 ${CLAUDE_SKILL_DIR}/scripts/count_tells.py [--surface] <target> (${CLAUDE_SKILL_DIR} is this file's folder) - [ ] 2. Read every visible string and decorative element; tag each problem with U1-U20 or an unslop rule number - [ ] 3. Verdict: heavy, light or none - [ ] 4. Edit - [ ] 5. Count again with the same command - [ ] 6. Report ``` Verdict, from the count and your reading: - **Heavy.** Tells in most of the rules, or the same tell repeated across the screen. Work through every rule. - **Light.** A few tells. Fix only those. Leave everything else exactly as it is. - **None.** The counter is at 0 and reading finds nothing that earns a cut. Say so, edit nothing, and name at most two optional refinements. A clean screen is a result, not a failure. The counter is a regex heuristic. It finds candidates and gives a before/after number. It misses U3, U4, U5, U7, U8, U12, U13 and U14, which need reading. With `--surface` it also counts U17 to U20 (gradient and glow utilities, off-scale pixel values, weights 800 and 900, `transition-all` and friends); it cannot tell a hue-to-hue gradient from a tone shift inside one neutral. For U15 and U16 it only sees the code forms (shadows, thick axis borders and gridlines, legends turned on). It also flags some legitimate cases. Your reading in step 2 is the real check. Report format: | Rule | Before | After | |---|---|---| | U1 eyebrow | 6 | 0 | | unslop 13 em dash | 4 | 0 | Then list what you kept on purpose, one line each, with the reason. Last, list anything you found but did not edit (data from a CMS, a decision that is the owner's) as tasks, each with its fix: ``` - [ ] src/i18n/en.json:42 U3 subtitle "Understand your data better": remove or replace with a fact ```skills/unslop-ui/scripts/count_tells.py5.1 KB2a2fdd24f736upstream ↗
#!/usr/bin/env python3 """Count UI slop candidates in a file or folder. Usage: python3 count_tells.py [--surface] <file-or-folder> [...] Prints JSON: {rule: {"count": n, "examples": ["file:line", ...]}}. Regex heuristic for before/after comparison. It misses tells that need reading (U3, U4, U5, U7, U8, U12, U13, U14) and can flag legitimate cases. --surface adds the visual rules U17 to U20 (gradients and glows, off-scale spacing, extra-heavy weights, motion). """ import json import os import re import sys EXTENSIONS = {".html", ".htm", ".jsx", ".tsx", ".js", ".ts", ".vue", ".svelte", ".astro", ".md", ".mdx"} SKIP_DIRS = {"node_modules", ".git", "dist", "build", ".next", ".svelte-kit", ".astro", "coverage"} # Enough to show where to look without flooding the agent's context. MAX_EXAMPLES = 5 EMOJI = re.compile( "[\U0001F300-\U0001FAFF\U00002600-\U000027BF\U0001F000-\U0001F2FF\U00002B50\U00002B55\U0000231A-\U0000231B\U000023E9-\U000023FA]" ) RULES = [ ("U1 eyebrow", re.compile(r"\buppercase\b.*\b(tracking-|letter-spacing)|\b(tracking-|letter-spacing).*\buppercase\b|text-transform:\s*uppercase")), ("U2 decorative numbering", re.compile(r">\s*0[1-9](?:\s|<|\.|/)|['\"`]0[1-9]['\"`]|>[^<>{}]*?(?<!:)//[^<>]*<")), ("U6 status string", re.compile(r"·|·|·|\·")), ("U9 badge word", re.compile(r">\s*(?:LIVE|Live|NEW|New|BETA|Beta|AI|PRO|Pro|HOT|Hot)\s*<|['\"`](?:LIVE|NEW|BETA|HOT)['\"`]")), ("U10 status dot", re.compile(r"animate-pulse|animate-ping|\brounded-full\b(?=.*\b(?:size-[12](?:\.5)?|[hw]-(?:1|1\.5|2|2\.5))\b)")), ("U11 emoji", EMOJI), ("U15 chart scaffolding", re.compile(r"feDropShadow|drop-shadow\(|shadowBlur|shadowColor|\bminor\s*:\s*\{|border\s*:\s*\{[^}]*width\s*:\s*(?:[2-9]|1\.[5-9])|grid\s*:\s*\{[^}]*lineWidth\s*:\s*(?:[2-9]|1\.[5-9])")), ("U16 legend", re.compile(r"legend\s*:\s*\{[^}]*display\s*:\s*true|<Legend\b")), ("unslop 13 em dash", re.compile(r"—|—|—|\—")), ] SPACING_UTILITY = re.compile(r"(?<![\w-])-?(?:[mp][trblxyse]?|gap(?:-[xy])?|space-[xy])-\[(\d+)px\]") SPACING_PROPERTY = re.compile(r"\b(?:margin|padding)(?:-(?:top|right|bottom|left))?\s*:\s*(\d+)px\s*(?:[;}\"']|$)|\bgap\s*:\s*(\d+)px") def count_off_scale(line): values = [m.group(1) for m in SPACING_UTILITY.finditer(line)] for m in SPACING_PROPERTY.finditer(line): values.append(m.group(1) or m.group(2)) return sum(1 for v in values if int(v) % 4 != 0 and int(v) != 2) def regex_counter(regex): return lambda line: len(regex.findall(line)) RULES = [(name, regex_counter(regex)) for name, regex in RULES] SURFACE_RULES = [ ("U17 gradient or glow", regex_counter(re.compile( r"\bbg-(?:gradient|linear|radial|conic)-to?-?|(?:linear|radial|conic)-gradient\(|\bbg-clip-text\b|background-clip:\s*text" r"|\bblur-(?:2xl|3xl)\b|\bshadow-\[0_0_|\bshadow-[a-z]+-\d{2,3}(?:/\d+)?\b|box-shadow:[^;]*\b0\s+0\s+\d+px" ))), ("U18 off-scale spacing", count_off_scale), ("U19 extra-heavy weight", regex_counter(re.compile( r"\bfont-(?:extrabold|black)\b|font-?[wW]eight\W{0,3}[89]00\b|\bfont-\[[89]00\]" ))), ("U20 motion", regex_counter(re.compile( r"\btransition-all\b|transition:\s*all\b|\bhover:scale-|\banimate-bounce\b" ))), ] def iter_files(targets): for target in targets: if os.path.isfile(target): yield target continue for root, dirs, files in os.walk(target): dirs[:] = [d for d in dirs if d not in SKIP_DIRS] for name in files: if os.path.splitext(name)[1].lower() in EXTENSIONS: yield os.path.join(root, name) def is_code_comment(line): stripped = line.lstrip() return stripped.startswith(("//", "/*", "*", "#")) def main(): args = sys.argv[1:] surface = "--surface" in args targets = [a for a in args if a != "--surface"] if not targets: print("Usage: python3 count_tells.py [--surface] <file-or-folder> [...]", file=sys.stderr) sys.exit(2) missing = [t for t in targets if not os.path.exists(t)] if missing: print("Not found: " + ", ".join(missing), file=sys.stderr) sys.exit(2) rules = RULES + SURFACE_RULES if surface else RULES results = {name: {"count": 0, "examples": []} for name, _ in rules} for path in iter_files(targets): try: with open(path, encoding="utf-8", errors="replace") as f: lines = f.readlines() except OSError as e: print("Skipped {}: {}".format(path, e), file=sys.stderr) continue for lineno, line in enumerate(lines, 1): if is_code_comment(line): continue for name, counter in rules: hits = counter(line) if hits: entry = results[name] entry["count"] += hits if len(entry["examples"]) < MAX_EXAMPLES: entry["examples"].append("{}:{}".format(path, lineno)) results["total"] = sum(r["count"] for r in results.values()) print(json.dumps(results, indent=2, ensure_ascii=False)) if __name__ == "__main__": main()skills/unslop-ui/scripts/load_unslop.py1.9 KB78ff5762d4e7upstream ↗
#!/usr/bin/env python3 """Print the pattern list of the newest installed /pstack:unslop skill. Called through dynamic context injection when /unslop-ui is invoked, so it must always exit 0: a non-zero exit would abort the whole skill. """ import glob import os import re # Where Claude Code, Cursor, Codex and `npx skills` put plugin and skill folders. SEARCH = [ "~/.claude/plugins/cache/*/pstack/*/skills/unslop/SKILL.md", "~/.cursor/plugins/**/pstack/**/skills/unslop/SKILL.md", "~/.claude/skills/unslop/SKILL.md", "~/.cursor/skills/unslop/SKILL.md", "~/.agents/skills/unslop/SKILL.md", "~/.codex/skills/unslop/SKILL.md", ".claude/skills/unslop/SKILL.md", ".cursor/skills/unslop/SKILL.md", ".agents/skills/unslop/SKILL.md", ] FALLBACK = ( "/pstack:unslop is not installed (https://github.com/cursor/plugins/tree/main/pstack). " "Apply at least: no AI vocabulary (delve, seamless, crucial, enhance, showcase), " "no em dashes, sentence-case headings, no decorative emojis, say what it does " "instead of how it feels, prefer the plain word." ) def version_key(path): # Compare paths by their numeric parts so 0.15.20 sorts after 0.15.9. return [int(p) for p in re.findall(r"\d+", path)] def find_unslop(): for pattern in SEARCH: paths = glob.glob(os.path.expanduser(pattern), recursive=True) if paths: return max(paths, key=version_key) return None def main(): path = find_unslop() if not path: print(FALLBACK) return try: with open(path, encoding="utf-8") as f: text = f.read() except OSError: print(FALLBACK) return # Drop the frontmatter and the skill's own intro; keep the numbered rules. start = text.find("## Patterns to detect and fix") print(text[start:] if start != -1 else re.sub(r"\A---.*?---\s*", "", text, flags=re.S)) if __name__ == "__main__": main()skills/unslop-ui/references/examples.md4.0 KBcc288c117ee2upstream ↗
# Before and after ## Contents - Hero with eyebrow (U1, U3, U8) - Numbered feature section (U2, U4) - Card that explains itself (U4, U5) - Status line (U6, U10) - KPI tile (U11, U14) - Chart header (U12, U13) - Chart scaffolding and legend (U15, U16) - Form field (U7) ## Hero with eyebrow (U1, U3, U8) Before: ```html <p class="text-xs uppercase tracking-widest text-indigo-500">Introducing Ledger</p> <h1>Finance. Simplified. Finally.</h1> <p>The all-in-one platform that helps modern teams seamlessly manage their money — without the hassle.</p> ``` After: ```html <h1>Ledger tracks every company card in one place</h1> <p>Receipts match to transactions automatically.</p> ``` The eyebrow goes (U1). The staccato slogan becomes a sentence that says what the product does (U8). The subtitle keeps one concrete fact and loses "seamlessly", "all-in-one" and the em dash (unslop 7, 13). ## Numbered feature section (U2, U4) Before: ```jsx <span className="font-mono text-sm">01 //</span> <h3>Smart sync</h3> <p>Our smart sync feature automatically keeps your files in sync across all of your devices.</p> ``` After: ```jsx <h3>Sync across devices</h3> <p>Edits on your phone show up on your laptop within seconds.</p> ``` The order of features isn't real, so the number goes (U2). The description repeated the title, so it now states a fact the title doesn't (U4). ## Card that explains itself (U4, U5) Before: ```jsx <Card> <CardTitle>Recent activity</CardTitle> <CardDescription>This card shows your most recent activity across the workspace (updates in real time).</CardDescription> <ActivityList /> </Card> ``` After: ```jsx <Card> <CardTitle>Recent activity</CardTitle> <ActivityList /> </Card> ``` ## Status line (U6, U10) Before: ```jsx <div className="flex items-center gap-2 text-xs"> <span className="h-2 w-2 rounded-full bg-green-500 animate-pulse" /> Live · 3 agents · Synced · v2.4.1 · Updated just now </div> ``` After, when nothing in the app tracks a live connection: ```jsx <p className="text-xs">3 agents</p> ``` If the dot is bound to a real websocket state, keep the dot with an `aria-label` and drop the word "Live". ## KPI tile (U11, U14) Before: ```jsx <Tile> <span>💰 Total revenue</span> <strong>$48,200</strong> <span className="text-green-600">▲ 12% up</span> <p>Revenue grew 12% compared to last month, showing strong momentum.</p> </Tile> ``` After: ```jsx <Tile> <span>Revenue</span> <strong>$48,200</strong> <span className="text-green-600">▲ 12% vs last month</span> </Tile> ``` ## Chart header (U12, U13) Before: ```js title: { text: 'Line chart of weekly active users' }, subtitle: { text: 'Each point represents one week. Hover over a point to see the exact value.' }, legend: { display: true }, // single series ``` After: ```js title: { text: 'Weekly active users' }, legend: { display: false }, ``` ## Chart scaffolding and legend (U15, U16) Before: ```js datasets: [{ label: 'This year', data: thisYear }, { label: 'Last year', data: lastYear }], plugins: { legend: { display: true, position: 'bottom' } }, scales: { y: { grid: { color: '#9ca3af', lineWidth: 2 }, border: { display: true, width: 2 }, ticks: { stepSize: 25 } }, }, ``` After: ```js datasets: [{ label: 'This year', data: thisYear }, { label: 'Last year', data: lastYear }], plugins: { legend: { display: false }, // Name each line at its last point instead of in a legend. datalabels: { display: (ctx) => ctx.dataIndex === ctx.dataset.data.length - 1, formatter: (v, ctx) => `${ctx.dataset.label} ${v}` }, }, scales: { y: { grid: { color: '#eeeeee', lineWidth: 1 }, border: { display: false } }, }, ``` Same chart type, data and series colors. The gridlines become hairlines, the axis border goes, and the legend becomes two labels at the line ends. ## Form field (U7) Before: ```html <label>Email address</label> <input placeholder="Enter your email address" /> <small>We'll use this email address to contact you.</small> ``` After: ```html <label for="email">Email</label> <input id="email" type="email" /> ```skills/unslop-ui/references/tokens.md3.0 KB798e470449bbupstream ↗
# Surface values Fix targets for U17 to U20. When the project already has a token system (Tailwind theme, CSS variables, a design-system package), use its values and only fix where the code bypasses them. These numbers are the fallback, not a house style. ## Contents - Spacing - Color - Type - Radius and depth - Motion ## Spacing Scale: 4, 8, 12, 16, 20, 24, 32, 40, 48, 64. | Where | Value | |---|---| | Inside a control | 4 to 12 | | Between rows in a list | 2 to 8 | | Between groups (a label and its list, two cards) | 12 to 24 | | Between sections | 32 to 64 | | Card padding | 16 to 24, one value for sibling cards | | Row height | 32 compact, 36 default, 44 touch | Space inside a group is smaller than space between groups. An off-scale value moves to the nearest step (`mt-[13px]` becomes `mt-3`). A 2px nudge inside a small control, or an odd value that exactly centers something, can stay. ## Color No hex ramp is prescribed. Keep the project's palette and fix how it is used. - Surfaces, borders and text come from one neutral family. Three text roles: primary, secondary, muted. Five near-identical tints of one hue become three. - One accent, on the primary action, the selection or the one number that matters. - Borders are hairlines: the text color at 6 to 10% opacity. - Text contrast is at least 4.5:1 on its surface, including text on the accent and muted text. - Semantic colors (green good, red error) carry meaning only, and sit inside the palette instead of glowing. - Gradients are allowed only as a tone shift inside one neutral. A gradient from one hue to another, gradient text, colored glows and blurred color blobs go. ## Type | Use | Size | Weight | |---|---|---| | Meta, counts | 12 | 400 | | Captions, secondary | 13 to 14 | 400 | | Body, navigation | 14 to 15 | 400 to 500 | | KPI figure | 28 to 32 | 500, `tabular-nums` | | Page title | 24 to 32 | 500 to 600 | Weights 400 to 600. Hierarchy comes from size and color, not from 800 or 900. Letter spacing is 0 under 16px. Negative tracking is for display text only. Numbers use one format on the screen. ## Radius and depth | Element | Radius | |---|---| | Tag, keycap | 4 to 6 | | Input, button, row | 8 to 10 | | Card | 12 to 16 | | Panel | 16 to 20 | Nested radius: inner = outer minus the padding between them, never below 4. Depth: a surface step plus a hairline. Where a shadow earns its place, keep it neutral and small: `0 1px 2px rgb(0 0 0 / 0.05)`, or `0 8px 24px rgb(0 0 0 / 0.06)` for something floating. ## Motion | Use | Duration | |---|---| | Hover, press, toggle | 120 to 180ms | | Menu, popover, tooltip | 160 to 220ms | | Entrance, layout change | 300 to 400ms | One easing curve for the screen: `cubic-bezier(0.22, 1, 0.36, 1)` or the framework's ease-out. Transition named properties (`transition-colors`, `transition-[opacity,transform]`), never `all`. Never animate width, height, top, left or margins. A press scales to 0.97 to 0.98. A card does not scale on hover. Keep motion that explains something (a menu rising a few pixels, a number tweening) and drop loops and bounces.skills/unslop-ui/agents/openai.yaml215 B03ae77486bdbupstream ↗
interface: display_name: "Unslop UI" short_description: "Cut AI tells from interface copy, charts and surface" default_prompt: "Run unslop-ui on the files I changed" policy: allow_implicit_invocation: falseREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/felipebasurto-unslop-ui-skills-unslop-ui.md