@julianoczkowski

frontend-design provides concrete aesthetic philosophies (Rams, Swiss, Japanese, Brutalist, Scandinavian, Art Deco, Memphis, Editorial) paired with implementation checklists for codebase exploration, typography pairing, color strategy, and mobile-first composition. emphasizes context-driven design decisions over generic patterns.

information-architecture defines the structural skeleton of a product or site, sitting between design brief and build. it interviews users about navigation depth, content growth, and user types, then produces a documented ia with sitemap, navigation model, content hierarchy, flows, naming conventions, and url strategy.

design-flow orchestrates a seven-phase guided workflow from requirements gathering through frontend build and optional review. it sequences dependent skills and manages state across phases, but lacks explicit failure handling and assumes all upstream skills exist and function correctly.

brief-to-tasks converts design briefs into ordered vertical-slice task lists with dependency tracking and component reuse classification. output is a markdown checklist saved to the design folder for structured feature planning.

design-tokens generates foundational design token files (css variables or tailwind config) for a project, scanning existing code for framework dependencies and theme patterns before outputting light/dark mode palettes and spacing scales.

grill-me conducts iterative design interviews by asking probing questions about plans until reaching shared understanding, with optional codebase examination to reduce unnecessary queries.

Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use…

Run a structured design critique against the brief and codebase. Checks visual hierarchy, consistency, responsiveness, accessibility, and aesthetic fidelity.…