Loading...
Loading...
Found 71 Skills
Prevent and remove generic AI-generated design defaults, incoherent visual choices, and established UI defects while creating, revising, or reviewing websites, apps, screenshots, mockups, and design code. Use as a passive quality gate during UI work or for an explicit anti-slop cleanup; preserve the chosen art direction instead of forcing a neutral redesign.
Use when designing module boundaries, planning refactors, or reviewing architecture in Python codebases. Also use when facing tangled dependencies, god classes, deep inheritance hierarchies, unclear ownership, or risky structural changes.
Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.
Read-only whole-project deep audit — architecture and module boundaries, documentation-vs-code fidelity, design-principle adherence (YAGNI/KISS/SOLID), and extensibility (how easily someone builds from source and adds a new provider/plugin/adapter) — producing a prioritized report with a SHIP / FIX / BLOCK verdict. Framework- and language-agnostic. Use when the user asks to 'audit/analyze the architecture', 'review the whole codebase design', 'does the code match the README/docs', 'how hard is it to add a new X', 'is this codebase ready to build on', or 'проведи глубокий анализ проекта', 'оцени архитектуру', 'соответствует ли код документации'. Do not use for a single diff/PR (use awesome-code-review), a named vulnerability (awesome-security-audit), runtime latency/memory (awesome-performance-audit), public-client disclosure (awesome-leak-audit), comment/naming cleanup (awesome-code-cleanup), or design-stage shaping of a new system or API (awesome-design-doc, awesome-api-design).
Always-on UX advisor that surfaces relevant Laws of UX when building or modifying UI components. Proactively activates when creating, editing, or reviewing any user interface — components, layouts, navigation, forms, interactions, or visual design. Covers 30 laws across decision-making, cognition, visual organization, memory, engagement, and design principles.
Web graphic design for interfaces, layouts, and visual systems. Use when designing landing pages, dashboards, hero sections, or applying design aesthetics (Bauhaus, Pop Art, Retro, Futuristic). Triggers on "design a", "visual design", "landing page", "color palette", "typography".
Surface interface quality concerns. Works on code, screenshots, specs, or plans.
Analyze a design against all 10 Refactoring UI skills and generate a comprehensive assessment with specific fixes
Audits code for SOLID principle violations — Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Identifies classes and methods that violate these principles and generates fix prompts. Trigger phrases: "SOLID check", "solid review", "SRP violation", "dependency inversion".
Determine what UI element draws attention first, second, third using size, weight, color, and de-emphasis strategies
Apply TypeScript design standards when creating or refactoring functions, methods, classes, modules, or shared contracts (interfaces, types, enums). Trigger for: typing decisions, domain modeling, architecture design (boundaries, DI, composition, API design), and design principles (SOLID, GoF, KISS, YAGNI, LIFT).
Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements. Use when making design decisions not covered by a specific design system, validating principle compliance, or resolving conflicts between aesthetics and accessibility. Design-system-agnostic and applies to every surface.