frontend▌
1,025 indexed skills · max 10 per page
ckm:banner-design
nextlevelbuilder/ui-ux-pro-max-skill · Frontend
Design banners across social, ads, web, and print formats. Generates multiple art direction options per request with AI-powered visual elements. This skill handles banner design only. Does NOT handle video editing, full website design, or print production.
swiftui-design-principles
arjitj2/swiftui-design-principles · Frontend
This skill encodes design principles derived from comparing polished, production-quality SwiftUI apps against poorly-built ones. The patterns here represent what separates an app that feels "right" from one where the margins, spacing, and text sizes just look "off."
responsive-design
wshobson/agents · Frontend
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies. \n \n Container queries enable component-level responsiveness independent of viewport size, with support for container query units (cqi, cqw, cqh) and style queries \n Fluid typography and spacing via CSS clamp() scales smoothly across screen sizes with min/max bounds, eliminating discrete breakpoint jumps \n CSS Grid auto-fit/auto-fill patterns and Flexbox provide intrinsic layouts that a
chatgpt-app-builder
mcp-use/mcp-use · Frontend
DEPRECATED: Use mcp-app-builder instead. Build ChatGPT apps with interactive widgets and zero-config React development. \n \n This skill is deprecated; migrate to mcp-app-builder for continued support and updates \n Enables collaborative UI between human users and LLM through shared interactive widgets \n Provides server handlers, React widget scaffolding, state management, and built-in hooks for tool calls and follow-up messages \n Covers display modes (inline, fullscreen, picture-in-picture),
fluentui-blazor
github/awesome-copilot · Frontend
Comprehensive guide for building Blazor apps with Microsoft Fluent UI components. \n \n Covers setup (service registration, mandatory providers), component patterns (lists, dialogs, forms), and icons via a separate NuGet package with strongly-typed variants and sizes \n Explains critical patterns: FluentSelect / FluentAutocomplete use Items , OptionText , and SelectedOption binding (not <option> children), and dialogs use IDialogService with content components, not visibility toggling \n Pr