agentleFS
kuker24kuker24/OpenCodeBestFriend/skills/found-this-design/SKILL.md

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).

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
  1. Very specific:

    Before any image_gen / image_edit: OpenCode native image tools if the session exposes them.

    line 21
  2. Very specific:

    Do not load impeccable, emil-design-eng, visual-studio, or adhd.

    line 22
  3. Distinctive:

    Stop before component atoms.

    line 26
  4. Very specific:

    Search with the scripts. Never read either catalog.json into context.

    line 27
  5. Very specific:

    Do not implement UI, copy a Motion prompt into code, or overwrite the project's DESIGN.md unless the user asked to pin files.

    line 29
  6. Very specific:

    Do not crawl Refero or Motionsites.

    line 31
  7. Very specific:

    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.

    line 49
  8. Distinctive:

    Do not ask for hex or canned aesthetic lanes.

    line 51
  9. Very specific:

    Use laneHint from the brief unless the user named a lane.

    line 59
  10. Distinctive:

    Comps: After the shortlist, not before.

    line 68
  11. Very specific:

    If there is no screenshot but a local page or dev server exists, capture one first viewport through opencode-chromium-cdp + browser-act …

    line 87
  12. Very specific:

    Pin + handoff: After a pick, write .impeccable/found-this-design.json (slug, bank, pack paths, lane, one-line reason, comp path).

    line 112

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, or adhd.

Hard rules

  • Stop before component atoms; atoms are impeccable + Design V2.
  • Search with the scripts. Never read either catalog.json into 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.md unless the user asked to pin files.
  • Do not crawl Refero or Motionsites. Do not open npm run bank unless 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.

  1. Fingerprint. From the user text, decide count (5 only if they asked for 5 / "lebih banyak") and query. Then:

    node <skill-dir>/scripts/fingerprint.mjs --cwd <project> --query "<text>" --count 3 > brief.json

    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. Do not ask for hex or canned aesthetic lanes.

  2. Search.

    node <skill-dir>/scripts/search.mjs --brief brief.json --lane <identity|section|both> --count <n>

    Use laneHint from the brief unless the user named a lane. Override bank root with OPENCODE_DESIGN_BANK or --bank. Exit 2 = catalogs missing; report the paths and stop.

  3. Read the shortlist packs only. For each item: preview, files.meta, and the start of files.design (Refero) or files.prompt (Motion). Collect real product name, offer, and visitor job from PRODUCT.md / the query. Do not invent claims.
  4. Comps. After the shortlist, not before. Save:

    .impeccable/found-this-design/<slug>-comp.png
    .impeccable/found-this-design/<slug>-comp.prompt.txt

    One 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:9 desktop; 9:16 when the surface is mobile-app or the user asked mobile.

    ConditionToolReferences
    Current-site screenshot existsimage_editscreenshot (product facts) + bank preview (world)
    Greenfield / no UIimage_editbank preview only; prompt carries product facts
    Tool blocked or faileddo not retry to evadeshow 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-act only 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 (--exclude the ones already shown). Expanding 3 → 5 generates the two extras only.

  5. 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.

  6. Pin + handoff. After a pick, write .impeccable/found-this-design.json (slug, bank, pack paths, lane, one-line reason, comp path). 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 /impeccable with 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.