Security & Compliancelow risk
writing-guidelines
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
nexu-io/open-design·skills/writing-guidelines/SKILL.md
59/ 100Recommendation
Install this skill
Choose your coding agent and copy a project or personal installation command.
Project installation.agents/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a codex -yPersonal installation~/.agents/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a codex -g -yProject installation.claude/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a claude-code -yPersonal installation~/.claude/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a claude-code -g -yProject installation.agents/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a github-copilot -yPersonal installation~/.copilot/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a github-copilot -g -yProject installation.agents/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a cursor -yPersonal installation~/.cursor/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a cursor -g -yProject installation.agents/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a gemini-cli -yPersonal installation~/.gemini/skills/writing-guidelines
npx skills add https://github.com/nexu-io/open-design/tree/7533db3f4342d09b27368fa5d907ebd3cdb93b75/skills/writing-guidelines -a gemini-cli -g -yNative Gemini CLI
gemini skills install https://github.com/nexu-io/open-design.git --scope workspace --path skills/writing-guidelines⚠ Installation uses the open-source skills CLI. Inspect the source and permissions before running the command.
Skill instructions
View source on GitHub ↗# Writing Guidelines Review files for compliance with Writing Guidelines. ## How It Works 1. Load the pinned guidelines from [`references/guidelines.md`](references/guidelines.md) — this is the default, reproducible execution path 2. Optionally, fetch the latest guidelines from the upstream URL below and diff against the pinned snapshot to see if anything has changed 3. Read the specified files (or prompt user for files/pattern) 4. Check against all rules in the guidelines 5. Output findings in the terse `file:line` format ## Guidelines Source **Default (pinned):** The vendored copy at [`references/guidelines.md`](references/guidelines.md) is the default execution path. It is a pinned snapshot of the upstream guidelines and guarantees the skill produces reproducible results in any runtime environment. **Upstream (live):** For users who want the very latest rules, the live source is available at: ``` https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md ``` Fetching the live version is optional — the pinned snapshot is always the baseline. ## Usage When a user provides a file or pattern argument: 1. Load [`references/guidelines.md`](references/guidelines.md) as the default source 2. Optionally fetch the upstream URL to check for updates 3. Read the specified files 4. Apply all rules from the guidelines 5. Output findings using the format specified in the guidelines If no files specified, ask the user which files to review.