Agent skill · Design & Presentation

vibe-research-before-design

Dispatches SOTA research before proposing any new feature, architecture, or technology choice. Use when facing design decisions, not when implementing existing specs.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill research-before-design --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/analysis/research-before-design/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# vibe-research-before-design Before proposing any design, architecture, or technology choice — research first. "Other people's documented failures count as observed failure." ## When to Use This Skill - Designing a new feature or system - Choosing between technologies, frameworks, or patterns - Making architectural decisions with long-term consequences - The user asks "how should we build X?" - You're about to say "I recommend..." for a design choice ## When NOT to Use This Skill - Implementing an already-designed spec (the research was done at design time) - Fixing a bug (use `vibe-debugging-journal` instead) - Simple refactoring with no architectural implications - The user has explicitly chosen a technology and wants implementation ## Steps 1. **Identify the design question** — What decision are we making? What are the key constraints? 2. **Dispatch research** — For each major sub-problem, find: - 2+ named real-world projects/libraries with adoption metrics (GitHub stars, npm downloads, production users) - 1+ academic paper or technical blog with year and venue/source - The **mechanism** — how does it actually work? (Not marketing copy) - **Known failures** — what went wrong fo

What's inside
Steps it walks through
  1. When to Use This Skill
  2. When NOT to Use This Skill
  3. Steps
  4. Red Flags
  5. Output Format
  6. Research Summary
  7. Comparison Table
  8. Recommendation
  9. Sources
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the vibe-research-before-design skill do?

Dispatches SOTA research before proposing any new feature, architecture, or technology choice. Use when facing design decisions, not when implementing existing specs.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill research-before-design --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 majiayu000/claude-skill-registry, a repository with 534 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.

Keep going