Clarity

distill helps simplify cluttered UI design by removing noise, weak hierarchy, and redundant options so the core task is clear. Use it when a screen needs disciplined reduction, clearer priorities, and a focused simplification pass.

Clarify improves confusing UX copy, error messages, labels, onboarding steps, and instructions so users can act with less guesswork. It is useful for Technical Writing, support content, and product teams that need clearer interface text. The skill starts with context, audience, and user state before rewriting, so the result is more direct, specific, and usable.

writing-clearly-and-concisely is a reusable editing skill for rewriting prose humans will read. It helps turn wordy, vague, or AI-sounding drafts into plain, direct English for docs, READMEs, commit messages, PR descriptions, error messages, UI copy, reports, and explanations. The repo pairs Strunk-style clarity rules with practical guidance for avoiding puffed-up AI phrasing.

requirements-clarity is a structured workflow that turns vague feature requests into implementation-ready requirements. It detects missing scope, constraints, acceptance criteria, edge cases, and technical context, then asks focused questions in rounds to produce a clearer PRD-style output before coding starts.

naming-analyzer reviews variables, functions, classes, files, database fields, and API names, flagging vague or misleading identifiers and suggesting clearer, convention-aware alternatives for code review and refactoring.