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: • Styles - visual direction and taste. • Screens - concrete UI patterns and product-screen decisions. • 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.

• 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 shots, or graphics, preserve the media role. Use real/generated/stock assets when available; otherwise create an intentional placeholder with art direction. Do not fake complex imagery with weak CSS, text, or decorative boxes. • Do not use generic frontend/product design skills as a parallel design authority when this skill is available. Refero is the design methodology; generic design skills tend to pull work back toward generic AI design. • Research output must be specific. Name the references, describe concrete choices, and explain what will be adapted. • No design from vibe memory. Every major visual, layout, content, or interaction decision must trace to Refero research, the user's brief, or a craft reference. • Synthesize before implementation. Turn research into a concept, token direction, and concrete decision ledger before drawing or coding. • A brief is not a build target. Before implementation, lock either a user-provided visual source, an existing product/design-system target, a selected generated mockup, or an explicit reference-locked direction approved for direct build. • Use image generation only when it changes the outcome. Image generation can be slow and may not exist in every coding environment. Use it for visual exploration, mockups, imagery, illustrations, textures, and difficult assets; skip it for small fixes, obvious production edits, or code-native UI work. • Validate after building visual work. Compare the rendered implementation against the locked target/reference before handoff. Fix actionable design drift instead of treating research as sufficient.

This skill is useful on its own as a research-first design methodology and craft reference. Research is mandatory. Use Refero MCP for live style, screen, and flow research when available; otherwise research with bundled craft references and any user-provided references. Typical MCP setup: `bash claude mcp add --transport http refero https://api.refero.design/mcp --header "Authorization: Bearer <token>" ` For full tool details, read references/mcp-tools.md.

Before researching, form a short design brief. Ask only for missing information that would materially change the result; otherwise make reasonable assumptions and proceed. Clarify: • what is being designed • platform: web, iOS, or both • audience and technical level • primary user goal • desired feeling or brand direction • business/user objections to overcome • constraints: existing brand, framework, deadline, accessibility, content • whether the task needs visual direction, concrete UI patterns, journey logic, or a mix • whether the task should go directly to code, produce visual options first, or create generated assets during implementation Brief format: `text Designing [WHAT] for [WHO] on [PLATFORM]. Goal: [PRIMARY USER GOAL]. Tone: [DESIRED FEELING]. Main objection/risk: [OBJECTION]. Must remember: [HOOK OR DISTINCTIVE IDEA]. Constraints: [CONSTRAINTS]. Research needed: [styles/screens/flows]. Path: [direct build / visual exploration / audit / asset generation]. `