lamina-research
Plan and synthesize evidence-grounded product research. Use when deciding what evidence is needed, designing actor walkthroughs, grounding claims in a repository or live product, analyzing user-provided references, modeling users and tasks, or communicating findings without inventing data. Use lamina-evaluation instead to judge a built product, and lamina-ux to design interaction behavior.
npx skills add aryaniyaps/lamina --skill lamina-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lamina Research ## Reference-loading protocol 1. Match the request's primary research decision to one row below. 2. Open that linked reference before answering. Add another only when a second decision materially changes the answer; do not preload the directory. 3. Start the response with `Using lamina-research: <topic path(s)>` so the selected evidence lens is auditable. ## Topic index | Decisio
What does the lamina-research skill do?
Plan and synthesize evidence-grounded product research. Use when deciding what evidence is needed, designing actor walkthroughs, grounding claims in a repository or live product, analyzing user-provided references, modeling users and tasks, or communicating findings without inventing data. Use lamina-evaluation instead to judge a built product, and lamina-ux to design interaction behavior.
How do I install it?
Run `npx skills add aryaniyaps/lamina --skill lamina-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aryaniyaps/lamina, a repository with 111 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.