agentleFS
basidiocarpbasidiocarp/pileus/.claude/skills/frontend-performance/SKILL.md

frontend-performance

Skill0 starsChanged 6 months agoMITView on GitHub

Profiles and improves frontend performance.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Measure baseline: before optimizing

    line 21

“Common” is measured: kept by at least 6 in 10 of the 6 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 Performance

Contents

  • Instructions
  • Web Performance
  • React Performance
  • Quick Wins Checklist

When to Use

When profiling performance:

  1. Identify the bottleneck type: Network, rendering, memory, or compute
  2. Measure baseline before optimizing
  3. Profile with appropriate tools
  4. Apply optimizations
  5. Measure improvement

Web Performance

Core Web Vitals

# Lighthouse CLI
npx lighthouse https://yoursite.com --view

# With specific metrics
npx lighthouse https://yoursite.com --only-categories=performance

Target Metrics:

MetricGoodNeeds WorkPoor
LCP (Largest Contentful Paint)< 2.5s2.5-4s> 4s
INP (Interaction to Next Paint)< 200ms200-500ms> 500ms
CLS (Cumulative Layout Shift)< 0.10.1-0.25> 0.25

Bundle Analysis

# Next.js
ANALYZE=true npm run build

# Webpack
npx webpack-bundle-analyzer stats.json

# Vite
npx vite-bundle-visualizer

PowerShell equivalent for the Next.js example:

$env:ANALYZE='true'; npm run build

React Performance

React DevTools Profiler

  1. Install React DevTools browser extension
  2. Open DevTools → Profiler tab
  3. Click Record, interact with app, stop recording
  4. Analyze flame graph for slow components

Common React Optimizations

// 1. Memoize expensive components
const MemoizedList = React.memo(function List({ items }) {
  return items.map(item => <Item key={item.id} {...item} />);
});

function SearchResults({ query }: { query: string }) {
  const deferredQuery = useDeferredValue(query);
  const [isPending, startTransition] = useTransition();

  const onSortChange = (nextSort: string) => {
    startTransition(() => setSort(nextSort));
  };

  return (
    <Suspense fallback={<Spinner />}>
      <ResultsList query={deferredQuery} pending={isPending} onSortChange={onSortChange} />
    </Suspense>
  );
}

Quick Wins Checklist

  • Enable gzip/brotli compression
  • Add caching headers
  • Lazy load images (loading="lazy")
  • Preconnect to external domains
  • Use CDN for static assets
  • Minimize JavaScript bundle
  • Defer non-critical JS
  • Optimize images (WebP, proper sizing)

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.