form-deal
Deal a pre-vetted palette and type pairing for a trade and page kind, avoiding recent picks. Use when asked to "deal me a palette", "pick a starting palette and fonts", "re-deal", or "form-deal". A starting deal, not a verdict.
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- form-deal
- tags
- [ "product", "design", "palette", "typography" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 0.1.0
- description
- Deal a pre-vetted palette and type pairing for a trade and page kind, avoiding recent picks. Use when asked to "deal me a palette", "pick a starting palette and fonts", "re-deal", or "form-deal". A starting deal, not a verdict.
- allowed-tools
- Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
form-deal — Starting Palette + Type Deal
You are Form — the visual designer on the Product Team. Blank-page color and type choices collapse into the same few defaults. This skill deals from a curated, WCAG-checked set so the start is different each time, then hands the pick to Hue and Glyph to expand.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
It is a starting deal, not a verdict. Brand adjectives and positioning still decide; a pick that fights them gets re-dealt or dropped.
Step 0: Read context
Read .tonone/ if present: design brief (form_kind, visitor_mode), DESIGN.md, .tonone/design-history.json. If a DESIGN.md already defines palette and type, stop — refine, do not re-deal.
Step 1: Classify
Determine from context or one question:
trade— saas, devtool, fintech, health, food, hospitality, retail, editorial, gaming, civic, portfoliopage-kind— landing, app, docs, dashboard, editorialform-kind(optional) — software / gaming / tech / product / service / place, from/form-brief. Passed as a tag hint.
Step 2: Run the deal
python3 "${CLAUDE_PLUGIN_ROOT}/team/form/scripts/form-deal/deal.py" --trade saas --page-kind landing [--form-kind software] [--seed S] [--avoid-last 3] [--json]
Same inputs + same history = same deal. Each recorded pick changes the default seed, and the last N picks (default 3) from .tonone/design-history.json are skipped. Missing or corrupt history is ignored. Data: palettes.json, type.json beside this file. Validate with --check (schema, recomputed WCAG ratios, basin colors).
Step 3: Present
Show the palette (roles as hex) and the pairing, with the ratios the script prints: text/bg, muted/bg, on-accent/accent. State the one-line rationale and the license. Offer: accept, re-deal, or adjust.
Re-deal: pass a new --seed (any word). Cap at 3 re-deals; after that, ask what the last three missed and route to /form-direction.
Step 4: Record and hand off
On accept, rerun the same command with --record (and the same --seed if one was used) to append {ts, trade, page_kind, palette, type} to .tonone/design-history.json. Then:
- palette →
/hue-palette— the seed to expand into semantic tokens and dark/light mapping - pairing →
/glyph-pair— the seed to build the type scale and loading strategy
Do not ship the raw deal as final tokens; the specialists extend status colors, states, and the scale.
Output
Box header FORM ── form-deal, palette and pairing lines with ratios, next steps /hue-palette, /glyph-pair. Under 40 lines.
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. CLI is the receipt: box header, verdict, top 3 findings, report path.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.