found-this-design
Skill0 starsChanged 2 months agoMITView on GitHub
Find 3 or 5 matching UI designs from the local design bank at `$OPENCODE_DESIGN_BANK` or `~/Design` (Refero styles + Motionsites sections) for the current web project or a redesign brief, then generate a high-fidelity first-viewport photo of this product in each recommended world. Use when the user runs /found-this-design or /found_this_design, or asks to find a design, cari desain, rekomendasi desain, design yang cocok, preview desain, prototype visual, design bank, Refero, Motionsites, or which visual direction fits this site. Not for implementing UI (use impeccable after a pick) or photoreal product/ad video (use visual-studio).
In this repository47 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- academicSkill
- adhdSkill
- agent-architecture-auditSkill
- api-designSkill
- automation-audit-opsSkill
- browser-actSkill
- chrome-devtools-axiSkill
- click-path-auditSkill
- codebase-designSkill
- code-tourSkill
- contract-firstSkill
- cost-aware-llm-pipelineSkill
- diagnosing-bugsSkill
- diagram-designSkill
- domain-modelingSkill
- emil-design-engSkill
- eval-harnessSkill
- full-audit-keamananSkill
- full-performance-auditSkill
- gh-axiSkill
- grill-with-docsSkill
- humanizerSkill
- hyperframesSkill
- id-demo-videoSkill
- img2threejsSkill
- impeccableSkill
- install-anti-slopSkill
- markitdownSkill
- matt-code-reviewSkill
- mongodb-opsSkill
- playwright-qaSkill
- prompt-optimizerSkill
- prototypeSkill
- researchSkill
- scroll-craftSkill
- scroll-worldSkill
- skill-stocktakeSkill
- smartbook-ingestSkill
- smartdocSkill
- supabase-opsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- vercel-opsSkill
- visual-studioSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 3 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Before any image_gen / image_edit: OpenCode native image tools if the session exposes them.
- Very specific: line 22
Do not load impeccable, emil-design-eng, visual-studio, or adhd.
- Distinctive: line 26
Stop before component atoms.
- Very specific: line 27
Search with the scripts. Never read either catalog.json into context.
- Very specific: line 29
Do not implement UI, copy a Motion prompt into code, or overwrite the project's DESIGN.md unless the user asked to pin files.
- Very specific: line 31
Do not crawl Refero or Motionsites.
- Very specific: line 49
If PRODUCT.md is missing and the query does not name a surface or product, ask one round: which surface, and what mood is forbidden.
- Distinctive: line 51
Do not ask for hex or canned aesthetic lanes.
- Very specific: line 59
Use laneHint from the brief unless the user named a lane.
- Distinctive: line 68
Comps: After the shortlist, not before.
- Very specific: line 87
If there is no screenshot but a local page or dev server exists, capture one first viewport through opencode-chromium-cdp + browser-act …
- Very specific: line 112
Pin + handoff: After a pick, write .impeccable/found-this-design.json (slug, bank, pack paths, lane, one-line reason, comp path).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Found This Design
Find a visual direction from the local bank. Recommend 3 (default) or 5.
Generate a high-fidelity first-viewport photo of this product in each
world, then stop. /impeccable builds after the user picks. Stop before
component atoms; atoms are impeccable + Design V2.
/found_this_design is the same command.
Load
- Matching: references/matching.md
- Bank paths and fields: references/banks.md
- Before any
image_gen/image_edit: OpenCode native image tools if the session exposes them; otherwise write prompt files and mark DEGRADED. Do not restate it. - Do not load
impeccable,emil-design-eng,visual-studio, oradhd.
Hard rules
- Stop before component atoms; atoms are impeccable + Design V2.
- Search with the scripts. Never read either
catalog.jsoninto context. - External brand pattern corpora (e.g.
awesome-design-md) may be referenced by humans as styling ideas, but never fetched, cloned, or vendored into the project. Product UI direction flows strictly from the local Design Bank →impeccable. - Do not implement UI, copy a Motion prompt into code, or overwrite the
project's
DESIGN.mdunless the user asked to pin files. - Do not crawl Refero or Motionsites. Do not open
npm run bankunless the user asked to browse. - Generate comps only for the shortlist. One viewport per candidate. No full-page scroll, no contact sheet.
- Comp text may be approximate. Product facts on the cards must be true.
- Match the user's language. Lane names stay English.
Run
<skill-dir> is this skill's directory.
Fingerprint. From the user text, decide
count(5 only if they asked for 5 / "lebih banyak") andquery. Then:node <skill-dir>/scripts/fingerprint.mjs --cwd <project> --query "<text>" --count 3 > brief.jsonIf
PRODUCT.mdis missing and the query does not name a surface or product, ask one round: which surface, and what mood is forbidden. Do not ask for hex or canned aesthetic lanes.Search.
node <skill-dir>/scripts/search.mjs --brief brief.json --lane <identity|section|both> --count <n>Use
laneHintfrom the brief unless the user named a lane. Override bank root withOPENCODE_DESIGN_BANKor--bank. Exit 2 = catalogs missing; report the paths and stop.- Read the shortlist packs only. For each item:
preview,files.meta, and the start offiles.design(Refero) orfiles.prompt(Motion). Collect real product name, offer, and visitor job fromPRODUCT.md/ the query. Do not invent claims. Comps. After the shortlist, not before. Save:
.impeccable/found-this-design/<slug>-comp.png .impeccable/found-this-design/<slug>-comp.prompt.txtOne first-viewport photo of this product wearing that bank world. High fidelity, not a wireframe, not the source thumb. Layout may leave the current site. Keep product name, offer, facts, and the visitor's job. Aspect
16:9desktop;9:16when the surface ismobile-appor the user asked mobile.Condition Tool References Current-site screenshot exists image_editscreenshot (product facts) + bank preview (world) Greenfield / no UI image_editbank preview only; prompt carries product facts Tool blocked or failed do not retry to evade show the bank thumb; say the comp is missing If there is no screenshot but a local page or dev server exists, capture one first viewport through
opencode-chromium-cdp+browser-actonly as an edit reference. Skip if capture fails.Fire 3 or 5 calls in parallel, one prompt per candidate (2–5 sentences): surface regions in order → this product's content in those regions → bank northStar / hexes / type / material → "high-fidelity designed website viewport, not a poster, not a photograph of a place". If a render reads as a poster or a photo of the subject, regenerate that slot once with a more literal layout skeleton. Write the prompt beside the png.
Re-roll generates only new ids (
--excludethe ones already shown). Expanding 3 → 5 generates the two extras only.Cards. Equal weight. Hero = generated comp (workspace-relative path). Bank thumb is a small "source" label.
Each card: product-in-that-world photo, source thumb, name, bank, kind/jenis, theme, one sentence from
reasons(why it fits this brief — not "best"), pack paths. Mark the score leader as "closest to the brief".Then offer: pick one · show 5 (if 3) · re-roll with a steer.
Pin + handoff. After a pick, write
.impeccable/found-this-design.json(slug,bank, pack paths,lane, one-line reason,comppath). Read that pack's DESIGN.md + tokens or prompt. The comp is a north-star preview, not a pixel spec; the bank pack owns tokens and type. Say the next step is/impeccablewith this world and this comp. Stop. Do not write components.Redesign: old look is anti-reference. New: pin is the starting world. Section: keep the project's identity; Motion fills only that section.
Prompt checklist (every comp)
- Product name and real offer, no invented customers/prices/metrics
- Named surface regions and their scale
- Bank hexes + type character + northStar or Motion material
- "Designed website viewport" — not poster, not interior photo
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.

