Agent skill
frontend-design
Enforce a precise, minimal design system for Battery's dashboard UI. Use this skill when building admin interfaces, deployment management screens, or any dashboard components. Inspired by Linear, Notion, and Stripe - clean, modern, enterprise-grade with Jony Ive-level precision.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/frontend-design-adlenehan-battery
SKILL.md
Frontend Design Principles
Design Direction
Battery is an enterprise deployment platform. The aesthetic should communicate:
- Trust & Sophistication: Cool tones, layered depth, professional
- Data & Analysis: Numbers-first, monospace for IDs and timestamps
- Utility & Function: Dense but readable, efficient use of space
Color Foundation
- Primary: Cool grays with blue undertones
- Accent: Electric blue for primary actions, success states
- Semantic: Green (deployed), Yellow (pending), Red (error/revoked)
- Mode: Support both light and dark themes
Core Craft Principles
4px Grid System
All spacing uses multiples of 4px:
4px- Tight inline spacing8px- Related elements12px- Default padding16px- Section gaps24px- Major separations32px- Page-level spacing
Symmetrical Padding
Top/Left/Bottom/Right must match. Never asymmetric padding.
// Correct
<div className="p-4">
<div className="px-4 py-3">
// Incorrect - asymmetric
<div className="pt-2 pb-4 pl-3 pr-5">
Border Radius Consistency
Use one system throughout:
rounded-none- Tables, code blocksrounded(4px) - Buttons, inputs, cardsrounded-lg(8px) - Modals, large containers
Depth & Elevation
Prefer borders over shadows for structure:
// Preferred - border-based depth
<div className="border border-gray-200 dark:border-gray-800">
// Use shadows sparingly for floating elements only
<div className="shadow-lg"> // Dropdowns, modals only
Typography Hierarchy
- Headings: System font, semibold (600)
- Body: System font, regular (400)
- Data: Monospace for IDs, timestamps, counts, URLs
// Data should use monospace
<span className="font-mono text-sm">deploy_abc123</span>
<span className="font-mono tabular-nums">1,234</span>
Iconography
Use Phosphor Icons (regular weight) throughout:
import { Rocket, Shield, Database } from '@phosphor-icons/react'
<Rocket size={20} />
Color for Meaning Only
- Gray builds structure
- Color communicates status/action
- Never decorative gradients
// Status colors
<Badge variant="success">Deployed</Badge> // Green
<Badge variant="warning">Pending</Badge> // Yellow
<Badge variant="error">Failed</Badge> // Red
<Badge variant="default">Draft</Badge> // Gray
Navigation & Layout
Sidebar Pattern
- Fixed left sidebar (240px)
- Logo top-left
- Primary nav with icons + labels
- User/org switcher bottom
Content Area
- Max width 1200px for readability
- Consistent page header pattern
- Breadcrumbs for deep navigation
Dark Mode
- Borders become more prominent than shadows
- Backgrounds: gray-900, gray-950
- Text: gray-100 (primary), gray-400 (secondary)
- Maintain same spacing and structure
Anti-Patterns
Never use:
- Drop shadows for depth (use borders)
- Border radius > 8px
- Asymmetric padding
- Decorative gradients
- Multiple font families
- Colorful backgrounds (except status indicators)
- Rounded-full on non-avatar elements
Always question:
- Is this spacing a multiple of 4?
- Is this color communicating meaning?
- Would this look correct in dark mode?
- Is data displayed in monospace?
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?