frontend▌

A practical framework for managing the fundamental challenge of software engineering: complexity. Apply these principles when designing modules, reviewing APIs, refactoring code, or advising on architecture decisions. The central thesis is that complexity is the root cause of most software problems, and managing it requires deliberate, strategic thinking at every level of design.

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

CSS-first design system framework for Tailwind v4 with tokens, components, and responsive patterns. \n \n Migrates configuration from tailwind.config.ts to CSS @theme blocks with native CSS variables, OKLCH color spaces, and @custom-variant for dark mode \n Provides production-ready component patterns including CVA-based variants, compound components, form controls, grids, and animations using native @keyframes and @starting-style \n Includes design token hierarchy (brand → semantic → component)

React patterns for hooks, effects, refs, and component design with escape hatch guidance. \n \n Effects synchronize with external systems only (WebSocket, third-party libraries, browser APIs); most component logic should avoid Effects entirely \n Common anti-patterns: derived state, expensive calculations, prop-change resets, and event handling all belong outside Effects—use render calculations, useMemo, key props, and event handlers instead \n Effect dependencies must never be suppressed; use u

$22

This skill enables conversion from Markdown or HTML to professional PowerPoint presentations using Marp (Markdown Presentation Ecosystem). Create beautiful, consistent slides using simple Markdown syntax with CSS-based themes.

You are a frontend developer documenting what data you need from backend. You describe the what, not the how. Backend owns implementation details.

End-to-end testing focused on real user behavior, minimal mocking, and avoiding component unit tests. \n \n Prioritizes E2E tests over unit tests; reserves unit tests for pure functions only \n Emphasizes accessible selectors (role-based, label-based) over CSS selectors and test IDs in E2E tests \n Recommends writing E2E tests instead of heavily mocked unit tests; suggests 3+ mocks as a signal to switch approaches \n Includes rules for test structure, selector strategy, and when to apply each te

Delegate design tasks to Gemini via ZenMux API. Gemini creates HTML page designs, SVG icons, and provides design advice.

Expert guidance for Godot's Control node system, themes, responsive layouts, and game UI patterns. \n \n Covers all major Control node types including containers (VBoxContainer, GridContainer, ScrollContainer), interactive controls (Button, TextEdit, Slider), and display nodes (Label, RichTextLabel, TextureRect) \n Provides complete theme system documentation with code examples for creating StyleBoxes, fonts, colors, and icons programmatically or as .tres resources \n Includes ready-to-use scene