agentleFS
Sign inStart free
hamzzaqureshihamzzaqureshi/gravidex/.agents/skills/frontend-engineering/SKILL.md

frontend-engineering

Skill1 starsChanged 7 days agoMITView on GitHub

Build and maintain production-grade web applications. Covers React/Next.js component architecture, state management, render performance optimization, Three.js WebGL rendering, and Playwright UI browser verification. Use when building UI features, optimizing React components, implementing 3D WebGL scenes, or running automated post-deploy browser smoke tests.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use observability, api-design and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 3 projects that use this

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When 3D graphics or WebGL components are required, follow Three.js lifecycle management (scene setup, geometry disposal, 60fps render loop).

    line 42
  2. Distinctive:

    Run automated smoke checks using Playwright/browser automation.

    line 46
  3. Distinctive:

    Verify console errors, accessibility trees (axe-core), form flows, and responsive layouts across mobile, tablet, and desktop viewports.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Frontend Engineering

Consolidated engineering capability for building, optimizing, and verifying production web applications across React, Next.js, WebGL, and browser automation.

When to Activate

  • Implementing React, Next.js, or TypeScript frontend components.
  • Designing component state architecture, client-side caching, and render lifecycles.
  • Profiling and eliminating frontend performance bottlenecks (re-renders, bundle size, Core Web Vitals).
  • Implementing 3D WebGL scenes, shaders, kinetic typography, or interactive backgrounds.
  • Running post-deploy automated browser verification (smoke tests, visual regression, form verification).

When NOT to Activate

  • Pure visual interface design and artistic exploration (use interface-design).
  • Constructing design tokens, color harmonies, or logo marks (use design-systems).
  • Backend API route handler development or database schema design (use backend-engineering).

Core Execution Workflow

  1. Architecture & State Design:
    • Organize components by domain/feature, maintaining small, cohesive files (<400 lines).
    • Enforce immutability: create new state objects, never mutate existing ones in place.
    • Separate server components (data fetching) from client components (interactivity) in Next.js App Router.
    • Consult references/component-architecture.md.
  2. Render & Performance Optimization:
    • Optimize bundle splitting, memoization, and lazy loading for high Core Web Vitals (LCP < 2.5s, CLS < 0.1, INP < 200ms).
    • Prevent unnecessary re-renders through selective context splitting and stable callbacks.
    • Consult references/render-optimization.md.
  3. Interactive 3D & WebGL Integration:
    • When 3D graphics or WebGL components are required, follow Three.js lifecycle management (scene setup, geometry disposal, 60fps render loop).
    • Consult references/threejs-webgl-patterns.md.
  4. Automated Browser UI Verification:
    • Run automated smoke checks using Playwright/browser automation.
    • Verify console errors, accessibility trees (axe-core), form flows, and responsive layouts across mobile, tablet, and desktop viewports.
    • Consult references/browser-verification-qa.md.

Modular Reference Directory

Reference ModulePrimary FocusSource Provenance
component-architecture.mdReact/Next.js patterns, hooks, state machines, props designaffaan-m/ECC (frontend-patterns)
render-optimization.mdVirtualization, memoization, image optimization, Core Web Vitalsaffaan-m/ECC (frontend-patterns)
threejs-webgl-patterns.md104 Three.js components, shaders, kinetic typography, WebGL lifecyclehamzzaqureshi/gravidex (threeui)
browser-verification-qa.mdPlaywright UI smoke tests, visual regression, console error auditsaffaan-m/ECC (browser-qa)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free