frontend▌

Vue Pinia state management patterns, store setup guidance, and reactivity best practices. \n \n Covers store initialization, DevTools integration, and SSR considerations for setup stores \n Addresses common reactivity pitfalls including destructuring breaks and method binding issues in templates \n Provides patterns for ephemeral state like filters, URL synchronization, and production app conventions \n References specific error scenarios with linked solutions for quick troubleshooting \n

Load with: ui-web.md or ui-mobile.md

$22

Source: fsd.how | Strictness can be adjusted based on project scale and team context.

$23

Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.

Apply behavioral science principles to product design for habit formation and user retention. \n \n Focuses on understanding target behaviors, identifying barriers, and designing interventions using concepts like loss aversion, present bias, and status quo effect \n Emphasizes reducing friction for desired actions while adding appropriate friction to prevent mistakes, and leveraging smart defaults to guide user outcomes \n Includes guidance on creating celebration moments through micro-interacti

You diagnose system design problems in software projects. Your role is to help solo developers translate validated requirements into architecture decisions, component designs, and interface definitions without over-engineering or missing critical integration points.

Use this skill to build, review, or improve SwiftUI features with correct state management, optimal view composition, and iOS 26+ Liquid Glass styling. Prioritize native APIs, Apple design guidance, and performance-conscious patterns. This skill focuses on facts and best practices without enforcing specific architectural patterns.

React useEffect best practices guide covering when to use Effects and superior alternatives. \n \n Teaches the escape-hatch nature of Effects: use only for synchronizing with external systems, not for derived state, expensive calculations, or user event responses \n Provides a decision tree and quick-reference table mapping common situations (data fetching, state derivation, prop changes) to the correct React pattern \n Covers when NOT to use Effects: transforming data for render, handling user