Refero design: research-first UI design methodology
Ground every design in real references — styles, screens, flows — with reference locks, decision ledgers and anti-AI-slop quality gates
- What
- Ground every design in real references — styles, screens, flows — with reference locks, decision ledgers and anti-AI-slop quality gates
- Cost
- Free
- Needs
- a design task to work on — for the full workflow, a Refero account with the Refero MCP server configured (the skill also works standalone with its bundled craft references)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @referodesign's primary design skill: a research-first methodology for UI, product and web design, built to give agents taste and product evidence instead of generic model knowledge. Three research layers: styles (visual direction), screens (concrete UI patterns), flows (multi-step journey logic). Non-negotiables: research before design work, never copy one reference, never average references into a safe middle (choose one dominant direction and preserve its sharp traits), preserve token and imagery roles, synthesize before implementing, and lock the direction in a reference lock plus a decision ledger before coding. Includes tool routing (refero_search_styles / refero_search_screens / refero_search_flows and their get-* variants), four workflow routes (direct build, visual exploration, audit, asset generation), bundled craft references (typography, color, motion, icons, copywriting, craft details) and an anti-AI-slop quality gate (no generic hero → features → pricing → FAQ, no default indigo, no decorative serif word swaps, at least one memorable detail, every major decision traceable to a reference, constraint or craft rule). Honest caveats: the full workflow routes through Refero's own MCP service — a free account/sign-in is needed for live style/screen/flow research; the skill still works standalone with its bundled craft references and user-provided ones; this is a long, opinionated methodology, not a quick fix. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a design task to work on — for the full workflow, a Refero account with the Refero MCP server configured (the skill also works standalone with its bundled craft references) Install "Refero design: research-first UI design methodology" for me. It gives my agent @referodesign's research-first design methodology: research styles, screens and flows before designing; synthesize into a locked reference direction with a decision ledger; preserve token and imagery roles; then build with bundled craft knowledge (typography, color, motion, icons, copywriting, accessibility) and run the anti-AI-slop quality gate — with four workflow routes (direct build, visual exploration, audit, asset generation). MIT-licensed. Repository: https://github.com/referodesign/refero_skill/blob/main/skills/refero-design/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "refero-design". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. bring the design brief and any brand constraints; sign in to Refero and add its MCP server for live research, or rely on the bundled craft references). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.