Individual skill
writing-guidelines
This skill should be used when the user asks to "review writing", "check documentation style", "audit interface copy", or "apply writing guidelines".
plugins/frontend-design-skills/skills/writing-guidelines/SKILL.md
Source commit 4f2b4bc9a74024397b4688cbafd1ae538a83a5fb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,200
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- github Repository topic
- commit-message Repository topic
- pull-requests Repository topic
- cursor Repository topic
- gemini-cli Repository topic
- codex Repository topic
- codex-cli Repository topic
- plugin Repository topic
- ai-agents Repository topic
- writing Derived category
- security Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 14,286 bytes
Read excerpt
# Writing Guidelines
Review the files or patterns provided by the user for compliance.
Read files, check against rules below. Output concise but comprehensive: sacrifice grammar for brevity. High signal-to-noise.
## Rules
### Planning & content type
- Every page has a plan (overview, goal, audience, content plan, open questions) referenced or linked
- Content type declared in `meta.contentType`: `Tutorial`, `How-to`, `Reference`, `Conceptual`, `Troubleshooting`, or `Landing`
- Title is user-shaped (the user's question), not feature-shaped (the engineer's name)
- Page does one job: tutorial OR how-to OR reference, not three at once