Loading...
Loading...
Found 148 Skills
Create or update a DESIGN.md from an existing product repository or public website. Use when asked to document an interface's design language, reconstruct its visual system, extract design tokens and guidance from current evidence, or give coding agents persistent UI context. Do not modify product source or promote accidental implementation patterns into design decisions.
Проверить, понятно ли пользователю, что произошло после действия, и предусмотрены ли состояния загрузки, пустоты и ошибки. Использовать при реализации сохранения, копирования, удаления, отправки, загрузки и синхронизации; при создании экранов с асинхронными данными; и при разборе интерфейса, который кажется неотзывчивым или непонятным. Не использовать для визуальной полировки и эстетики.
freeCodeCamp's "Command-line Chic" UI design system and aesthetic guidelines. Apply these rules whenever building, styling, or reviewing any UI that should look and feel like a freeCodeCamp product — web apps, dashboards, landing pages, admin tools, component libraries, or themes. Use this skill when the user mentions freeCodeCamp styling, fCC design, "Command-line Chic", dark theme development for fCC, or asks for a UI that follows freeCodeCamp's visual identity. Also use when working on any freeCodeCamp repository, contributing to freeCodeCamp projects, or building tools and dashboards for freeCodeCamp staff, even if the user doesn't explicitly mention the design system.
Reviews UI/frontend code and tells you exactly why it "looks AI-generated" — then how to fix it. Use it when a React/Tailwind/HTML interface looks off, generic, or unfinished, when you want a design score before shipping, or when asked to make UI look more professional, polished, or "designed, not generated." Self-contained; based on the open-source StyleSeed design engine.