Retenta has not executed this skill.
Evidence record · captured 2026-10-11
Frontend Design
Prompts the agent to act as a design lead with a distinct point of view: identify the subject, audience and primary job of the UI first, then make deliberate, subject-specific choices of palette, typography, layout and hero treatment instead of templated defaults (explicitly avoiding stock patterns such as the big-number-plus-gradient hero).
Editorial assessment
This is a source-only assessment. It does not claim runtime or security testing.
What it does
Turns the agent into a design lead that writes a design plan, then challenges it before coding. Its distinctive move is a named list of the visual defaults generated pages cluster around, to keep free choices off them.
Best for
- Building a new landing page or product UI where the brief leaves visual direction open
- Reworking an existing page that reads as a generic template
- Writing interface copy such as button labels, empty states and error messages alongside the layout
Strengths in the source
- Requires a written token plan first (4 to 6 named hex colors, typeface roles, an ASCII wireframe, principles), then a review of that plan against the brief before any code is written.
- Lists five concrete clusters of generated-looking design, down to specific hex values and chrome such as ALL-CAPS eyebrows and arrow-suffixed links, so the agent has checkable things to avoid.
- States that the brief's own words always win, including when the client asks for one of the listed default looks.
- Sets a quiet quality floor: mobile responsive, visible keyboard focus, reduced motion respected, plus self-critique from screenshots where the environment allows.
Limitations
- Pure prose guidance with no bundled scripts, linters or checks, so adherence depends entirely on the agent's judgment.
- Screenshot-based self-critique only happens in environments that can render and capture the page.
- Taste-driven by design: the 'avoid these defaults' list reflects a point of view and may conflict with an established brand system that uses them.
When not to use it
- Work inside an existing design system with fixed tokens and components, where distinctiveness is not the goal
- Backend, data or logic changes that do not touch visual design
Reviewed by Retenta editorial on 2026-10-11; scope: source only.
Files included in this review
skills/frontend-design/SKILL.md
Evidence and boundaries
The skill folder bundles no executable scripts. Retenta has not run a security scan.
- Pinned publisher source
- skills/frontend-design/SKILL.md
- Revision
- dbd4588f9e1033efb41dad4bef2f7947c8993d44
- License evidence
- Apache-2.0Retenta preserves the license text captured with this immutable upstream snapshot; no independent legal or security review is claimed.
- Last source change
- 2026-09-03
- Independent verification
- Published by Anthropic, which does not own the product this skill covers. Not independently verified.
- Upstream repository
- Open publisher repository
Compatibility
Claude Code (plugin marketplace)
documentedNamed in the upstream skill or repository documentation; not tested by Retenta.
Claude.ai
documentedNamed in the upstream skill or repository documentation; not tested by Retenta.
Claude API (Skills API)
documentedNamed in the upstream skill or repository documentation; not tested by Retenta.
Requirements and access
- None required
Referenced tools
No named tool is required by the reviewed SKILL.md.
Install from the source
Clones the current default branch, which may be newer than the reviewed revision dbd4588. The destination shown is Claude Code's personal skills folder; other agents read the same folder from their own skills directory.
View the SKILL.md at its source Verify the publisher's install documentationInstall the full skill folder
git clone --depth 1 https://github.com/anthropics/skills.git
cp -R skills/skills/frontend-design ~/.claude/skills/frontend-designThyme RAG Capsules
Make this skill’s state durable, governed, and portable.
A Retenta capsule lets agents recall prior work, append provenance-stamped progress, and carry the memory to the next run.