agentleFS
Sign inStart free
AndyTechnologiesAndyTechnologies/my-own-skills/skills/ui-design/SKILL.md

ui-design

Skill0 starsChanged 39 days agoApache-2.0View on GitHub

Trigger: UI/UX design, interface, components, design system, dark luxury, dark premium, elegant dark theme, color, typography, layout, accessibility. Produce concise UI decisions and record them in the generated design artifact.

59 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use harness-design, graphic-design and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VictoriakaeySkill

    harness-design

    Use when designing or improving the action space, observation format, tool boundaries, and evaluation signals of an LLM agent. Covers the five layers of harness design: what tools the agent has, what it sees after acting, how each tool is scoped, how behavior is evaluated, and how to iterate when the agent misbehaves. Prevents the most common harness failures — agents that pick wrong tools, ignore critical information, or loop without progress.

    Also in 3 projects that use this

  • travisjneumanSkill

    graphic-design

    Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.

    Also in 3 projects that use this

  • soilmassSkill

    typography

    Typography and kinetic text animations including character reveals, typewriter effects, scramble/decode, wave motion, and animated gradients. Use when creating text reveals, headline animations, number counters, or any text-based motion effects.

    Also in 3 projects that use this

  • OpenAISkill

    auth

    Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication.

    Also in 3 projects that use this

  • VercelSkill

    react

    React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.

    Also in 4 projects that use this

  • 3stoneBrotherSkill

    code-audit

    Professional code security audit skill covering 55+ vulnerability types. Enhanced with WooYun 88,636 real-world vulnerability cases (2010-2016). This skill should be used when performing security audits, vulnerability scanning, penetration testing preparation, or code review for security issues. Supports 9 languages: Java, Python, Go, PHP, JavaScript/Node.js, C/C++, .NET/C#, Ruby, Rust. Includes 143 mandatory detection items across all languages with language-specific checklists. Covers SQL injection, XSS, RCE, deserialization, SSRF, JNDI injection, JDBC protocol injection, authentication bypass, business logic flaws, race conditions, and modern security domains (LLM, Serverless, Android). WooYun integration adds: statistical-driven parameter priority, bypass techniques library, logic vulnerability patterns, and real-case references. v1.0: Initial public release with Docker deployment verification framework.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never invent an unverifiable decision.

    line 20
  2. Distinctive:

    Keep decisions concise: one line per decision with a 1-line rationale (design artifact budget is under 800 words).

    line 21
  3. Distinctive:

    If the change touches UI/UX, run the checklist in priority order.

    line 51
  4. Very specific:

    Write the ## UI Decisions section into the generated design artifact before persisting it.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 50 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Activation Contract

Load when a design task covers UI/UX: new pages, components, design systems, color/typography/layout choices, or interface accessibility. Applies to the SDD sdd-design phase and direct design work. Skip when the change is backend, API, or infrastructure only.

Hard Rules

  • Record every UI decision INSIDE the generated design artifact (design.md) in a ## UI Decisions section — never in loose repo files or sidecars.
  • Detect the stack from the project (package.json, pubspec.yaml, *.xcodeproj, etc.); never assume one.
  • Recommend semantics, not raw values: color/type/spacing tokens; no raw hex, no fixed px containers, no placeholder-only labels.
  • Hierarchy: accessibility and touch rule before visual polish. Run the checklist in priority order.
  • Never invent an unverifiable decision; if nothing fits, state the fallback explicitly.
  • Keep decisions concise: one line per decision with a 1-line rationale (design artifact budget is under 800 words).

Decision Gates — UI Priority Checklist

#Check (must hold)
1Accessibility: contrast >= 4.5:1; visible focus rings; aria labels for icon-only controls; keyboard nav
2Touch & interaction: targets >= 44x44px; 8px+ spacing; loading feedback; no 0ms state changes
3Performance: lazy images (WebP/AVIF); space reserved (CLS < 0.1)
4Style consistency: match product type; consistent patterns; SVG icons, not emoji
5Layout responsive: mobile-first breakpoints; no horizontal scroll; no fixed px containers
6Typography & color: base 16px; line-height 1.5; semantic tokens; body >= 12px
7Motion: context-aware timing; respect reduced-motion; avoid width/height animation
8Forms & feedback: visible labels; errors near field; helper text; progressive disclosure
9Navigation: predictable back; bottom nav <= 5; deep linking
10Charts & data: legends, tooltips; never color-only meaning

Style Direction — Gentle AI

Activate when the request targets the Gentle-AI / Gentleman Programming ecosystem or asks for "gentle-ai style", "estilo gentle", "diseño gentle", or a dark-first zinc/magenta or Rose Pine UI — never design it from memory alone.

  • Identity: dark-first; deep zinc backgrounds (#09090b web, #191724 TUI); single magenta accent #ea1889 (web) / #c4a7e7 lavender (TUI); Inter web typography; Rose Pine palette in terminal; subtle borders, no hard lines.
  • Defaults: background #09090b; accent #ea1889; font Inter; type web app/landing.
  • Non-negotiables: ONE chromatic accent · borders #ffffff12, never pure hard lines · rounded-lg (8px) controls, rounded-2xl (16px) cards · spacing in 4px multiples · TUI text contrast >= 4.5:1 (never #6e6a86/#31748f for normal text) · dark-first.
  • Page structure: fixed nav (bg-black/80 backdrop-blur-xl border-b), max-w-6xl container, transition-colors on interactives.
  • Stack: React — Tailwind for layout only, colors via @theme tokens or style; TUI — Rose Pine hexes directly.
  • Full tokens, palettes, and rules: read ../gentle-ui/SKILL.md.

Execution Steps

  1. If the change touches UI/UX, run the checklist in priority order; mark each item decided or explicitly out of scope.
  2. Record chosen palette, type scale, spacing, tokens, and interaction patterns — one line each, with rationale.
  3. Write the ## UI Decisions section into the generated design artifact before persisting it.
  4. Report unresolved UI questions as risks in the phase result.

Output Contract

Return the UI Decisions section content and any unresolved UI risks; keep product choices separate from technical decisions.

References

  • ../_shared/sdd-phase-common.md — phase retrieval/persistence and return envelope.
  • ../sdd-design/SKILL.md — design phase contract this skill augments.
  • ../gentle-ui/SKILL.md — Gentle AI direction: web (zinc/magenta) and TUI (Rose Pine) tokens, structure, general rules.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free