search-design-system

Search Design System

Overview

Turn a design need into a private, structured search; inspect the returned evidence before selecting a theme. Search and scoring run locally after the versioned index is loaded.

Workflow

1. First organize the requirements into a structured query. Extract only the platform, industry, product type, page type, style, brand personality, color scheme, light/dark mode, density, and keywords. Do not pass the user's original text to scripts or network endpoints.
2. Determine the platform. When the user has not specified it, confirm the platform with the user, or search both the desktop and mobile indexes at the same time; do not default on your own.
3. According to query-schema.md and taxonomy.md generate the request. By default use scripts/cli.mjs search to read Make-Template's online manifest; pass --index and --local-root。
4. For each candidate, read matched、unmatched、scoreBreakdown、reviewStatus and publishable, then obtain the complete DESIGN.md and view the preview. Do not select based only on score.
5. Explain the recommendation reasons and mismatches in light of the user's constraints.deferred may be used for local reference, but must not be described as having obtained public release authorization.
6. Download the package only when the user's workflow needs deployable resources; for ordinary selection, read only DESIGN.md and the preview. Do not send use events or analytics events.

Example

Write the locally organized request to a temporary file:

{
  "schemaVersion": 1,
  "readerVersion": "1.0.0",
  "platform": "desktop",
  "terms": ["analytics", "finance"],
  "hardFilters": { "industries": ["finance-payments"] },
  "softFilters": { "styles": ["professional"], "density": ["high"] },
  "exclude": { "styles": ["playful"] },
  "limit": 4
}

node scripts/cli.mjs search --index /path/to/desktop.json --request /path/to/request.json --local-root /path/to/runtime

Then pass one returned result to scripts/cli.mjs fetch --kind designMd and read the full body before choosing.

Quick reference

Situation	Action
Platform missing	Confirm, or search both indexes
Deferred result	Read verified DESIGN.md and preview locally or online; package stays unavailable
Online result	Default to the canonical Make-Template manifest and verified hashes
Too few results	Report resultSummary.reason; do not pad or duplicate
Stale cache	State it explicitly; do not silently downgrade

Common mistakes

• Passing the user's original prose as terms instead of extracting a minimal structured query.
• Choosing the top score without reading unmatched constraints and full DESIGN.md.
• Treating deferred as publishable or inventing a public artifact URL.
• Downloading a package during exploration when DESIGN.md and preview are sufficient.

Read response-schema.md for result fields, artifact behavior, and stable error codes.