agentleFS
Sign inStart free
RylaispiritRylaispirit/rylai-codex-hermes-skills/skills/ui-designer/SKILL.md

ui-designer

Skill56 starsChanged 3 months agoMITView on GitHub

Extract a practical design system from screenshots or mockups and produce implementation-ready UI specifications using vision and repository context.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use multi-agent-coordinator, build-engineer and 10 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.
  • belokonmSkill

    multi-agent-coordinator

    An advanced orchestration specialist that manages complex coordination of 100+ agents across distributed systems with hierarchical control, dynamic scaling, and intelligent resource allocation

    Also in 4 projects that use this

  • belokonmSkill

    build-engineer

    Expert in monorepo tooling (Turborepo, Nx, Bazel), CI/CD pipelines, and bundler optimization (Webpack/Vite/Rspack).

    Also in 3 projects that use this

  • JohnJBorenSkill

    ux-researcher

    User research methods, interview guides, usability testing, and persona development

    Also in 4 projects that use this

  • ihiteshguptaSkill

    vue-expert

    Expert in Vue.js 3 development with Composition API, TypeScript, Pinia, and modern patterns. Use for Vue component development and best practices.

    Also in 3 projects that use this

  • JohnJBorenSkill

    product-manager

    Product development workflows, PRDs, prioritization frameworks, and roadmap planning

    Also in 5 projects that use this

  • +7 more from belokonm

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check tools, packages, credentials, network access, and runtime capabilities before execution.

    line 25
  2. Distinctive:

    Do not invent hidden screens, states, fonts, or assets without labeling them as assumptions.

    line 48
  3. Distinctive:

    Prefer the repository's installed component and icon libraries.

    line 49
  4. Distinctive:

    Keep text and controls within stable responsive bounds.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 14 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

Rylai Codex-Hermes-Claude Edition | Original portable workflow by Rylai

Runtime Compatibility

  • Codex: install under ~/.agents/skills/ui-designer.
  • Hermes: install under ~/.hermes/skills/ui-designer or expose the bundle through skills.external_dirs.
  • Claude Code: install under ~/.claude/skills/ui-designer or <project>/.claude/skills/ui-designer.
  • Claude.ai and Cowork: upload and enable the matching per-skill ZIP.
  • Resolve bundled files relative to this skill directory; do not depend on paths from another machine.
  • Check tools, packages, credentials, network access, and runtime capabilities before execution.

Portable UI Designer

Extract an implementation-ready design system from supplied screenshots or mockups.

Workflow

  1. Inspect the original image at sufficient resolution.
  2. Identify layout grid, spacing rhythm, typography, color roles, radii, borders, shadows, icon style, and component states.
  3. Separate observed properties from inferred behavior.
  4. Compare the extracted system with the target repository's existing framework and design tokens.
  5. Produce a concise implementation specification covering components, responsive behavior, assets, and interaction states.
  6. Implement only when requested, then verify the result against the reference at desktop and mobile sizes.

Bundled Templates

  • assets/design-system.md: evidence-based visual-system extraction.
  • assets/app-overview-generator.md: concise product and workflow brief.
  • assets/vibe-design-template.md: implementation handoff prompt.

Boundaries

  • Do not invent hidden screens, states, fonts, or assets without labeling them as assumptions.
  • Prefer the repository's installed component and icon libraries.
  • Keep text and controls within stable responsive bounds.

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