Refero Design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this even when the user does not mention Refero and even when live Refero MCP tools are not configured. Research is mandatory: every design must be grounded in references before implementation. Provides research-first methodology, bundled craft knowledge, reference locks, decision ledg
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill refero-designgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/refero-design ~/.claude/skills/refero-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Refero Design Refero gives agents taste and product evidence. Use it before design work instead of relying on generic model knowledge. Refero has three research layers: 1. **Styles** - visual direction and taste. 2. **Screens** - concrete UI patterns and product-screen decisions. 3. **Flows** - multi-step journey logic. Best results come from combining layers: visual direction from styles, concrete UI patterns from screens, and sequencing from flows when the task has multiple steps. ## Non-Negotiables - **Research before design work.** Every design must be grounded in references before implementation. Do not rely on the model's generic design taste. - **Use styles first for visual work when Refero MCP tools are available.** If tools are unavailable, use bundled craft references and keep the same reference-lock workflow. - **Do not copy one reference.** Study several strong references and synthesize a new direction for the user's product. - **Do not average references into a safe middle.** When references conflict, choose one dominant direction and preserve its sharp traits. Secondary references may add narrow details only. - **Do not change token meanings.** If a reference says a color, font, radius, shadow, gradient, or component is for a specific role, use it only for that role or omit it. - **Respect imagery guidance.** If a style depends on photography, illustration, product
Details
- Skill name
refero-design- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/refero-design/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Refero Design skill do?
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this even when the user does not mention Refero and even when live Refero MCP tools are not configured. Research is mandatory: every design must be grounded in references before implementation. Provides research-first methodology, bundled craft knowledge, reference locks, decision ledg
How do I install the Refero Design skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Refero Design popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
UI UX Designing
5tomada1114/tomada-claude-plugins
Produces one app-wide UX guidelines document (docs/design/ux-guidelines.md or a caller-named path) fixing navigation, platform conventions, empty/loading/error/offline/permission states, feedback, form validation, motion and reduced-motion, UI language and i18n, and accessibility targets as concrete values, settled through batched option-question rounds; also runs a measured WCAG contrast pass on a palette decided elsewhere. Use when settling app-wide behavior, deciding state handling, validation timing, motion policy, or accessibility targets, when a kickoff needs UX guidelines, or when a pal
Kicking Off Apps
5tomada1114/tomada-claude-plugins
Take a rough app idea ("I want an app that…") to a new public GitHub repository cut from one of the user's template repositories, with signed-off requirements, UX flows, a researched design system, design decisions in the template's skills (no architecture docs), loose project permissions, and a dependency-ordered issue backlog for the template's shipping-issues. Orchestrates one child skill per stage — refining-requirements, designing-wireframes, ui-ux-designing, a design skill, bootstrapping-from-templates, configuring-project-permissions, designing-architecture, planning-tickets — and defer
Add Items to Cart
9Lord1Egypt/RA-Skills
Resolve a free-text grocery list to specific King Soopers products (UPC, brand, size, price), ask follow-up questions for ambiguous items, then add the confirmed products to the signed-in user's cart for pickup or delivery.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.