What problem does it solve? Building UI with the chrome component registry requires knowing which of its 100+ components exists, what props each accepts, and how its dark brutalist design language works — this Skill gives an agent that knowledge so it installs and composes the right components instead of guessing props or inventing inconsistent UI. ## Core Features & Use Cases - Component installation workflow: Guides init and add commands via the @justin06lee/chrome CLI, with transitive dependency resolution, import rewriting, and conflict handling. - Full component reference: Eight reference files document every component's role, internals, props with types and defaults, gotchas, and canonical examples. - Design language enforcement: Codifies the dark-only, square-corner, lowercase-copy, no-ascii-arrow rules so composed UI matches the registry. - Use Case: Ask the agent to add a searchable project grid to a Next.js app — it checks for chrome.json, reads the gallery reference, runs bunx @justin06lee/chrome@latest add gallery, and wires the component with correct props. ## Quick Start Use the chrome skill to add a command palette and a toast system to my Next.js project and wire them into the root layout.
