Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/rand/cc-polymath/elegant-designnpx skills add rand/cc-polymath --skill elegant-designgit clone --depth 1 https://github.com/rand/cc-polymathWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rand/cc-polymath/elegant-design)<a href="https://agentmods.dev/skills/rand/cc-polymath/elegant-design"><img src="https://agentmods.dev/badge/skills/rand/cc-polymath/elegant-design.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00043 | $0.02540 |
| Opus 5 | $0.00022 | $0.01270 |
| Sonnet 5 | $0.00009 | $0.00508 |
| Haiku 4.5 | $0.00004 | $0.00254 |
Grade A, and why
elegant-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Elegant Interfaces
Philosophy
World-class design is intentional, accessible, and delightful. Every element serves a purpose, every interaction feels natural, and the experience adapts gracefully across contexts.
Core Principles:
- Clarity over cleverness - Users should never wonder what to do next
- Consistency over novelty - Patterns should repeat predictably
- Performance over features - Fast, smooth interactions trump visual complexity
- Accessibility always - Design for all users from the start
- Progressive disclosure - Reveal complexity only when needed
- Intentional friction - Make destructive actions harder, constructive actions effortless
When to Use This Skill
Use this skill when:
- Building web applications with React/Next.js/similar frameworks
- Creating developer tools or technical interfaces
- Designing interfaces with chat, terminals, or code display
- Implementing real-time or streaming features
- Ensuring accessibility and responsive design
- Working with shadcn/ui, daisyUI, or HeroUI design systems
Design Process Workflow
Follow this workflow for optimal results:
1. Discovery & Planning (15-30 min)
Map User Experience:
# Create flow diagrams with Graphviz
cat > user-flow.dot << 'EOF'
digraph UserFlow {
Start -> "Observe State"
"Observe State" -> "Orient Understanding"
"Orient Understanding" -> "Decide Action"
"Decide Action" -> "Act Execute"
"Act Execute" -> "Observe State" [label="OODA loop"]
}
EOF
dot -Tpng user-flow.dot -o user-flow.png
OODA Loop Mapping: For each major user goal, optimize the cycle:
- Observe - What information does the user need?
- Orient - How do they make sense of it?
- Decide - What choices are available?
- Act - How do they execute?
Document States:
- Entry points (how users arrive)
- Core loops (repeated actions)
- Success states (goals achieved)
- Failure states (errors, recovery paths)
- Edge cases (empty, loading, error, extreme data)
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- foundation/colors-and-spacing.md 9.4 KB
- foundation/layout-patterns.md 5.5 KB
- foundation/typography.md 7.3 KB
- implementation/components-and-accessibility.md 5.6 KB
- implementation/performance.md 2.8 KB
- implementation/testing-and-qa.md 1.6 KB
- interactive/chat-and-messaging.md 7.7 KB
- interactive/diffs-and-logs.md 6.3 KB
- interactive/streaming-and-loading.md 7.8 KB
- interactive/terminals-and-code.md 8.5 KB
- README.md 3.8 KB
- reference/anti-patterns.md 4.0 KB
- reference/design-systems.md 2.4 KB
- reference/tools-and-libraries.md 3.3 KB
- SUMMARY.txt 2.0 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 303 lines · 43 tokens per session scan A 428926d13c35
elegant-design is a skill published in the GitHub repository rand/cc-polymath (140 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 2,540 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
frontend-design
创建具有高设计品质、可交付生产的前端界面。当用户要求构建 Web 组件、页面、海报或应用(如官网、落地页、仪表盘、React/Vue 组件、HTML/CSS 布局,或对任意 Web UI 进行样式/美化)时使用本技能。产出有创意、打磨到位且避免「AI 通用审美」的代码与界面设计。.
antfu-design
Use this when building interfaces with UnoCSS in any framework (React, Vue, Svelte, Solid, or plain HTML), from dense devtools panels to landing pages. Read core-design-read first to set the direction, then apply the token system plus the polish and anti-slop rules.
taste
Use when improving the visual taste, positioning, polish, trust, and conversion clarity of a website or product UI. Runs a category-first visual audit, applies a decisive design pass, and verifies the result with screenshots rather than subjective vibes.
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
modern-css
Proactively apply when creating design systems, component libraries, or any frontend application. Triggers on CSS Grid, Subgrid, Flexbox, Container Queries, :has(), @layer, @scope, CSS nesting, @property, @function, if(), oklch, color-mix, light-dark, relative color, @starting-style, scroll-driven animations, view…
obsidian-theme-dev
CSS/SCSS development patterns for Obsidian themes. Load when working with theme.css, SCSS variables, or CSS selectors.