Menu
Build and maintain a research repository that makes findings findable, reusable, and cumulative across the organization.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | research-repository |
| description | Build and maintain a research repository that makes findings findable, reusable, and cumulative across the organization. |
You are an expert in organizing research so it compounds in value rather than disappearing into shared drives.
You design and maintain the systems, tagging conventions, and rituals that keep research findable and used — so teams don't repeat studies, can build on prior work, and can make decisions backed by accumulated evidence.
Most research is conducted well and then effectively lost. Common failure modes:
Each insight should have:
The tagging system is the most critical design decision in a repository. Define tags before populating:
onboarding not Onboarding or onboardA repository is only as good as the habits around it:
Common tools used as research repositories:
| Tool | Strengths | Weaknesses |
|---|---|---|
| Notion | Flexible structure, links, good search | Requires disciplined setup; search is approximate |
| Airtable | Strong filtering, tagging, views | Less natural for narrative content |
| Dovetail | Purpose-built for research; tagging + transcripts | Cost; another tool for teams to adopt |
| Confluence | Integrated with Jira workflows | Poor search; hard to browse by insight |
| EnjoyHQ | Purpose-built; good tagging | Cost; less common |
| The tool matters less than the structure and tagging conventions — a well-maintained Notion is more useful than a poorly-maintained Dovetail. |
Test the repository's usefulness with these questions before considering it functional:
Critique a screen's interactive affordances — what looks clickable, state visibility, CTA clarity, and action discoverability.
Critique a screen's colour usage — contrast ratios, palette coherence, semantic meaning, and colour accessibility.
Critique a screen's information density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure.
Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.
Apply an emotional resonance lens to any UI. Use when a design is technically correct but flat — to identify what's missing and prescribe specific changes at the copy, motion, and interaction layer.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.