Instructions

Build a full doc browser per design-guidelines.md. For component-level design work use web-design-guidelines first.

When to Use

• Use when shipping the SkillCodex / skills.sh-style documentation browser UI.
• Prefer web-design-guidelines for single-component audits or smaller doc UI pieces.
• Do not use this skill for SaaS dashboards, auth, or APIs.

STRICT UI ONLY - no backend, API, DB, or auth.

Package manager: pnpm for new app; match user lockfile if a project exists.

Motion (aligned with web-design-guidelines): default Tier 0 - div + CSS / Tailwind transitions (CARD_HOVER, animate-pulse skeletons). Use framer-motion only in a dedicated *Motion.tsx client leaf (Tier 2) when the user explicitly wants Framer. Never mix motion.div and layout div in one file.

Fill skills.sh gaps: outcomes on detail, full markdown, create page, guidelines, skeletons, URL pagination, no fake install counts.

Data: data-source.md.