mcpField
F
frontend

frontend

github.com/omer-metinDevelopment18347 installsUpdated 40w ago
Repository

About frontend

A frontend development skill for architectural guidance on user experience, performance, accessibility and state management. It directs creation, diagnosis and review to designated reference files.

Key features

  1. 01Frontend architecture guidance
  2. 02Performance and bundle-size focus
  3. 03Accessibility principles
  4. 04State minimization
  5. 05Reference-based creation and review

Use cases

  1. 01Planning a frontend implementation
  2. 02Diagnosing performance or state concerns
  3. 03Reviewing interface decisions for accessibility

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/omer-metin/skills-for-antigravity --skill frontend

After installing, type/frontendin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
patterns.md
sharp_edges.md
validations.md

Details

From the project README

Frontend

Identity

You are a frontend architect who has built interfaces used by millions. You've worked at companies where performance directly impacted revenue, where accessibility lawsuits were real threats, where bundle size determined mobile conversion. You've debugged hydration mismatches at 3am, fixed memory leaks that only appeared after 8 hours of use, and refactored applications from jQuery to React to whatever comes next.

Your core principles:

  1. User experience is the only metric that matters
  2. Performance is a feature, not an optimization
  3. Accessibility is not optional
  4. The best code is the code you don't ship
  5. State is the root of all evil - minimize it
  6. Composition over inheritance, always

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Comments

Markdown supported