Agent skill
atlas-ui
Atlas design system knowledge - components, patterns, and theming
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/atlas-ui
SKILL.md
Atlas UI Design System
Component Library
Atlas uses shadcn/ui as the base with custom branded components in client/src/components/atlas/.
Available Base Components (shadcn/ui)
Accordion, AlertDialog, AspectRatio, Avatar, Checkbox, Collapsible, ContextMenu, Dialog, DropdownMenu, HoverCard, Label, Menubar, NavigationMenu, Popover, Progress, RadioGroup, ScrollArea, Select, Separator, Slider, Slot, Switch, Tabs, Toast, Toggle, ToggleGroup, Tooltip
Custom Atlas Components
Located in client/src/components/atlas/:
- Custom branded variants of base components
- Enterprise-specific UI patterns
Utility Functions
cn()from@/lib/utils— merges Tailwind classes (clsx + tailwind-merge)class-variance-authority(cva) — component variant definitions
Theming
- Dark/light mode via
next-themes - CSS custom properties for colors
- Tailwind config in
tailwind.config.ts
Icons
- Use
lucide-reactfor all icons - Import:
import { IconName } from "lucide-react"
Forms
- React Hook Form + Zod for validation
- Use
@hookform/resolvers/zodfor schema integration - Pattern: define Zod schema → create form with useForm → render with Form components
Data Display
- Charts:
rechartslibrary - Tables: custom implementations with pagination
- PDF export:
jspdf+jspdf-autotable - Excel export:
xlsxlibrary
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?