wait-what-bro
Re-pitch the previous answer in plain language when it did not land. User-invoked: /wait-what-bro, «wait what», «я не понял», «объясни проще». Shorter and clearer, zero jargon, zero analogies.
- License 许可
- MIT
- 最近更新
- 2026-08-25
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- wait-what-bro
- description
- Re-pitch the previous answer in plain language when it did not land. User-invoked: /wait-what-bro, «wait what», «я не понял», «объясни проще». Shorter and clearer, zero jargon, zero analogies.
02 资源文件 1
- 参考文档agents/openai.yaml382 B
03 SKILL.md 正文
Wait What Bro
Comprehension failed. Back up and re-pitch that — decide yourself how far back to go, because what lost the user is usually bigger than the last paragraph.
- Open with just enough context to place the subject and the current state of the work.
- Reply in the language of the user's last message. Keep commands, code, paths, and names as exact literals.
- Plain words, active voice, short concrete sentences. No analogies. No jargon, acronyms, or invented terms without a plain definition right where they appear. No filler and no performed slang.
- Structure the answer around three things: what happened or where the work stands, what it means for the user, what step or decision comes next.
- Shorter than the original answer, without losing constraints, risks, or verified facts. Talk like one person to another — no condescension.
- Use only the context already in the conversation. No tool calls, no file reads, no invented facts, no continuing the original work unless separately asked. If something important is missing, say so.
Done when the answer reads clearly on the first pass, contains no undefined terms, and is written in the user's language.
04 同仓库更多 Skills
writing-for-agents
Use for delegate_task, Kanban, and all agent-facing text.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
vue-best-practices
Use for Vue 3, .vue files, Vue Router, or Pinia. Skip when the repo has no Vue.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
tailwind-v4
Use when writing or reviewing Tailwind CSS v4 classes or migrating v3 syntax.
react-best-practices
Mastra React subset only. Generic React or Next uses vercel-react-best-practices.