coding-javascript
When javascript being written or edited.
When & Why to Use This Skill
This Claude skill serves as an automated JavaScript coding assistant that enforces strict development standards and best practices. It streamlines the programming workflow by ensuring consistent syntax, mandatory metadata documentation, and optimized file management, making it an essential tool for maintaining high-quality, readable, and maintainable JavaScript codebases.
Use Cases
- Standardizing Code Quality: Automatically enforcing uniform syntax rules, such as double-quote usage and compact vertical spacing, across large-scale JavaScript projects.
- Automated Documentation & Tracking: Ensuring every function and class contains mandatory metadata headers for better version control and team collaboration tracking.
- Safe Code Refactoring: Preventing data loss during automated edits by using intelligent file collision logic that appends timestamps to new filenames.
- Legacy Code Maintenance: Preserving critical existing comments while adding new explanatory documentation to improve long-term code readability and logic transparency.
- Web Automation Integration: Prioritizing browser-based actions and efficient tool selection for seamless web-centric JavaScript development.
| name | coding-javascript |
|---|---|
| description | When javascript being written or edited. |
Javascript coding standards
Mandatory Metadata
Every function or class you touch MUST have this comment header:
// [Created-or-Modified] by [Model_Name] | YYYY-MM-DD_[Iteration]
Example: // Modified by Claude-4.5-Sonnet | 2026-01-27_01
Syntax & Style
Quotes: Enforce Double Quotes (") over Single Quotes ('). Good: x += "." Bad: x += '.' Vertical spacing: Keep vertical spacing compact (no excessive blank lines). Readability: Prioritize Readable Code over "clever" one-liners. In-line js: Prefer including from functions in .js files to in-line js, unless explicitly justified.
Comments
Preserve comments: Do NOT delete existing, still relevant comments. Comment liberally: Explain why, not just what.
Logic & Operations
File Collisions: If a file exists, append _[timestamp] to the new filename. Simplicity: Choose the simplest working solution.
Tooling Preference (Web)
Primary: browser_action (ALWAYS try this first). Fallback: Other browser tools (Only if browser_action fails).