Frontend Dev Guidelines
CheckedHelps with frontend development, guidelines 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
Run this in your project
terminal$ npx skills add mrgoonie/claudekit-skills --skill frontend-dev-guidelines -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
mrgoonie
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.
Automated safety checks
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 mrgoonie/claudekit-skills at 80113d86bc.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 80113d86bc
- Scanned
- 11 files, 5,128 lines
About this skill
What it does
This skill provides a structured framework for frontend development guidelines, ensuring consistency and best practices within web projects. It helps AI agents generate code that adheres to specific architectural standards and maintainability requirements.
When to use it
- Establishing a unified coding style across large teams or multiple microservices.
- Generating boilerplate code that automatically enforces project-specific linting rules.
- Creating documentation templates for component architecture and state management patterns.
- Refactoring legacy codebases to align with modern frontend development standards.
Key capabilities
- Defines clear architectural patterns for scalable frontend applications.
- Enforces consistent naming conventions, file structures, and directory organization.
- Integrates best practices for performance optimization and accessibility compliance.
- Supports generation of reusable component libraries with standardized interfaces.
Example prompts
- "Generate a React component following the project's frontend development guidelines."
- "Create a TypeScript utility function that adheres to our established coding standards."
- "Draft a README section explaining how new developers should structure their code using these guidelines."
Tips & gotchas
Ensure your AI agent has access to the specific style guide or configuration files referenced in the skill's context. This skill is most effective when paired with existing project documentation to avoid conflicts between custom rules and general best practices.