design-research
Skill10 starsChanged 28 days agoMITView on GitHub
Run a competitive research pass on a target site and its top competitors, producing a structured competitive-intelligence report — brand snapshot, competitor scoring, white-space gaps, and keyword landscape — plus a build brief that feeds the design and SEO workflow. Uses the Firecrawl MCP for deep multi-page scraping when connected; otherwise built-in WebFetch/WebSearch + html-extract. Trigger when the user says "competitive research", "competitor analysis", "research the niche", "niche research", "what are competitors doing", "give me a competitive report", "client research", or "engagement research".
- Reads credentials
10 other projects use a version of this.
Adopted by
Most recently taken up by
- fergo5002/design-directortheir own version, first seen Nov 15, 2026
- ldaume/agentic-engineering-harnesstheir own version, first seen Nov 8, 2026
- matthewdigiuseppe/MStacktheir own version, first seen Nov 1, 2026
- int2t05/engineering-skillstheir own version, first seen Oct 15, 2026
- shub-rajput/design-superskillstheir own version, first seen Oct 14, 2026
- adtn0810/truestacktheir own version, first seen Sep 12, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- hamelsmu/design-research★ 76same name
- matthewdigiuseppe/MStack★ 17same name
- tykisgod/quick-question★ 12same name
- mevans2120/design-suite-claude-skills★ 11same name
- shub-rajput/design-superskills★ 10same name
- int2t05/engineering-skills★ 3same name
- ldaume/agentic-engineering-harness★ 3same name
- adtn0810/truestack★ 2same name
- fergo5002/design-director★ 1same name
- wjlgatech/design-anything★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- blast-promptSkill
- client-outreachSkill
- content-draftSkill
- copywritingSkill
- csv-to-reportSkill
- design-accessibilitySkill
- design-buildSkill
- design-croSkill
- design-dimensionsSkill
- design-motionSkill
- design-system-genSkill
- design-system-persistSkill
- design-tokens-emitSkill
- design-visual-qaSkill
- html-extractSkill
- parallel-buildSkill
- portable-html-portSkill
- qa-gateSkill
- route-codex-reviewSkill
- route-gemini-contextSkill
- route-three-brainSkill
- seo-auditSkill
- seo-backlinksSkill
- seo-clusterSkill
- seo-competitor-pagesSkill
- seo-content-briefSkill
- seo-contentSkill
- seo-dataforseoSkill
- seo-driftSkill
- seo-ecommerceSkill
- seo-firecrawlSkill
- seo-geoSkill
- seo-googleSkill
- seo-hreflangSkill
- seo-image-auditSkill
- seo-image-genSkill
- seo-local-unifiedSkill
- seo-pageSkill
- seo-programmaticSkill
- seo-schemaSkill
- seo-sitemapSkill
- seo-strategySkill
- seo-sxoSkill
- seo-technicalSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Detect tooling: Check whether the Firecrawl MCP is connected:
- Distinctive: line 47
Identify competitors: Use WebSearch on the niche + the target's core terms to assemble a competitor set (default 5).
- Very specific: line 58
Read the craft dimensions with the negative-space/rhythm method in references/design-research/white-space-method.md.
- Distinctive: line 70
Tier 1 — Firecrawl MCP: If connected, deep multi-page scraping of target + competitors.
- Distinctive: line 74
Tier 4 — guided: If a site is JS-rendered and Firecrawl isn't connected, work from the pages you can fetch and note what a full crawl would …
- Distinctive: line 77
Always state which tier ran and what Firecrawl would add.
- Distinctive: line 106
Every row degrades to a real deliverable.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
design-research
Family: design Status: Stable
Purpose
The research front-end of an engagement. Given a target domain and a niche, it
captures the target's positioning, identifies top competitors, scores each on key
dimensions, surfaces the white space no one is filling, and produces a markdown or
interactive-HTML report that feeds design-system-gen, design-dimensions,
blast-prompt, and the SEO skills. It is tool-aware: with the Firecrawl MCP it
does deep multi-page scraping; without it, built-in web fetch/search + html-extract
still produce a real competitive read.
Triggers
- "competitive research" / "competitor analysis"
- "research the niche" / "niche research"
- "what are competitors doing"
- "give me a competitive report"
- "client research" / "engagement research"
Inputs
- Target domain
- Industry / vertical
- Geographic scope (local / national / global)
- Number of competitors (default 5)
- Output format: markdown | interactive HTML | both
Steps
- Detect tooling. Check whether the Firecrawl MCP is connected:
(on Windows usepython3 "${CLAUDE_PLUGIN_ROOT}/scripts/workflow/capability_probe.py"pyifpython3is absent; in PowerShell the variable is$env:CLAUDE_PLUGIN_ROOT). It reports whetherFIRECRAWL_API_KEYis set. - Capture the target. Tier 1: Firecrawl-scrape the site for voice, services,
positioning. Tier 2: WebFetch the key pages +
html-extractfor structure/tokens. - Identify competitors. Use WebSearch on the niche + the target's core terms to assemble a competitor set (default 5); let the user confirm/adjust.
- Scan each competitor. Same tier path as step 2, one pass per competitor.
- Score each on the 18-dimension rubric in
data/competitor-rubric.csv(positioning, brand-craft, content-depth, trust-signals, conversion-path, findability). Score every dimension 0–4 against its good/bad anchors and roll up the weighted composite exactly asreferences/design-research/competitor-rubric.mddescribes, so scores compare across competitors. - Find the white space — walk each dimension across the whole set and flag the
ones where every competitor is weak (the rubric's
white_space_testcolumn). Read the craft dimensions with the negative-space/rhythm method inreferences/design-research/white-space-method.md. - Keyword landscape — call
seo-clusterif available; otherwise a WebSearch-based intent grouping. - Compose the report into the user's workspace (see Outputs).
- Report which tier ran and what a full Firecrawl crawl would add.
Capability routing
This skill follows the plugin's capability-tier cascade
(references/CAPABILITY-TIERS.md):
- Tier 1 — Firecrawl MCP. If connected, deep multi-page scraping of target + competitors.
- Tier 2 — built-in (default). WebFetch + WebSearch +
html-extractfor a real competitive read from the key pages. - Tier 4 — guided. If a site is JS-rendered and Firecrawl isn't connected, work from the pages you can fetch and note what a full crawl would add.
Always state which tier ran and what Firecrawl would add.
Outputs
Written into the user's project workspace:
| Output | What it contains | Format | Quality bar (how it is scored) |
research/01-target-brand.md | brand/positioning extraction for the target | md | every claim traces to a fetched page; no invented positioning |
research/02-competitor-analysis.md | each competitor scored 0–4 on all 18 rubric dimensions + six weighted category scores + overall + keyword landscape | md (Critical/High/Medium open-lane groups) | every score cites the signal_to_check it was read from; anchors from data/competitor-rubric.csv; unobservable dimensions marked "not assessed", never zeroed |
research/03-build-brief.md | the highest-weight open lanes turned into headline build moves | md | each move names the dimension + white_space_test it fills; ranked by rubric weight |
competitive-analysis.html (optional) | interactive scoring report (radar/bar over the six categories) | HTML | scale reads 0–4 honestly; no rescale-to-100 implying false precision |
| Tier line | which tier ran + what a full Firecrawl crawl would add | one sentence | states the tier honestly; no fabricated SEO/performance number |
Filed to: the user's project workspace, never into the plugin. A never-fabricate field (competitor SEO volume, field CWV, backlink counts) ships as a labeled proxy
- a
needs_tier1note — never a synthesized number.
Error Handling
| Condition | Detection | Behavior (degrade, never fail) | User-facing message |
| Firecrawl MCP absent | capability_probe.py reports FIRECRAWL_API_KEY unset / MCP not exposed | fall through to Tier-2 WebFetch + WebSearch + html-extract | "Ran Tier 2 (built-in fetch). Add Firecrawl for deep multi-page + JS-rendered crawl." |
| A competitor site is JS-gated / auth-walled | key pages fetch empty or a shell | score only the dimensions whose signal_to_check was observable; mark the rest "not assessed" | "Couldn't reach <pages> — scored the visible signals; a Tier-1 crawl would complete the rubric." |
| No network / offline | fetch raises or --no-network set | analyze provided saved pages / files only | "Offline — scored the provided pages; live fetch would add competitors and freshness signals." |
| Too few competitors found | WebSearch returns < requested set | score what was found; state the smaller n | "Found only <n> credible competitors — scored those; broaden the niche terms to add more." |
seo-cluster unavailable | skill not installed / not routed | fall back to a WebSearch-based intent grouping for the keyword landscape | "Used a WebSearch keyword read; install seo-cluster for SERP-overlap clustering." |
| Bad / empty input (no target domain) | required input missing | ask for the target + niche; do not invent a subject | "A target domain and niche are required to run a competitive pass." |
Every row degrades to a real deliverable; the built-in Tier-2 path is the product.
Dependencies
- Optional (Tier 1): Firecrawl MCP (
extensions/firecrawl/) — deep scraping; free path works without it - Built-in (Tier 2): WebFetch; WebSearch;
html-extract seo-cluster(optional — adds SERP-based keyword landscape; free path: WebSearch intent grouping)scripts/workflow/capability_probe.py(required — tooling detection)- Scoring rubric + method (required knowledge):
data/competitor-rubric.csv,references/design-research/competitor-rubric.md,references/design-research/white-space-method.md
Notes
The output structure is a proven engagement shape, made repeatable here instead of
bespoke per project. Respect target sites' robots.txt and Terms of Service when
scraping (see PRIVACY.md); research artifacts stay in the user's workspace.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

