frontend-design

When creating, restyling, or holistically reviewing web UI — set a coherent aesthetic direction, coordinate its design disciplines, and build or assess the…

Skill by bryan824

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/bryan824-frontend-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

When creating, restyling, or holistically reviewing web UI — set a coherent aesthetic direction, coordinate its design disciplines, and build or assess the result.

Use cases: design, frontend

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/frontend-design

What's inside

Skill name: frontend-design
Description: When creating, restyling, or holistically reviewing web UI — set a coherent aesthetic direction, coordinate its design disciplines, and build or assess the result.
License: MIT
Instructions: 32 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
REVIEW.md · references/

SKILL.md (first lines)

# Frontend Design

<!-- Modified for kirin-pi. -->

Give the interface a point of view; a collection of familiar components is not a
visual system. This skill owns aesthetic direction and orchestration, not every
domain rule.

- Name one aesthetic direction, then express a small visual thesis through type,
  color, rhythm, layout, and only the interactions that reinforce it.
- Establish foundations before polish. Coordinate available `frontend-accessibility`,
  `frontend-layout`, `frontend-writing`, `frontend-typography`, `frontend-color`,
  `frontend-motion`, and `frontend-polish` guidance. Missing siblings are not an
  installation requirement: assess those disciplines directly and state coverage
  limits. Apply an Apple-specific direction only when explicitly requested.
- Preserve existing tokens, components, density, and styling conventions unless
  redesign is explicit. Do not add arbitrary values to evade the system.
- Reject generic defaults: unconsidered SaaS-blue or purple gradients, centered
  card stacks, interchangeable hero-and-columns layouts, and decorative motion
  without a purpose.
- Stress real content before calling a design complete: long names, amounts,
  IDs, labels, localized strings, and narrow widths need deliberate wrapping,
  truncation, shrinking, or reflow.
- For implementation, build working project-native code rather than a mood
  board or placeholder. For a holistic review, follow
  [the shared review contract](references/REVIEW.md). Review-only requests stay
  read-only; implementation requests build the agreed scope.

Carry forward a named direction, a coherent small system, and code or evidence
that survives content stress.

From bryan824/kirin-pi, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Oct 1, 2026 (28 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/bryan824/kirin-pi
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from bryan824

Cite this page

frontend-design skill. Agent Mart. https://agentmart.dev/skills/bryan824-frontend-design (last updated 2026-10-24)