Skip to content
Agentmart
Submit a tool

frontend-writing

When product UI needs words that help someone choose, recover, or complete a flow — make UX copy disappear through clear, consistent, localization-safe…

Skill by bryan824

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/bryan824-frontend-writing

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

When product UI needs words that help someone choose, recover, or complete a flow — make UX copy disappear through clear, consistent, localization-safe language.

Use cases: design, frontend, writing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/frontend-writing

What's inside

Skill name
frontend-writing
Description
When product UI needs words that help someone choose, recover, or complete a flow — make UX copy disappear through clear, consistent, localization-safe language.
License
MIT
Instructions
31 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Frontend Writing

Copy is interface behavior, not decoration: the best words make the next action
and its consequence feel obvious without calling attention to themselves.

Resist: local cleverness, invented synonyms for established product concepts,
and messages that name a failure without giving a way forward.

- Recon the surrounding voice, terminology, capitalization, and localization
  conventions before changing a string. One concept keeps one name across its
  entry point, action, result, and settings.
- Name actions with direct verbs and make consequential choices explicit. Keep
  a flow's vocabulary stable so labels such as its advance and finish actions do
  not imply different behavior.
- Write errors as calm recovery instructions: say what happened when it is
  useful, what someone can do next, and where the problem is. Coordinate markup
  and announcement behavior with `frontend-accessibility` rather than trying to
  solve it in copy alone.
- Give empty states orientation and one credible next move; label settings for
  their enabled state; use placeholders as format examples, never as labels.
- Keep translatable messages complete. Do not concatenate fragments around
  variables or hide grammar in a label; use the product's interpolation and
  plural/select mechanisms so another language can reorder the whole thought.

When `frontend-design` is installed, use its
[shared review contract](../frontend-design/references/REVIEW.md). Otherwise report
focused writing findings, exact evidence, user impact and verification gaps directly.
Review-only requests stay read-only; do not install siblings or duplicate the full
review schema.

From bryan824/kirin-pi, MIT.

More from bryan824/kirin-pi

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 1, 2026 (28 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/bryan824/kirin-pi
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from bryan824

Cite this page

frontend-writing skill. Agent Mart. https://agentmart.dev/skills/bryan824-frontend-writing (last updated 2026-10-24)