Best Practices
ListedEnsures consistent, high-quality frontend code adhering to Davila7's established style guides and best practices for maintainability.
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 davila7/claude-code-templates --skill best-practices -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
davila7
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 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 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: polyfill.io.
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
polyfill.ioundeclaredWhat it found
- cli-tool/components/skills/development/best-practices/SKILL.md:240contacts polyfill.io
<script src="https://polyfill.io/v3/polyfill.min.js?features=fetch,IntersectionObserver"></script>
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 davila7/claude-code-templates at 79182c51fb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 79182c51fb
- Scanned
- 1 file, 524 lines
About this skill
The davila7-best-practices skill provides a curated set of coding standards and architectural guidelines specifically designed for frontend development workflows. It helps AI agents generate cleaner, more maintainable code by enforcing consistent patterns across HTML, CSS, and JavaScript implementations.
When to use it
- Refactoring legacy frontend codebases to align with modern industry standards.
- Generating new components that adhere to a specific team's style guide automatically.
- Auditing existing projects for common pitfalls like inconsistent naming conventions or lack of accessibility features.
- Onboarding AI agents into a project environment where strict adherence to established best practices is required.
Key capabilities
- Enforces consistent frontend coding standards across different file types.
- Promotes maintainable architecture patterns suitable for scalable applications.
- Integrates directly into Claude Code templates for immediate application during generation.
- Covers essential frontend disciplines including structure, styling, and logic organization.
Example prompts
- "Apply the davila7-best-practices template to refactor this React component for better performance."
- "Generate a new landing page section using davila7-best-practices guidelines for CSS and HTML."
- "Audit my existing JavaScript module against the davila7 best practices and list necessary changes."
Tips & gotchas
This skill is optimized for frontend contexts; ensure your project files are accessible before requesting refactoring. While it enforces strong standards, complex legacy systems may require manual overrides to accommodate unique business logic constraints.