Fill the UI block of .agents/copy/pages/<slug>.md. Krug scan, Zinsser cut, Nicely Said labels. Use when микрокопи, кнопка, форма. SKIP: long-form pitch (site-copy-headlines); tokens (project-design).
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add VKirill/claude-lane-stack --skill site-copy-ux --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Site Copy Ux?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vkirill-site-copy-ux)More formats (shields.io, HTML) on the badges page.
---
name: site-copy-ux
description: "Fill the UI block of .agents/copy/pages/<slug>.md. Krug scan, Zinsser cut, Nicely Said labels. Use when микрокопи, кнопка, форма. SKIP: long-form pitch (site-copy-headlines); tokens (project-design)."
argument-hint: "[info]"
---
# Site copy — UX
Need `pages/<slug>.md`. Else headlines skill first.
Template section: `## UI (Krug)` in `page-brief.template.md`
Sources: Krug *Don’t Make Me Think*; Zinsser *On Writing Well*; Fenton/Lee *Nicely Said*.
## MUST
1. Billboard: one H1, one primary CTA, one proof. Scan, don’t essay.
2. Trunk test: page name, site name, you-are-here.
3. Button = verb + object they want (`Get the audit`, not `Submit`).
4. Cut clutter: delete the sentence, then the word. No noun stacks.
5. Write strings only under `## UI` in that page file.
6. Skip `status: locked`. Refresh `INDEX.md` after edits.
## NEVER
- Two equal primary CTAs
- “Click here” / “Learn more”
- Puzzle nav
- Color/type decisions (that is DESIGN.md)
- Rewrite `locked`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
