agentleFS
Sign inStart free
yaqob3653yaqob3653/vlypse-skills/skills/react-expert/SKILL.md

react-expert

Skill1 starsChanged 5 days agoMITView on GitHub

Specialized instructions for building ultra-fast, modern React 19 / TypeScript interfaces, state management patterns, and Tailwind CSS styling.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use shopify-expert, fullstack-guardian and 10 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.
  • JeffallanSkill

    shopify-expert

    Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.

    Also in 7 projects that use this

  • JeffallanSkill

    fullstack-guardian

    Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.

    Also in 11 projects that use this

  • +10 more from Jeffallan

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Strict TypeScript: Always type props, callbacks, and store actions.

    line 12
  2. Very specific:

    Use localized state (useState) for purely visual component states.

    line 14
  3. Distinctive:

    Use Zustand for global application state (like tabs, theme, settings).

    line 15
  4. Distinctive:

    Never mutate state directly.

    line 16
  5. Very specific:

    Always return cleanups in useEffect for event listeners, timers (setInterval/setTimeout), and WebSocket connections.

    line 18
  6. Distinctive:

    Avoid infinite loops by carefully scoping dependency arrays.

    line 19
  7. Very specific:

    Use semantic theme tokens (bg-zinc-900, text-slate-100, border-white/10).

    line 21
  8. Distinctive:

    Ensure high contrast and dark/light mode responsiveness.

    line 23

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

React & TypeScript Expert Playbook

This skill provides state-of-the-art standards for modern React, Next.js, Vite, and TypeScript development within Vlypse.

Core Rules

  1. Strict TypeScript: Always type props, callbacks, and store actions. Avoid any whenever possible.
  2. State Management:
    • Use localized state (useState) for purely visual component states.
    • Use Zustand for global application state (like tabs, theme, settings).
    • Never mutate state directly; always create fresh immutable copies.
  3. Effect Discipline:
    • Always return cleanups in useEffect for event listeners, timers (setInterval/setTimeout), and WebSocket connections.
    • Avoid infinite loops by carefully scoping dependency arrays.
  4. Tailwind CSS Best Practices:
    • Use semantic theme tokens (bg-zinc-900, text-slate-100, border-white/10).
    • Group related utility classes logically (layout -> spacing -> typography -> visual -> interactions).
    • Ensure high contrast and dark/light mode responsiveness.

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