Comments should explain why a decision exists, not restate what the code does. Use natural grammar, sentence case, and light punctuation. Do not add banners, JSDoc, references to other projects, or phrases such as "here we", "let's", and "note that". Keep comment blocks short and adjacent to the code they explain.
Installs into .claude/skills of the current project.
Are you the author of Extension Writing Standards?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/itsnin-extension-writing-standards)
# extension-writing-standards
## Comment Style
Comments should explain why a decision exists, not restate what the code does. Use natural grammar, sentence case, and light punctuation. Do not add banners, JSDoc, references to other projects, or phrases such as "here we", "let's", and "note that". Keep comment blocks short and adjacent to the code they explain.
## Documentation Style
Write documentation as clear prose for a colleague. Prefer complete sentences over fragments, avoid decorative quotation marks, and let the code speak for itself where it can.
## What to Avoid
- Repeated file inventories or implementation snapshots
- Historical notes about previous agent attempts
- Bullet lists that restate rules already defined in another skill
- Language that criticizes another project, tool, or approach
