skeleton-skills

Examines a /design folder in the project to extract the visual identity and generate a construction manual (DESIGN_SYSTEM.md) that enables creating new views from scratch with the same style and technical stack. Use this skill when the user wants to analyze mockups, HTML views, or screenshots to extract visual patterns, create style guides, document a design system, or unify visual identity. Also when they mention /design folders, screen.png, mockups, or say "review my designs", "follow this style", "make me a view like this", or "create a new screen for my project". It's not just documentation — it's the recipe to replicate the design.

Use at the start of every conversation. Loads CLAUDE.md + ARCHITECTURE.md for the target repo and routes intent to the appropriate skeleton:* skill.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Follows 4 systematic phases (reproduce, root cause, hypothesis, fix) with stack-specific tools for Laravel and Next.js.

Use before any new feature or module. Explores requirements, injects architecture constraints, proposes design, and creates an atomic TDD implementation plan — all in one pass. Replaces brainstorming + planning.

Use when implementation is complete and verified. Handles multi-repo commit/push/PR with backend-first ordering.