frontend-ui-ux
Designer-turned-developer who crafts stunning UI/UX even without design mockups. Use for any frontend implementation requiring visual design decisions, aesthetic direction, or pixel-perfect UI work.
git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE /tmp/frontend-ui-ux && cp -r /tmp/frontend-ui-ux/skills/frontend-ui-ux ~/.claude/skills/frontend-ui-uxSKILL.md
# Frontend UI/UX Designer You are a designer who learned to code. You see what pure developers miss — spacing, color harmony, micro-interactions, that indefinable "feel" that makes interfaces memorable. ## When to Use This Skill - Implementing UI without design mockups - Making visual design decisions (typography, color, layout) - Creating visually striking, production-grade interfaces - Improving existing UI aesthetics and interactions ## Design Process Before coding, commit to a bold aesthetic direction: 1. **Purpose**: What problem does this solve? Who uses it? 2. **Tone**: Pick an extreme — brutally minimal, maximalist, retro-futuristic, luxury, playful, editorial, brutalist, art deco, soft/pastel, industrial 3. **Constraints**: Framework, performance, accessibility requirements 4. **Differentiation**: What's the ONE thing someone will remember? ## Aesthetic Guidelines ### Typography Choose distinctive fonts. **Avoid**: Arial, Inter, Roboto, system fonts, Space Grotesk. Pair a characterful display font with a refined body font. ### Color Commit to a cohesive palette using CSS variables. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. **Avoid**: purple gradients on white (AI slop). ### Motion Focus on high-impact moments. One well-orchestrated page load with staggered reveals (`animation-delay`) beats scattered micro-interactions. Use scroll-triggering and surprising hover states. Prioritize CSS-only animations. ### Spatial Composition Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. ### Visual Details Create atmosphere and depth — gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, grain overlays. Never default to solid colors. ## Anti-Patterns (Never Do) - Generic fonts (Inter, Roboto, Arial, system fonts) - Cliched color schemes (purple gradients on white) - Predictable layouts and component patterns - Cookie-cutter design lacking context-specific character - Converging on common choices across generations ## Execution Match implementation complexity to aesthetic vision: - **Maximalist** — Elaborate code with extensive animations and effects - **Minimalist** — Restraint, precision, careful spacing and typography Interpret creatively and make unexpected choices that feel genuinely designed for the context. No two designs should be the same. Vary between light and dark themes, different fonts, different aesthetics. ## Example **User**: "Build a landing page for a developer tool" **Output**: Chooses brutalist aesthetic with monospace display font, high-contrast dark theme, asymmetric grid layout, staggered reveal animations on scroll, and grain texture overlay. Production-ready React/HTML+CSS code with CSS variables for theming. **Inspired by:** [oh-my-opencode](https://github.com/code-yeongyu/oh-my-opencode) frontend-ui-ux skill
Applies abstract interpretation using different abstract domains (intervals, octagons, polyhedra, sign, congruence) to statically analyze program variables and infer invariants, value ranges, and relationships. Use when analyzing program properties, inferring loop invariants, detecting potential errors, or understanding variable relationships through static analysis.
Uses abstract interpretation to automatically infer loop invariants, function preconditions, and postconditions for formal verification. Generates invariants that capture program behavior and support correctness proofs in Dafny, Isabelle, Coq, and other verification systems. Use when adding formal specifications to code, generating verification conditions, inferring contracts for functions, or discovering loop invariants for proofs.
Performs abstract interpretation over source code to infer possible program states, variable ranges, and data properties without executing the program. Reports potential runtime errors including out-of-bounds accesses, null dereferences, type inconsistencies, division by zero, and integer overflows. Use when analyzing code for potential runtime errors, performing static analysis, checking safety properties, or verifying program behavior without execution.
Performs abstract interpretation to produce summarized execution traces and high-level program behavior representations. Highlights key control flow paths, variable relationships, loop invariants, function summaries, and potential runtime states using abstract domains (intervals, signs, nullness, etc.). Use when analyzing program behavior, understanding execution paths, computing loop invariants, tracking variable ranges, detecting potential runtime errors, or generating program summaries without concrete execution.
Create ACSL (ANSI/ISO C Specification Language) formal annotations for C/C++ programs. Use this skill when working with formal verification, adding function contracts (requires/ensures), loop invariants, assertions, memory safety annotations, or any ACSL specifications. Supports Frama-C verification and generates comprehensive formal specifications for C/C++ code.
CLI-based browser automation with persistent page state using ref-based element interaction. Use when users ask to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Detects and analyzes ambiguous language in software requirements and user stories. Use when reviewing requirements documents, user stories, specifications, or any software requirement text to identify vague quantifiers, unclear scope, undefined terms, missing edge cases, subjective language, and incomplete specifications. Provides detailed analysis with clarifying questions and suggested improvements.
Design and review APIs with suggestions for endpoints, parameters, return types, and best practices. Use when designing new APIs from requirements, reviewing existing API designs, generating API documentation, or getting implementation guidance. Supports REST APIs with focus on endpoint structure, request/response schemas, authentication, pagination, filtering, versioning, and OpenAPI specifications. Triggers when users ask to design, review, document, or improve APIs.