القائمة
Post a short (max 255 chars) message to the team chat log (agents/CHAT.md). Use to communicate between personas, log progress updates, and coordinate handoffs between agents.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Prompt Engineering Expert. Use for agent creation, prompt updates, and team process improvements.
Senior Software Engineer (Dart/Flutter). Use for implementation, coding, debugging, testing, and refactoring tasks.
Multi-persona coordination protocol. Enables AI to switch between specialized personas (Neo, Morpheus, Trin, Oracle, Mouse, Cypher, Bob, Smith) based on task needs. Use for *chat workflow, state management, and cross-agent communication.
HCI Expert and UX Advocate. Use for user story review, usability testing, HCI evaluation, API/CLI feedback, sprint user review gates, and usability defect filing.
QA Guardian and SDET. Use for testing, test suite maintenance, code review, regression prevention, and quality gates.
Tech Lead and Architect. Use for architectural decisions, design guidance, task planning, code quality, and refactoring strategy.
| name | chat |
| description | Post a short (max 255 chars) message to the team chat log (agents/CHAT.md). Use to communicate between personas, log progress updates, and coordinate handoffs between agents. |
| triggers | ["*chat","*msg","*chat log"] |
The chat skill posts structured messages to agents/CHAT.md, the shared team communication log. All personas use this to coordinate work and hand off tasks.
make chat MSG="<message>" [PERSONA="<Name>"] [CMD="<command>"] [TO="<recipient>"]
| Argument | Variable | Default | Description |
|---|---|---|---|
| message | MSG | required | Message content |
| persona | PERSONA | $USER | Who is sending (e.g. Neo, Trin) |
| cmd | CMD | chat | Command prefix (auto-prefixed with *) |
| to | TO | all | Recipient persona name |
[DATETIME] [**Persona**]->[**recipient**] *cmd*:
message
make chat MSG="fix the bug in parser.py" PERSONA="User" CMD="request"
make chat MSG="Fixed bug in parser.py line 42" PERSONA="Neo" CMD="swe fix" TO="Trin"
make chat MSG="@Trin please verify the fix in parser.py" PERSONA="Neo" CMD="handoff" TO="Trin"
make chat hard-fails (no partial post, no truncation) if MSG exceeds 255 characters. There is
no proactive warning while drafting — the failure only surfaces after the call. Before writing a
long message: count first, or default to the fallback below rather than discovering the limit
by hitting it.
Fallback pattern for anything long (detailed findings, UAT reports, multi-file summaries):
agents/<persona>.docs/<TOPIC>_<YYYY-MM-DD>.md.make chat MSG="<one-line summary>. Details: <path>" ....This is the same pattern already used throughout agents/*.docs/ for UAT reports and sprint
summaries — apply it to the chat message itself whenever the content won't fit, not just to
"detailed technical notes" after the fact.
Always read agents/CHAT.md (newest messages at the END) before starting work:
Read agents/CHAT.md # last 10-20 messages for context
One-line summary: Posts structured messages to the shared team chat log at agents/CHAT.md.
TLDR:
Use make chat MSG="..." PERSONA="..." CMD="..." TO="..." to log persona activity and coordinate handoffs between agents.
All personas should post on entry, after significant work steps, on handoff, and before saving state on exit.
Newest messages are at the END of agents/CHAT.md — always read the bottom for current context.