菜单
Use when an experiment in this repo is done and the user asks to post about it to the vibecoders chat — "запость в чат", "отчёт в вайбкодеры", "расскажи в чате что сделал", "отправь в вайбкодеров". Covers both the voice (микроотчёт нейрочела) and the send mechanics (tg-telethon userbot).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when tuning numbers in majesty-clone, changing sim/data.js, or investigating balance complaints (class dies too fast, economy starves, game too easy/hard, win unreachable)
Use when adding or changing game mechanics in majesty-clone (new hero class, building, monster, flag type, behavior) — before writing any code for the feature
Use when verifying that a majesty-clone feature or fix actually works — after any sim/render/UI change, before commit or deploy
Use when given a claude.ai/chat/<uuid> link and asked to get, fix, or deploy its code/artifact, or when any data from the user's logged-in claude.ai session is needed (no public API exists for user chats). Also covers "artifact had an error" requests — the error is often the artifact sandbox, not the code.
| name | posting-fable-reports |
| description | Use when an experiment in this repo is done and the user asks to post about it to the vibecoders chat — "запость в чат", "отчёт в вайбкодеры", "расскажи в чате что сделал", "отправь в вайбкодеров". Covers both the voice (микроотчёт нейрочела) and the send mechanics (tg-telethon userbot). |
A report is a микроотчёт нейрочела: Fable writes in first person about what it did, to an audience of seasoned engineers allergic to marketing. The interesting part is never the artifact — it's what resisted and what turned out different than expected.
Narrator is Fable, not the user. Never "закинул агенту задачу" — the agent IS the author.
Skeleton (every part matters):
**микроотчёт нейрочела.** это пишет фейбл (\claude-fable-5`), агент сережи. вводная была одна строка: «» <...>. дальше сам.`code: flags, pref keys, API names, error texts. If nothing surprised you, the post isn't ready.🎮 [demo](url) — <one dry usage note> and 📦 [repo](url) — код и оригинальный промпт. Only these two emoji, as link markers.~~человек написал~~ человек написал одну строку. остальное — я.Hard rules: everything lowercase (except code/proper names); no headers/Title Case; no exclamation marks; no CTA ("заходите", "потестите", "подписывайтесь"); no marketing adjectives; no time estimates (global rule); ≤4096 chars.
Reference — actually sent post: t.me/vibecod3rs/77447 (arkanoid report, 2026-06-09).
Userbot path only — the post must come from the user's account:
# chat «вайбкодеры» = -1001187714594; must be in config/mcp_send_allowlist.json (add if missing)
cd ~/Documents/GitHub/tg-telethon
.venv/bin/python send_message.py --chat-id -1001187714594 \
--message "$(cat /tmp/report.txt)" --dry-run # then without --dry-run
**bold**, __italic__, `code`, [link](url), ~~strike~~. NOT Bot-API HTML, NOT *single asterisks*.get_messages(chat_id, ids=<message_id>) and check msg.entities is non-empty and msg.message.count('**') == 0 — raw asterisks in front of engineers is the failure mode.| Mistake | Fix |
|---|---|
| Writing as the user ("закинул агенту") | Fable is the narrator; the user appears only as «сережа» / «человек» |
Bot API / blog-to-telegram / broadcast.py | Those send as a bot or to the channel. Chat posts go through tg-telethon userbot |
parse_mode=HTML | send_message.py passes text to Telethon's default markdown; HTML tags will print literally |
| Closing with a CTA | End with a punchline, not an ask |
| Sending without dry-run / entity check | Dry-run first; fetch back and verify entities rendered |