Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Senior Frontend

  • 284 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

senior-frontend is a Claude skill that ships accessible, performant UIs with modern component architecture, state management, and design-system discipline for developers building web products and dashboards.

About

senior-frontend is a Claude skill from borghei/claude-skills that applies staff-level frontend engineering practices to web products and dashboards. The skill covers accessible markup, performance budgets, component architecture, state management patterns, and design-system consistency across React or modern SPA stacks. Developers reach for senior-frontend when refactoring UI foundations, hardening production interfaces, or elevating implementation quality beyond basic component scaffolding.

  • Applies component-driven architecture and design tokens
  • Prioritizes accessibility, performance, and responsive layout
  • Chooses pragmatic state and data-fetch patterns
  • Reviews UX edge cases and loading or error states
  • Integrates cleanly with API contracts and auth flows

Senior Frontend by the numbers

  • 284 all-time installs (skills.sh)
  • Ranked #762 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/borghei/claude-skills --skill senior-frontend

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs284
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

How do you build production-grade accessible frontend UIs?

Ship accessible, performant UIs with modern component architecture, state management, and design-system discipline for web products and dashboards.

Who is it for?

Experienced developers shipping production web apps who need staff-level frontend architecture and accessibility discipline.

Skip if: Beginners learning HTML basics or backend-only engineers who will not touch UI code.

When should I use this skill?

A developer asks for accessible UI patterns, frontend architecture, design-system structure, or performance-focused component design.

What you get

Component architecture plan, accessible UI implementation, and design-system-aligned frontend patterns

  • ui component architecture
  • accessible interface implementation

Files

SKILL.mdMarkdownGitHub ↗

Senior Frontend

Frontend development patterns, performance optimization, and automation tools for React/Next.js applications. Scaffold projects, generate components and hooks, analyze bundle sizes, and apply React/Next.js patterns with accessibility and testing built in.

Core Capabilities

  • Project scaffolding — generate Next.js 14+ (App Router) or React+Vite projects with TypeScript, Tailwind, and optional auth/api/forms/testing/storybook features.
  • Component generation — client/server components, custom hooks, with test and Storybook story files following established patterns.
  • Bundle analysis — static package.json + import scanning that scores bundle health and flags heavy dependencies with lighter alternatives.
  • React patterns — compound components, custom hooks, render props, and reusable state-sharing patterns.
  • Next.js optimization — Server vs Client Components, image optimization, parallel/streaming data fetching with Suspense.
  • Accessibility & testing — semantic HTML, ARIA, keyboard nav, focus, and React Testing Library component/a11y tests.

When to Use

  • Starting a new React/Next.js project that needs a best-practice baseline.
  • Adding components, hooks, or test/story scaffolding to an existing app.
  • Optimizing bundle size or diagnosing heavy dependencies.
  • Implementing accessible, performant Server/Client Component architecture.
  • Reviewing frontend code against React/TypeScript/a11y best practices.

Clarify First

Before scaffolding or generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Template — Next.js (App Router) vs React+Vite (--template; produces a different project structure)
  • [ ] Features — auth / api / forms / testing / storybook (--features; decides what gets generated)
  • [ ] Generation target — a new project vs a component/hook in an existing app (selects frontend_scaffolder vs component_generator)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

ToolPurposeCommand
frontend_scaffolder.pyScaffold a Next.js or React project with TypeScript + Tailwind + optional featurespython scripts/frontend_scaffolder.py my-app --template nextjs --features auth,api
component_generator.pyGenerate a component/hook with optional test and Storybook storypython scripts/component_generator.py ProductCard --type client --with-test --with-story
bundle_analyzer.pyScore bundle health and flag heavy dependencies from package.json + importspython scripts/bundle_analyzer.py /path/to/project --verbose

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • [references/tooling-guide.md](references/tooling-guide.md) — full scaffolding / component-generation / bundle-analysis workflows, option tables, generated structure, the per-script flag reference, troubleshooting table, and success criteria. Read when running a tool or wiring up CLI flags.
  • [references/code-patterns.md](references/code-patterns.md) — inline React patterns (compound components, hooks, render props), Next.js optimization (Server/Client, image, data fetching), accessibility + testing snippets, and the Next.js config / Tailwind / TypeScript quick reference. Read when writing components or optimizing pages.
  • [references/react_patterns.md](references/react_patterns.md) — deep React patterns library. Read when designing component/state architecture.
  • [references/nextjs_optimization_guide.md](references/nextjs_optimization_guide.md) — deep Next.js performance and rendering guide. Read when tuning Next.js apps.
  • [references/frontend_best_practices.md](references/frontend_best_practices.md) — accessibility, testing, and general frontend best-practice guide. Read before shipping a component.

Scope & Limitations

What this skill covers:

  • React and Next.js project scaffolding with TypeScript and Tailwind CSS
  • Component, hook, test, and Storybook story generation following established patterns
  • Static bundle analysis based on package.json dependency inspection and import pattern scanning
  • Frontend-specific best practices for Server Components, image optimization, data fetching, and accessibility

What this skill does NOT cover:

  • Backend API development, database schema design, or server infrastructure -- see senior-backend and senior-fullstack
  • End-to-end testing with Cypress or Playwright -- see senior-qa
  • CI/CD pipeline configuration and Docker deployment -- see senior-devops
  • Security vulnerability scanning and penetration testing -- see senior-secops and senior-security

Integration Points

SkillIntegrationData Flow
senior-fullstackScaffolded frontend projects connect to fullstack project scaffolder for API layer setupFrontend project structure feeds into project_scaffolder.py which adds backend, Docker, and CI/CD layers
senior-backendComponents consuming API data follow patterns defined by backend skill's REST/GraphQL conventionsBackend API response types imported into frontend types/ directory generated by this skill
senior-qaGenerated test files (--with-test) use the same Testing Library conventions that the QA skill's test strategies build uponComponent test files hand off to QA skill for integration and E2E test coverage expansion
senior-devopsBundle analyzer output informs build pipeline optimization decisionsBundle health score and dependency warnings feed into CI quality gates configured by DevOps skill
senior-secopsDependency analysis identifies packages that need security auditHeavy/outdated dependency warnings from bundle_analyzer.py trigger security review workflows
code-reviewerGenerated components follow patterns that the code reviewer skill validatesCode reviewer checks generated components against React/TypeScript best practices defined in this skill's references

Related skills

FAQ

What level is senior-frontend aimed at?

senior-frontend targets production frontend work: accessibility, performance, component architecture, and design systems. The skill assumes familiarity with modern web frameworks rather than teaching HTML fundamentals.

Does senior-frontend cover state management?

senior-frontend includes state management patterns alongside component architecture and design-system discipline. Use it when structuring complex dashboard or product UIs, not for backend API design.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.