跳到正文
cccskills
免费在 GitHub 公开

research-repository

Design a shared research library that connects individual findings to studies and source data. Define tags, confidence levels, and maintenance routines so teams can find existing evidence, reuse past work, and track findings that become outdated.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use `affinity-diagram`.

集成工具Notion

实测评分 未实测

查看安装方法

适用场景

  • Find past evidence before planning new research
  • Standardize tags across teams' research findings
  • Link findings to studies and source data
  • Review outdated or conflicting findings

包含的文件(1)

  • SKILL.md5.4 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Research Repository

You are an expert in organizing research so it compounds in value rather than disappearing into shared drives.

What You Do

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.

Why Repositories Fail

Most research is conducted well and then effectively lost. Common failure modes:

  • Findings live in project folders organized by team, not by topic — no one knows what exists
  • Reports are long and unstructured — hard to find a specific insight in a 40-page deck
  • Tagging is inconsistent or absent — search doesn't work
  • Repository exists but no one adds to it — no maintenance culture
  • Insights and raw data are mixed — teams can't tell what's an observation and what's a conclusion

Repository Architecture

Three Layers

  1. Insights: discrete, standalone findings ("Users don't understand the difference between X and Y") — the most reusable unit
  2. Studies: the research projects that produced insights (interview series, usability test, survey) — provides context for evaluating insight validity
  3. Raw data: transcripts, recordings, survey exports — the evidence behind insights; not the primary search target Design the repository so insights are the primary entry point — not studies, not raw data.

Insight Structure

Each insight should have:

  • Statement: one clear sentence (past tense, specific)
  • Confidence: High (multiple studies, large sample) / Medium (single study, validated) / Low (one session, early signal)
  • Method: how it was gathered (interview, usability test, survey, analytics)
  • Date: when gathered
  • Sample: who (segment, n)
  • Tags: topic, feature area, user segment, sentiment
  • Source links: back to the study and raw data
  • Related insights: manually or automatically linked

Tagging System

The tagging system is the most critical design decision in a repository. Define tags before populating:

Tag Dimensions

  • Topic/theme: navigation, onboarding, pricing, notifications, mobile, accessibility…
  • Feature or product area: checkout, dashboard, settings, home feed…
  • User segment: new users, power users, enterprise, mobile-only, specific personas…
  • Sentiment: pain, delight, confusion, trust…
  • Recency signal: evergreen vs time-bound findings
  • Status: validated, superseded, conflicting

Rules

  • Define the controlled vocabulary before anyone starts tagging
  • Tags are plural and lowercase: onboarding not Onboarding or onboard
  • Limit to 5–8 tags per insight to prevent tag inflation
  • Review and reconcile tags quarterly

Repository Culture and Maintenance

A repository is only as good as the habits around it:

Adding research

  • Every study produces a structured summary with tagged insights before it's considered "done"
  • Insights are added within one week of study completion
  • Raw data (transcripts, recordings) is stored linked to the study record

Keeping it current

  • Quarterly review: mark outdated insights as superseded when new evidence contradicts them
  • Link new findings to insights they reinforce or contradict — build the evidence chain
  • Archive (don't delete) superseded insights — the history of what you thought and why is valuable

Making it useful

  • Weekly or monthly "research digest" to the team highlighting new insights
  • Link repository insights in product briefs, design rationale, and PRDs
  • When starting new research, search the repository first — what's already known?

Tooling

Common tools used as research repositories:

ToolStrengthsWeaknesses
NotionFlexible structure, links, good searchRequires disciplined setup; search is approximate
AirtableStrong filtering, tagging, viewsLess natural for narrative content
DovetailPurpose-built for research; tagging + transcriptsCost; another tool for teams to adopt
ConfluenceIntegrated with Jira workflowsPoor search; hard to browse by insight
EnjoyHQPurpose-built; good taggingCost; less common
The tool matters less than the structure and tagging conventions — a well-maintained Notion is more useful than a poorly-maintained Dovetail.

Search and Retrieval

Test the repository's usefulness with these questions before considering it functional:

  • "What do we know about why users churn?" → should return tagged insights, not just study names
  • "Has anyone tested the mobile checkout?" → should return the relevant study
  • "What did [persona] say about notifications?" → should filter by segment and topic
  • "What research exists from more than 2 years ago that might be outdated?" → should be filterable by date

Best Practices

  • Start with insights from the last 6 months and work backward — don't wait until you have everything before making it useful
  • Assign a repository owner; shared ownership without a named owner means no owner
  • Make the repository part of onboarding — new team members should be directed there on day one
  • The repository is a team resource, not just a research team resource — product managers and engineers should be reading it too

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

中文简介正在准备中。当前显示英语简介。

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills30582026年9月6日 更新

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

中文简介正在准备中。当前显示英语简介。

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills30582026年9月6日 更新

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

中文简介正在准备中。当前显示英语简介。

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills30582026年9月6日 更新

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

中文简介正在准备中。当前显示英语简介。

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills30582026年9月6日 更新

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

中文简介正在准备中。当前显示英语简介。

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills30582026年9月6日 更新

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

中文简介正在准备中。当前显示英语简介。

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills30582026年9月6日 更新

查看 Owl-Listener 的全部技能

报告此技能的问题