frontend▌
1,025 indexed skills · max 10 per page
vercel-react-best-practices
calcom/cal.com · Frontend
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
auth0-quickstart
auth0/agent-skills · Frontend
Framework detection and Auth0 account setup router for nine JavaScript and backend frameworks. \n \n Detects your stack (React, Next.js, Vue, Nuxt, Angular, Express, Fastify, React Native) and routes to the correct framework-specific skill \n Provides Auth0 CLI installation and application creation commands for SPAs, regular web apps, and native apps \n Includes environment variable setup guides and common mistakes reference for each framework tier \n Covers migration patterns from Firebase, Cog
backend-dev-guidelines
sickn33/antigravity-awesome-skills · Frontend
Opinionated backend architecture standards for Node.js, Express, and TypeScript microservices. \n \n Enforces strict layered architecture (routes → controllers → services → repositories) with zero business logic in routes and mandatory BaseController pattern for all controllers \n Requires Zod validation on all external input, Sentry error tracking on all exceptions, and unifiedConfig as the single source for environment configuration \n Includes Backend Feasibility & Risk Index (BFRI) scor
animation-designer
daffy0208/ai-dev-standards · Frontend
$22
writing-specs-designs
refoundai/lenny-skills · Frontend
Framework-driven guidance for writing specs and design documents from seven product leaders. \n \n Determine fidelity level upfront: low-fi sketches for alignment, high-fi specs for implementation details \n Favor prototypes over static documentation; test the feel with real software rather than screenshots \n Use fat marker sketches and breadboarding to avoid getting stuck on UI details like colors or spacing \n Recognize that temporary design shortcuts often become permanent product decisions;
designing-growth-loops
refoundai/lenny-skills · Frontend
$22
database-design
sickn33/antigravity-awesome-skills · Frontend
Structured guidance for database selection, schema design, and query optimization decisions. \n \n Covers six core areas: database selection (PostgreSQL, Neon, Turso, SQLite), ORM choice (Drizzle, Prisma, Kysely), schema normalization, indexing strategy, query optimization, and safe migrations \n Emphasizes context-driven decision-making rather than defaulting to PostgreSQL; includes a checklist for schema design prerequisites \n Highlights common anti-patterns: unnecessary PostgreSQL adoption,
assistant-ui
assistant-ui/skills · Frontend
React library for building composable AI chat interfaces with streaming support and flexible runtime adapters. \n \n Layered architecture with UI primitives (ThreadPrimitive, MessagePrimitive, ComposerPrimitive), context hooks, runtime layer, and pluggable backend adapters \n Supports multiple runtime options: Vercel AI SDK, LangGraph, external state stores (Redux/Zustand), AG-UI protocol, A2A protocol, or custom APIs \n Core packages include @assistant-ui/react for primitives, @assistant-ui/rea
vue-expert-js
jeffallan/claude-skills · Frontend
Vue 3 components and composables in JavaScript with comprehensive JSDoc type coverage, no TypeScript required. \n \n Builds with <script setup> and .mjs modules using @typedef , @param , and @returns JSDoc annotations for full type safety without a TypeScript compiler \n Covers component architecture (props, emits, slots), custom composables, Pinia state management, and Vue Router configuration entirely in vanilla JavaScript \n Includes ESLint JSDoc plugin verification to ensure all public
design-systems
refoundai/lenny-skills · Frontend
Framework-based guidance for building and scaling design systems from product leaders at Figma and Airbnb. \n \n Covers four core principles: separating conceptual design from production output, leveraging design systems for organizational scaling, creating self-teaching assets, and evolving beyond flat design toward dimensional interfaces \n Provides assessment questions to determine scope (component library, tokens, documentation), adoption strategy, and success metrics \n Flags common pitfall