research-design

Analyze UI references to collect screen and flow evidence for design decisions.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill research-design-conradmaker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-design
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/research-design
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill research-design-conradmaker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill enables structured, evidence-based research workflows for UI screens and flows. It collects real-service screen and flow references, extracts actionable patterns, and organizes findings into design decisions that can be handed off to downstream owners, reducing context loss and enabling repeatable validation.

Core Features & Use Cases

  • Discovery-driven reference collection: aggregate real-world screens and flows to ground design decisions in actual usage.
  • Pattern extraction and comparison: identify recurring layout and interaction patterns across references and contrast best-in-class examples.
  • Handoff-ready design decisions: translate findings into owner-specific artifacts (prd.md, artifacts.md, design prompts) for downstream teams like ds-ui-patterns, ds-visual-design, ds-typography, ds-product-ux, and fe-*.
  • Guidance and governance: provide an evidence-led framework that can be invoked for screen/flow research, pattern extraction, and reference-driven synthesis.

Quick Start

Initiate a Refero MCP research session to collect screen and flow references and produce an evidence-based handoff for downstream owners.

Frequently Asked Questions about research-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect UI references to inform product design decisions?

To collect UI references for product design decisions, initiate a research session to aggregate real-world screens and flows. This grounds your design choices in actual usage evidence rather than assumptions.

What is evidence-based UI research and how does it work?

Evidence-based UI research analyzes real-service screen and flow references to extract actionable patterns. It translates findings into structured artifacts like pattern tables and steal lists for downstream teams.

How do I extract interaction patterns from multiple screen references?

To extract interaction patterns from screen references, analyze collected UI flows to identify recurring layouts. The process contrasts best-in-class examples and compiles them into a structured pattern table.

Can I use this approach for both web and mobile platform research?

Yes, you can use this UI research approach for both web and mobile platforms. It applies to research workflows across product screens, flows, and patterns regardless of the target platform.

How do I hand off UI research findings to downstream design teams?

To hand off UI research findings to design teams, translate the evidence into owner-specific artifacts like prd.md, artifacts.md, and design prompts. This ensures structured delivery to downstream owners.

What's the best way to organize UI flow analysis for downstream owners?

The best way to organize UI flow analysis is structuring outputs into a pattern table, steal list, and handoff recommendations. This enforces evidence-based translation into owner-ready design artifacts.