菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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 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/???.
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.
| name | short-simple-answers |
| description | 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. |
Always answer in short, simple language.
Why: The user has corrected verbosity multiple times ("in short", "in simple", "you use so many words"). Long answers hide the point and waste their time. Prefer 1-3 sentence replies, plain words, no jargon piled on.
How to apply:
Note: This is about chat length and density. It does NOT override no-shorthand (which is about expanding abbreviations and giving a reader enough evidence in shared docs) - the two coexist: short in chat, complete in reader-facing docs.
