agentsclimarketplace

Design research

Skill wjlgatech/design-anything/skills/design-research

Any design intent in (text, picture) → execution-ready 3D blueprint out — construction- and 3D-print-verified. Game design · simulation · architecture (3DCP+AI) · interior · landscape.

Install
npx -y skills add wjlgatech/design-anything --skill design-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the three-window research method on any design question: /last30days (engagement — what's alive now), /last30years (survival — what's load-bearing), /last300years (endurance — what governs taste). Trigger: "research X for this design", "what's the state of the art in Y", "has Z ever worked".

The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, as published. Nobody here has run it

design-research

When to use

Before betting the repo, a project, or a client on a tool, method, or principle.

What it does

  1. 30 days: rank by observed engagement — releases, stars, pushes, dated announcements. Freshest verified signal wins; reputation counts for nothing.
  2. 30 years: rank by survival — still-used + built-upon + hype-survived (the 3-probe test). Tier 🏛/🌳/🌱; under-10-years can never outrank a survivor.
  3. 300 years: rank by endurance with a Whig-history guard — keep the surviving kernel, flag the superseded dogma (Modulor's ruler, not his city).
  4. Synthesize the Lindy read: bet interfaces on survivors, hot-swap the young layer, and record the anti-portfolio (who was louder and died).

Example

The repo's own digests are the golden output: research/last30days/DIGEST.md, research/last30years/DIGEST.md, research/last300years/DIGEST.md.

Verification (eval-with-teeth)

Every entry carries a URL; dated claims carry dates; anything unverifiable is marked UNVERIFIED; single-source promotional claims are flagged as such. A digest with unlabeled uncertainty is a failed run — no evidence ⇒ No.

Safety

Research grounds decisions; it doesn't make them. Surface trade-offs, let the human pick at genuine forks.

Cross-runtime

Needs web search in the harness; degrades to knowledge-cutoff answers with an explicit staleness warning.

Gives 0 of the 12 instructions most design frontend skills give

Counted across 1,170 of the 1,878 authors here whose files we hold, read 2026-08-06

  • use css variables for color consistencyin 73 of 1170, across 24 files
  • match implementation complexity to the aesthetic visionin 70 of 1170, across 20 files
  • commit to one bold aesthetic direction before codingin 70 of 1170, across 25 files
  • add atmospheric background effects and texturesin 58 of 1170, across 10 files
  • use unexpected spatial compositions and layoutsin 55 of 1170, across 7 files
  • implement real working codein 55 of 1170, across 7 files
  • vary themes and aesthetics across different designsin 48 of 1170, across 7 files
  • launch chromium in headless modein 47 of 1170, across 4 files
  • close the browser when donein 47 of 1170, across 4 files
  • run provided scripts with help flag firstin 47 of 1170, across 4 files
  • use descriptive selectors for elementsin 47 of 1170, across 4 files
  • wait for network idle statein 46 of 1170, across 3 files

Said here and by no other author read

  • rank recent items by observed engagement
  • prefer freshest verified signal over reputation
  • rank historical items by survival
  • apply the 3-probe test
  • rank old ideas by endurance
  • keep the surviving kernel

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.