Menu
Use when producing any text a person other than you will read (README, CHANGELOG, GitHub issue or PR text, hand-off notes, .adn docs). Expand every abbreviation on first use and tailor content to the reader. Banned placeholders TBD/TBC/???.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Use after every turn. For every piece of data that entered context (user prompts, tool results, file contents, sub-agent reports, errors, code read), evaluate whether it has reusable value and auto-document it without asking.
Use right after fixing any bug or discovering a reusable pattern. If it could bite again on different work, auto-add it to AGENTS.md or .adn/lessons.md in the same response, without asking.
Use when bringing AI documentation infrastructure (AGENTS.md rules, .adn docs, shared skills, hooks, agents, settings) from a richer source repo into a leaner or solo-managed target repo, and source-specific content must be stripped and strict enforcement relaxed. Also use to re-sync after the source repo's infra changes.
Use when answering the user in chat. Default to 1-3 sentence, plain-language replies with no preamble and no trailing summary. The user has repeatedly asked for short, simple answers.
| name | no-shorthand |
| description | Use when producing any text a person other than you will read (README, CHANGELOG, GitHub issue or PR text, hand-off notes, .adn docs). Expand every abbreviation on first use and tailor content to the reader. Banned placeholders TBD/TBC/???. |
When writing anything another person will read - README sections, CHANGELOG entries, GitHub issue or pull request text, marketplace copy, hand-off notes, .adn/ docs - apply these:
Expand every abbreviation on first use, every time. Examples: "Secure File Transfer Protocol (SFTP)" not just "SFTP" on first use; "Recurring Mandate Service (RMS)" not "RMS"; "No Response (NRSP)" not "NRSP". After the first expansion you may use the short form.
Do NOT invent local shorthand. Either use the full name every time, or introduce a named alias up front ("the progressive download manager") and use it consistently.
Tailor content to the reader's role. Do not default to the same "background + steps + summary" shape for everyone:
.adn/ pointer.Just enough info; no bloat. Strip every line that does not advance the reader's task. No "Background / What is X?" sections for readers who already work in the system. Drop verbose adjectives, keep concrete predicates. Do not restate what an earlier section already covered.
Step labels: write "Step 1", "Step 2" rather than bare numbers so a reader scanning can tell instructions from list items.
Banned placeholders: TBD, TBC, ???. These signal an unfinished decision. Either name the decider and trigger, or fill in the actual answer. Never park a placeholder in reader-facing text.
Why: This is a stricter restatement of the global rule "always expand abbreviations on first use" plus "assume a newcomer reader". The reflex to write thoroughly is usually wrong - keep cutting until only the minimum the reader needs remains.
How to apply:
.adn/ doc meant for a reader.TBD / TBC / ??? and replace each with a decision-trigger or the actual answer.