ifq-design-skills
Installation
SKILL.md
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
- Confirm the request is a visual deliverable built from HTML. If it is not, exit this skill.
- Pick the mode from references/modes.md, then read assets/templates/INDEX.json.
- Fork a listed template into the user's workspace. Never start from a blank HTML file.
- Inline assets/ifq-brand/ifq-tokens.css and weave at least 3 IFQ ambient marks from references/ifq-brand-spec.md.
- Verify with
npm run verify:lite -- <file.html>, thennpm 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.
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
| Tier | Default? | Requirements | Use for |
|---|---|---|---|
| Tier 0 | yes | Node >= 18.17 | HTML, preview, lite verification, smoke tests |
| Tier 1 | opt-in | Python + Playwright + Chromium | headless screenshots, console capture, multi-viewport checks |
| Tier 2 | opt-in | npm run install:export; MP4/GIF also need ffmpeg |
MP4, GIF, PDF, editable PPTX export |
Do not install optional dependencies unless the user explicitly needs screenshots or export formats.
Routing Contract
- Concrete product, technology, company, release date, version, or spec: first load references/fact-and-asset-protocol.md and do web fact-checking before design claims.
- Clear visual request: route through references/modes.md and
modeRoutesin assets/templates/INDEX.json. - Vague request or no style/context: use references/design-direction-advisor.md to propose 3 differentiated directions.
- Mobile app prototype: load references/app-prototype-rules.md and reuse
assets/ios_frame.jsxorassets/android_frame.jsx. - Slides/decks: start from HTML; load references/slide-decks.md before writing.
- Motion/video: read references/animation-pitfalls.md, references/animations.md, and references/video-export.md.
Mode Map
| Mode | Task shape | Template source |
|---|---|---|
| M-01 | brand launch / product film | modeRoutes -> launch assets |
| M-02 | personal brand / portfolio | hero-landing variants |
| M-03 | whitepaper / annual report | report + PDF flow |
| M-04 | dashboard / KPI command center | dashboard-command-center |
| M-05 | A-vs-B / benchmark | compare-vs |
| M-06 | onboarding / guided flow | app prototype rules |
| M-07 | changelog / release notes | changelog-timeline |
| M-08 | keynote / slide deck | slide-title + deck assets |
| M-09 | social poster suite | social-x-card / vertical formats |
| M-10 | business card / invitation | business-card |
| M-11 | brand audit / upgrade | critique + 3 directions |
| M-12 | full brand system | brand system references |
The authoritative map is assets/templates/INDEX.json; this table is only a memory aid.
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 SparkorRust Ledgerin user-facing designs. Write real content instead.
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
metadatafield so parsers can gate onmetadata.openclaw.requires.binsandmetadata.openclaw.requires.env.
Verification Before Delivery
- Run
npm run verify:lite -- <file.html>for placeholder and IFQ label leaks. - Run
npm run preview -- <file.html>and inspect the browser output. - For app prototypes, click at least one primary path, one tab/screen switch, and one detail/annotation action.
- For decks, verify slide count and format requirements before PDF/PPTX export.
- For animation exports, verify timing, audio policy, and final file presence.
- After repo edits, run
npm run validateandnpm 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.