tag

frontend

1,037 indexed skills · max 10 per page

skills (1037)

cc-skill-frontend-patterns

sickn33/antigravity-awesome-skills · Frontend

0

Modern frontend patterns for React, Next.js, and performant user interfaces.

chrome-extension-ui

pproenca/dot-skills · Frontend

0

Comprehensive UX/UI design guide for Chrome Extensions, optimized for Manifest V3. Contains 42 rules across 8 categories, prioritized by impact to guide extension UI development and code review.

frontend-accessibility-best-practices

sergiodxa/agent-skills · Frontend

0

Accessibility patterns for building inclusive React applications following WCAG standards. Contains 7 rules across 4 categories focused on semantic HTML, screen reader support, keyboard navigation, and user preferences.

level-design

pluginagentmarketplace/custom-plugin-game-developer · Frontend

0

Use this skill: When designing engaging levels, pacing gameplay, or creating environmental narratives.

react-email

vercel-labs/json-render · Frontend

0

React Email renderer that converts JSON specs into HTML or plain-text email output.

api-design-patterns

bobmatnyc/claude-mpm-skills · Frontend

0

Design robust, scalable APIs using proven patterns for REST, GraphQL, and gRPC with proper versioning, authentication, and error handling.

widgets-ui

inference-sh/skills · Frontend

0

Declarative UI from JSON via ui.inference.sh.

frontend-design

vudovn/antigravity-kit · Frontend

0

Philosophy: Every pixel has purpose. Restraint is luxury. User psychology drives decisions. Core Principle: THINK, don't memorize. ASK, don't assume.

nextjs-authentication

giuseppe-trisciuoglio/developer-kit · Frontend

0

Provides authentication implementation patterns for Next.js 15+ App Router using Auth.js 5 (NextAuth.js), covering the complete authentication lifecycle from initial setup to production-ready role-based access control implementations.

test-tui

openai/codex · Frontend

0

You can start and use Codex TUI to verify changes. \n Important notes: \n Start interactively.\nAlways set RUST_LOG=\"trace\" when starting the process.\nPass -c log_dir=<some_temp_dir> argument to have logs written to a specific directory to help with debugging.\nWhen sending a test message programmatically, send text first, then send Enter in a separate write (do not send text + Enter in one burst).\nUse just codex target to run - just codex -c ...

prevpage 61 / 104next