borghei/Claude-Skills / product-team/design-direction
design-direction
VerifiedTurns a product brief into a design-system spec: style direction, contrast-checked palette, type pairing, tokens, UX rules and chart choices. Use when starting a new product's UI, picking a palette or fonts, or auditing a token file.
assets/design-spec-template.md
View on GitHub# Design Direction Decision: [Product name]
**Date:** [YYYY-MM-DD] **Owner:** [name] **Spec verdict:** [CONSISTENT / CONFLICTS — paste from the tool]
## Brief
- Product: [one sentence]
- Audience and context of use: [who, where, on what device, with what constraints]
- Platform / mode / contrast target: [web | mobile | both] / [light | dark | both] / [AA | AAA]
- Brand inputs that are fixed: [colours, typefaces, logo rules — with source]
## Decisions
| Decision | Choice | Source | Overridden? Why |
|----------|--------|--------|-----------------|
| Product type | [id] | recommender | |
| Direction | [id] | recommender | |
| Palette | [id] | recommender | |
| Type pairing | [display / body / mono] | recommender | |
| Density | [compact / comfortable / spacious] | | |
| Motion tier | [calm / standard / expressive] | | |
## Findings carried forward
Paste every `fail` and `warn` from the recommender and the checker. Each gets an owner
and a resolution, or a one-sentence reason it is accepted.
| Finding | Owner | Resolution |
|---------|-------|------------|
| | | |
## Token audit
- Checker run on: [file] — [PASS / FAIL], critical [n] high [n] medium [n] low [n]
- Palettes re-verified after any edit: [yes / not edited]
## Manual rules reviewed
List the rule ids from the spec's UX rules table reviewed with the product open, and the
result of each.
| Rule | Screen / component | Result |
|------|--------------------|--------|
| | | |
## Sign-off
- [ ] Every colour pair in both modes passes the target (tool output attached)
- [ ] Brand colour adjustments accepted by the brand owner
- [ ] Reduced-motion behaviour specified for every animation
- [ ] Chart choices map to written data questions
- [ ] Stack notes handed to engineering
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |