Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Playbook

Listed
austintgriffith·vlatest·frontend

Automates frontend development tasks like component generation and style guide updates based on a defined playbook.

Repository

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 austintgriffith/ethskills --skill frontend-playbook --full-depth -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

austintgriffith

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.vercel.com, myapp.yourname.eth.link.

    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.

    Hosts contacted

    api.vercel.comundeclaredmyapp.yourname.eth.linkundeclared

    What it found

    • frontend-playbook/SKILL.md:184contacts api.vercel.com
      curl -X PATCH "https://api.vercel.com/v9/projects/PROJECT_ID" \
    • frontend-playbook/SKILL.md:243contacts myapp.yourname.eth.link
      curl -s -o /dev/null -w "%{http_code}" -L "https://myapp.yourname.eth.link"
    • frontend-playbook/SKILL.md:246contacts myapp.yourname.eth.link
      curl -s -L "https://myapp.yourname.eth.link" | grep 'og:image'

  • 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 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 austintgriffith/ethskills at 06ea4efa08.

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

Commit
06ea4efa08
Manifest
frontend-playbook/SKILL.md
Scanned
1 file, 333 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

The frontend-playbook skill provides a collection of best practices and patterns for building user interfaces. It aims to improve consistency, maintainability, and overall quality in frontend development projects. This includes guidance on component structure, styling approaches, and common UI interactions.

When to use it

  • New Project Setup: To establish a solid foundation with pre-defined conventions from the start.
  • Codebase Refactoring: To standardize existing code and improve its readability and maintainability.
  • Onboarding New Developers: As a resource for new team members to quickly understand project coding standards.
  • Addressing UI Inconsistencies: To resolve discrepancies in styling or component behavior across different parts of an application.

Key capabilities

  • Component structure guidelines
  • Styling approaches and best practices
  • Common UI interaction patterns
  • Codebase standardization

Example prompts

  • "Show me the recommended folder structure for a new React component."
  • "What's the preferred method for handling CSS in this project?"
  • "How should I implement a modal dialog box according to the playbook?"

Tips & gotchas

The frontend-playbook assumes some familiarity with frontend development concepts and technologies. It’s most effective when used as a guiding resource rather than a strict set of rules, allowing for flexibility within established boundaries.