From simpleapps
Writing standards for code comments, documentation, specs, PRDs, and team communication. Applies RFC 2119 requirement language and token-efficient writing.
npx claudepluginhub simpleapps-com/augur-skills --plugin simpleappsThis skill uses the workspace's default tool permissions.
Apply these standards to all written output: code comments, docs, specs, PRDs, wiki pages, commit messages, and team communication.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Apply these standards to all written output: code comments, docs, specs, PRDs, wiki pages, commit messages, and team communication.
Spec: https://www.rfc-editor.org/rfc/rfc2119
Use ALL CAPS when invoking requirement levels:
Use lowercase for casual suggestions: "you should consider..." vs "you SHOULD implement..."
Decision framework: Does the system break without it? → MUST. Degrades? → SHOULD. No impact? → MAY.
In CLAUDE.md and skill instructions, use "YOU MUST" or "IMPORTANT" as emphasis markers to improve adherence to critical rules.
Every token costs time, money, and cognitive load. Be concise without losing clarity.
Rules:
auth.ts:45 not "authentication file line 45"By audience:
By format:
When to expand:
When to cut:
Default to brief. Expand only when the reader cannot infer meaning from context. Two sentences that answer the question beat two pages that fill the context window.
Lists with no inherent order (deny rules, config arrays, feature lists, bullet-point explanations) MUST be sorted alphabetically. Alphabetical order makes items easier to find and minimizes git diffs — new entries slot into a predictable position instead of appending at the end.
Applies to JSON arrays, markdown bullet lists, table rows, and any unordered collection.
Use descriptive variable and function names. Abbreviations save keystrokes but cost readability — the human reviewing your output MUST be able to understand the code without deciphering names.
$groupQuantity not $gq, cartItem not cii, j, k) and well-known abbreviations (id, url, db) are finecalculateShippingCost not calcShipThinking trigger words (think, think hard, ultrathink) are deprecated. Extended thinking is on by default. Use /effort (low/medium/high/max) for control.