Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Standards

Checked
clarkkkk·vlatest·frontend

Ensures consistent UI code quality & accessibility by enforcing Clarkkkk's established frontend style guide and best practices.

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 clarkkkk/seagull --skill frontend-standards -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

clarkkkk

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 clarkkkk/seagull at 802398e838.

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

Commit
802398e838
Manifest
skills/frontend-standards/SKILL.md
Scanned
6 files, 573 lines
Copies in repo
3 — all of them scanned
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, frontend-standards, provides access to a collection of established best practices and guidelines for building user interfaces. It helps ensure consistency, accessibility, and maintainability in frontend development projects. The skill aims to improve the quality and efficiency of UI creation by leveraging existing conventions.

When to use it

  • New Project Setup: To quickly establish a baseline for code style and structure at the beginning of a new project.
  • Code Reviews: As a reference point during code reviews to ensure adherence to established standards.
  • Team Onboarding: To help new team members understand and follow consistent coding practices.
  • Refactoring Legacy Code: To guide efforts in bringing older, less structured codebases up to modern standards.

Key capabilities

  • Provides a collection of frontend best practices.
  • Offers guidelines for UI consistency.
  • Supports accessibility considerations in UI development.
  • Promotes maintainability through standardized coding conventions.

Example prompts

  • "What are the recommended naming conventions for CSS classes?"
  • "Show me examples of accessible form element implementations."
  • "How should I structure a React component file according to these standards?"

Tips & gotchas

The effectiveness of this skill depends on having a clear understanding of frontend development principles. While it provides guidelines, interpreting and applying them correctly requires some level of experience in UI design and implementation.