Frontend Dev Guidelines

Name: Frontend Dev Guidelines
Author: poletron

Checked

poletron·vlatest·frontend·CC0-1.0

Helps with frontend development, guidelines as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

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

Run this in your project

terminal

$ npx skills add odjaramillo/custom-rules --skill frontend-dev-guidelines -a claude-code

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

poletron

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 30 Sept 2026

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 poletron/custom-rules at aba6668777.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: aba6668777
Manifest: registry/skills/frontend-dev-guidelines/SKILL.md
Scanned: 22 files, 10,330 lines
Copies in repo: 2 — 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, poletron-frontend-dev-guidelines, provides a set of frontend development guidelines. It aims to ensure consistency and quality in frontend codebases. The specific details of these guidelines are not provided in the source material but can be assumed to cover aspects like coding style, component structure, and accessibility best practices.

When to use it

When onboarding new frontend developers to a project.
During code reviews to enforce consistent standards.
To automatically format or lint frontend code.
When creating documentation for frontend development processes.
To ensure adherence to established coding conventions within a team.

Key capabilities

Provides frontend development guidelines.
Aims to improve codebase consistency and quality.

Example prompts

"Generate a list of recommended JavaScript linting rules."
"Explain the preferred method for structuring React components in this project."
“What are the accessibility best practices I should follow when building forms?”

Tips & gotchas

The specific guidelines enforced by this skill are not detailed. It's crucial to understand the exact rules and conventions implemented within the skill before relying on it for automated code formatting or review.