Skip to content
TrustedSkillsbeta
Back to all skills

Frontend React Best Practices

Checked
sergiodxa·vlatest·frontend·MIT

Helps with frontend development, React, best practices as part of building frontend UIs and user experiences workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sergiodxa/agent-skills --skill frontend-react-best-practices -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sergiodxa

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sergiodxa/agent-skills at 40e21b4618.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
37 files, 2,995 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides expert guidance on implementing best practices for React frontend development, including component structure, state management, performance optimization, and accessibility standards.

When to use it

  • You're building a complex React application and need advice on structuring components effectively.
  • You want to ensure your app is performant and follows modern React conventions.
  • You're preparing for code reviews or working in a team that enforces strict coding standards.
  • You need help making your UI more accessible to users with disabilities.

Key capabilities

  • Guidance on component composition and separation of concerns
  • Recommendations for state management patterns (e.g., Context API, Redux)
  • Optimization techniques like memoization and lazy loading
  • Accessibility best practices for React components

Example prompts

  • "How should I structure my React components for better maintainability?"
  • "What are the best ways to optimize performance in a large-scale React app?"
  • "Can you explain how to implement accessibility features in a React form?"

Tips & gotchas

  • Ensure your project is using a modern version of React (18 or newer) to take full advantage of recommended practices.
  • Best practices may vary based on the size and complexity of your application, so tailor advice to your specific use case.