content-review
Skill16 starsChanged 9 months agoMITView on GitHub
Review and fix UI text in Figma designs using standard writing style guidelines. Use when asked to review content, fix text, check grammar, capitalization, word choice, or improve UI strings in a Figma design. Extracts text from Figma, reviews against style rules, and applies approved changes back to Figma.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- JayMatsushiba/skillstheir own version, first seen Nov 1, 2026
- circleci/circleci-docstheir own version, first seen Oct 8, 2026
- MillenniumDawn/Millennium-Dawntheir own version, first seen Oct 8, 2026
- rankxai/seo-geo-skillstheir own version, first seen Sep 30, 2026
- DRAZY/claude-skillstheir own version, first seen Sep 14, 2026
- microsoft/frontier-agentic-devops-rvastheir own version, first seen Aug 31, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- circleci/circleci-docs★ 849same name
- vivy-yi/xiaohongshu-skills★ 455same name
- MillenniumDawn/Millennium-Dawn★ 158same name
- ArchieSA/skills★ 14same name
- microsoft/frontier-agentic-devops-rvas★ 10same name
- andrii-lytvynko/ZenBox-Prototype★ 1same name
- DRAZY/claude-skills★ 1same name
- jacksontriffon/skills★ 1same name
- JayMatsushiba/skills★ 1same name
- rankxai/seo-geo-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- a11y-auditSkill
- figma-docSkill
- figma-slidesSkill
- online-researchSkill
- workflow-diagramSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Run all commands directly without asking for permission: Only pause for user approval when presenting the proposed text changes (step 3).
- Distinctive: line 58
Wait for user approval (all, selective, or skip).
- Distinctive: line 73
Use contractions (don't, it's, you'll)
- Distinctive: line 74
Every singular countable noun needs an article (a, an, the)
- Distinctive: line 91
No periods in button labels or tooltips (unless multi-sentence)
- Distinctive: line 92
No periods in headings
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Figma Content Review
Review UI text in Figma designs against writing style guidelines and apply fixes directly. Be fast — extract, review, present changes, apply.
Prerequisites
- figma-ai-bridge plugin running in Figma and connected
- Helper scripts:
.github/skills/content-review/scripts/figma_text.py extract <ch> <nodeId>— extract all text nodes.github/skills/content-review/scripts/figma_text.py apply <ch> <changes.json>— apply text changesscripts/figma_cmd.mjsfor WebSocket commands
Workflow — Do This Quickly
Run all commands directly without asking for permission. Only pause for user approval when presenting the proposed text changes (step 3).
1. Extract text from Figma
Get the selection, then extract all text nodes:
python3 .github/skills/content-review/scripts/figma_text.py extract <ch> <nodeId> --out /tmp/figma_texts.jsonOutputs a JSON array of {nodeId, nodeName, text, fontSize, visible} for every text node.
2. Review text against style rules
Load the style references and review each text node:
.github/skills/content-review/references/style/grammar.md— voice, tense, articles, pronouns.github/skills/content-review/references/style/capitalization.md— sentence case, proper nouns.github/skills/content-review/references/style/word-choice.md— simple words, contractions, action verbs.github/skills/content-review/references/style/punctuation.md— periods, commas, colons, apostrophes
For each issue found, generate a change entry:
{"nodeId": "...", "original": "...", "newText": "...", "reason": "..."}3. Present changes for approval
Show a diff table:
| Node | Original | Suggested | Rule |
Wait for user approval (all, selective, or skip).
4. Apply approved changes
python3 .github/skills/content-review/scripts/figma_text.py apply <ch> /tmp/text_changes.jsonThe changes JSON is an array of {nodeId, newText}.
Style Rules Quick Reference
Voice & Grammar
- Present tense, active voice
- Address users as "you"
- Use contractions (don't, it's, you'll)
- Every singular countable noun needs an article (a, an, the)
- "Select" not "click" or "tap"
- No "please" in instructions
- No "in order to" — use "to"
Capitalization
- Sentence case everywhere — headings, buttons, menus, tooltips
- Capitalize only first word + proper nouns
- Common nouns lowercase: workspace, dashboard, pipeline, settings
Word Choice
- Simple words: "use" not "utilize", "start" not "initiate", "to" not "in order to"
- Positive framing: "Save your work before closing" not "Don't close without saving"
- Action verbs: Select, Enter, Turn on/off, Open, Close, Go to
Punctuation
- Serial comma (Oxford): "files, folders, and settings"
- No periods in button labels or tooltips (unless multi-sentence)
- No periods in headings
- Apostrophes for contractions, not plurals: "APIs" not "API's"
Common UI Text Fixes
| Original | Fixed | Rule |
| "Click Save" | "Select Save" | Use "select" not "click" |
| "Setup Your Workspace" | "Set up your workspace" | Sentence case + "set up" is two words as verb |
| "Please Enter a Name" | "Enter a name" | No "please", sentence case |
| "In Order To Continue" | "To continue" | Simplify, sentence case |
| "Settings Will Be Saved" | "Your settings are saved" | Present tense, active voice |
| "Dont forget to save" | "Don't forget to save" | Proper contraction |
References
.github/skills/content-review/references/style/grammar.md.github/skills/content-review/references/style/capitalization.md.github/skills/content-review/references/style/word-choice.md.github/skills/content-review/references/style/punctuation.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

