Imported from peixl/ifq-design-skills (SKILL.md). Install upstream with npx skills add peixl/ifq-design-skills. Copyright stays with the author (Apache-2.0 WITH brand-clause).

IFQ Design Skills

One prompt in -> shippable HTML out, with optional MP4 / GIF / PPTX / PDF / SVG export. This root file is a short router for OpenClaw, ClawHub, skills.sh, Hermes, Codex, Claude Code, Cursor, OpenCode, and other AgentSkills-compatible hosts. Load deeper files only when the task requires them.

30-Second Load Path

1. Confirm the request is a visual deliverable built from HTML. If it is not, exit this skill.
2. Pick the mode from references/modes.md, then read assets/templates/INDEX.json.
3. Fork a listed template into the user's workspace. Never start from a blank HTML file.
4. Inline assets/ifq-brand/ifq-tokens.css and weave at least 3 IFQ ambient marks from references/ifq-brand-spec.md.
5. Verify with npm run verify:lite -- <file.html>, then npm run preview -- <file.html>.

Human + Agent Promise

• Humans get a finished artifact path: HTML first, optional export only when requested, and no hidden setup.
• Agents get a short route: mode, template, must-read references, tier policy, and verification command.
• Maintainers get regression pressure: 12 mode evals, scanner-clean scripts, and marketplace metadata checks.
• Marketplaces get a readable package: one-line install, zero required env vars, explicit permissions, and no silent installs.

First-Run Success Path

After install, make the first interaction produce a visible artifact in one turn:

1. Accept a natural-language visual request without turning it into setup work.
2. Route it to one mode and one template; name both in the final evidence.
3. Write the HTML file into the user's workspace with labeled assumptions for unresolved facts.
4. Run npm run verify:lite -- <file.html> when shell is available, then preview or screenshot with host browser tooling when available.
5. Report the file path, route, template, verification result, and only caveats that affect use.

Do not ask for account login, global install, export dependencies, or broad environment changes during the first-run path.

Output Boundary

• Core output is verified local HTML, plus SVG/static companions or export-ready source structure when the task needs them.
• MP4/GIF/PDF/PPTX helpers are full-repo optional automation. Prepare the HTML source first; install or run export tooling only after explicit user intent.
• Never claim an export file, screenshot, marketplace status, or security result exists until the relevant command or live check has actually passed.

Use When

• Interactive prototype, hi-fi mockup, clickable app flow, dashboard, landing page, whitepaper, report, infographic, slide deck, changelog, card, invitation, social cover, or brand system.
• Motion demo or launch animation, especially when the user also wants MP4/GIF output.
• Design critique, brand diagnosis, or 3 differentiated style directions before implementation.
• The user asks for PDF/PPTX/SVG export from an HTML-first source.

Do Not Use When

• The real task is production frontend engineering, backend work, SEO-critical site implementation, or a CSS bug inside an existing app.
• The user only wants copy editing with no visual artifact.
• The deliverable must round-trip through Word, Google Docs, or a locked corporate template.

Tier Policy

Do not install optional dependencies unless the user explicitly needs screenshots or export formats.

Routing Decision Tree

User request arrives
  │
  ├─ Is it a visual design deliverable? ─── No → Exit skill, hand back to default agent
  │
  ├─ Can you match a mode trigger? ─── Yes (confidence >70%) → fork template → deliver → verify
  │                                      (one-turn: name assumptions, no questions)
  │
  ├─ Can you match a mode trigger? ─── Yes (confidence ≤70%) → design-direction-advisor.md lightweight
  │                                      (3 text-only directions, no demos, wait for user pick)
  │
  ├─ Does it mention a concrete product/tech/event? ─── Yes → fact-and-asset-protocol.md + web fact-check
  │
  ├─ Is it a mobile app prototype? ─── Yes → app-prototype-rules.md + ios_frame.jsx / android_frame.jsx
  │
  └─ Is it motion/video? ─── Yes → animation-pitfalls.md + animations.md + video-export.md

Read references/modes.md for full mode protocol. The Quick Reference table above is the speed layer.

Quick Reference (Agent Speed Table)

All templates: npm run verify:lite -- <file> + npm run preview -- <file> (Tier 0, zero-install).

IFQ Ambient Layer

• The user's brand is the subject. IFQ is the authored layer: layout rhythm, warm paper, rust ledger, mono field notes, signal spark, quiet URL, and editorial contrast.
• Every deliverable uses at least 3 IFQ marks. Never paste a loud generic logo or watermark unless the task is IFQ-owned or an animation export that calls for the promotion stamp.
• Built-in templates use local-first fonts for China-safe rendering. Google Fonts or CDN runtimes are opt-in only; see references/font-loading.md.
• Avoid visible internal taxonomy labels such as Signal Spark or Rust Ledger in user-facing designs. Write real content instead.

Conversation Patterns

Pattern A — Specific request (most common, one turn): User: "做一个 A vs B 对比评测，我们对 Stripe" → Agent: fact-check both products → route M-05 → fork T-compare-vs → fill with verified data → deliver → verify.

Pattern B — Confident default (one turn): User: "给我做个 landing page" → Agent: match M-02 with >70% confidence → fork T-hero-landing → pick Editorial Serif style → fill with defaults → deliver → verify → name assumptions in caveats.

Pattern C — Lightweight advisor (two turns): User: "帮我做点好看的东西" → Agent: no mode match at >70% → read design-direction-advisor.md → propose 3 text-only directions → user picks → route → deliver.

Pattern D — Iterative refinement: User: "把刚才那个 deck 的配色改暖一点" → Agent: locate previous artifact → edit in-place → re-run verify:lite → report what changed.

Rule: never ask more than 1 question per turn. Use defaults for everything else. If the user did not specify a style, pick one and name it in the deliverable — they can iterate.

Error Recovery

Safety Contract

• Root instructions stay scoped to HTML visual delivery. Do not ask for unrelated secrets, host config, persistent agents, or background services.
• Scripts are local-first: no dynamic eval, no runtime network calls, no hidden installs, and no writes outside the user's workspace.
• Required environment variables are intentionally empty. Optional export tools are documented and invoked only after user intent.
• OpenClaw/ClawHub metadata lives in the single-line JSON metadata field so parsers can gate on metadata.openclaw.requires.bins and metadata.openclaw.requires.env.

Verification Before Delivery

1. Run npm run verify:lite -- <file.html> for placeholder and IFQ label leaks.
2. Run npm run preview -- <file.html> and inspect the browser output.
3. For app prototypes, click at least one primary path, one tab/screen switch, and one detail/annotation action.
4. For decks, verify slide count and format requirements before PDF/PPTX export.
5. For animation exports, verify timing, audio policy, and final file presence.
6. After repo edits, run npm run validate and npm run verify:publish.

Reference Map

Completion Rule

Deliver the smallest verified artifact that satisfies the request. Report the output file, the verification commands run, and any caveats. Do not claim export, screenshots, or marketplace safety unless the relevant check actually passed.