ui-craft-dense-dashboard
Dense dashboard / admin / Bloomberg / Retool / data-heavy internal tools. Locked knobs: CRAFT=7, MOTION=3, DENSITY=9. IBM Plex + mono numbers, semantic palette, 4/8px grid, sparklines, tabular-nums. Trigger on: dashboard, admin panel, data-dense, analytics, Bloomberg-like, Retool-like.
What this skill does
# UI Craft — Dense Dashboard Pre-committed dense style: data-first, keyboard-first, operator tools. Bloomberg, Retool, Linear issues view, admin panels. Every pixel earns its place. ## Knobs (locked) - **CRAFT_LEVEL = 7** — polished but not precious; operators value speed over sheen. - **MOTION_INTENSITY = 3** — micro-only. Row hover, row active tint, inline confirm. No scroll reveals in table areas. - **VISUAL_DENSITY = 9** — tight 4/8px grid; whitespace earns its place. Do not re-ask these in Discovery. Confirm brand accent + dark/light preference only. ## Style anchors - UI sans + mono pairing. Mono for every ID, hash, timestamp, code. - Semantic palette required: success, warning, danger, info + one brand accent. - `tabular-nums` on every numeric column; mono on identifiers. - Tight 4/8px spacing grid. `px-3 py-2` table cells, `gap-2` toolbars. - Sparklines everywhere; horizontal bars for categorical; area for time-series. No pie. No 3D. - Keyboard shortcuts visible inline (`⌘K`, `J/K`, `E` to edit). - Dense chrome: breadcrumbs + tabs + toolbars + filter chips are welcome. - Micro-motion only. Row hover, row active, inline save. No entrance stagger. ## Base rules (inherited) All rules in `../ui-craft/SKILL.md` apply. This file overrides knob defaults and adds style-specific guidance below. The anti-slop and craft tests still apply in full. ## Style-specific overrides **Typography** - UI: IBM Plex Sans or Inter, 400 / 500. - Mono: IBM Plex Mono or Geist Mono for IDs, hashes, timestamps, code, version numbers, kbd. - Body size: 13-14px default; 12px in dense tables is fine. - `tabular-nums` on every numeric column, metric card, timestamp, duration. - `font-variant-numeric: tabular-nums slashed-zero` for IDs + codes. - Headings: compact. Page title 18-20px, section 14-15px 500. **Color (semantic palette required)** - Brand accent: one — primary actions, active tab, selected row accent tint. - Semantic, subdued OKLCH (lightness 50-60, chroma ≤ 0.15): - success `oklch(60% 0.12 150)` - warning `oklch(72% 0.13 75)` - danger `oklch(58% 0.15 25)` - info `oklch(62% 0.12 240)` - Never saturated hues — dashboards live on screens for 8 hours. - Status dots, badge text, chip text use semantic color; backgrounds stay neutral. **Spacing & layout** - 4/8px spacing scale — never 5, 7, 9, 10. Stick to 4 / 8 / 12 / 16 / 24. - Table cells: `px-3 py-2` default; `px-2 py-1.5` for ultra-dense. - Toolbar rows: `gap-2`, `h-9` controls, `text-sm`. - Sidebar: narrow (200-240px), subtle bg tint, icon + label; never full dark. - Cards: `p-4`, 8px radius; 1px border over shadow. **Data display** - Every number column: `tabular-nums` + right-aligned. - Every ID / hash / commit / timestamp: monospace. - Sparklines inline in rows for trend context. 24-40px tall, single color. - Category charts: horizontal bars. Time-series: area with 15% → 0% fade. No pies. - Deltas: plain text `+12.5%` in semantic color, no pill. - Empty states: one-line hint + keyboard shortcut to create. **Chrome & navigation** - Breadcrumbs + tabs + sub-toolbar together is expected and fine. - Filter chips: outline style, removable `×`, no pill fill. - Global command palette: `⌘K` visible in header search affordance. - Row actions: inline icons on hover; also available via keyboard. - Pagination: text `Page 3 of 42` + `tabular-nums`, plus `J/K` navigation. **Motion** - Row hover: background shift to `oklch(96% 0.002 250)` light / `oklch(20% 0.005 250)` dark, 80ms. - Active/selected row: brand accent tint at ~6% opacity + 2px accent left border. - Inline save / confirm: 150ms fade + check icon swap. - No scroll-triggered reveals in table areas — they stutter long lists. - Sort arrow, filter open, column resize: instant or <100ms. ## Reference files to read first Load these from `../ui-craft/references/`: - `dashboard.md` — primary reference; metric cards, charts, sidebar, tables - `typography.md` — tabular-nums, mono pairing, scale - `motion.md` Rendering Performance — compositor pipeline, layer promotion, scroll-linked motion - `responsive.md` — tablet + laptop breakpoints, toolbar collapse Skip `inspiration.md` (landing-page focused), `sound.md`. ## Anti-patterns for THIS style - Serif fonts anywhere in chrome or data. Editorial is a different variant. - Proportional figures in numeric columns — always `tabular-nums`. - Saturated hues — reads as consumer app, not operator tool. - Colored pills on every delta — plain text in semantic color. - Pie charts, donut charts, 3D charts. Ever. - Vertical bar chart for time-series — use area/line. - Uniform colored top borders on metric cards. - Card grids with heavy whitespace — if it feels airy, wrong variant. - Full-dark sidebar (common AI pattern) — subtle tint only. - Scroll-triggered reveals or stagger animations in table areas. - Hidden keyboard shortcuts — always surface `⌘K`, row shortcuts, help trigger. - Vague loading states — show skeleton rows matching column structure, not generic spinner.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.