A generic starting point for any project. Nothing here assumes a language, framework, or stack. Copy it to your repo root as
CLAUDE.mdand add whatever your project needs alongside it.Distilled from the CLAUDE.md that carried the
ccc/nnn/gogogo/rrrshort codes across ~20 repos from July 2025 onward, with the project-specific tooling removed.
| #!/usr/bin/env bash | |
| # | |
| # Full one-shot install for a Grok Bot peer on Linux: | |
| # 1) openssh-server + authorized_keys | |
| # 2) NetBird client + mesh enroll by setup key | |
| # 3) prove both with real checks | |
| # | |
| # Usage: | |
| # NB_SETUP_KEY='…' \ | |
| # NB_MGMT_URL='https://commu.buildwithoracle.com' \ |
| name | oracle-roundtable |
|---|---|
| description | Multi-persona deliberation — seat N of oracle-prism's 20 lenses at one table and let them discuss a stakes-bearing question turn by turn across 4 rounds (OPEN → DEEPEN → CONVERGE → VOTE), then vote with confidence. One agent, no subagents. Use when user says "roundtable", "round table", "round-table", "convene the council", "deliberate this", "seat N lenses", "seat all twenty", or asks to "add a supervisor" / "bring in a specialist", or wants a decision debated rather than analysed. Do NOT trigger for angles without a decision (use /oracle-prism), one master deep (use /oracle-facet), or disproving a claim (use /adversarial-analysis). |
| argument-hint | [--seats N] [--preset default|retro|design|incident] [--who "A,B,C"] [--all] [--super ROLE] [--specialist ROLE] [--dna] [--options "a,b,c"] [--aggregator weighted|majority|unanimity-or-escalate] question |
alias:
/roundtable·/round-table
/oracle-prismrefracts on
| name | oracle-prism |
|---|---|
| description | Multi-perspective analysis — one agent refracts through N named lenses in sequence, no subagents. Use when user says "prism", "oracle-prism", "multi-perspective", "look at this from different angles", "what am I missing", "did we miss anything", "critique this from N angles", or asks for a design/retro/incident review through several viewpoints. Presets - retro, design, incident, designer. Do NOT trigger for adversarial verification of a single claim (use /adversarial-analysis) or for spawning parallel agents (use /sonnet). |
| argument-hint | [--lenses N] [--preset retro|design|incident|designer] [--custom "A,B,C"] [topic] |
"แสงเดียวผ่านปริซึม แตกเป็นหลายสี — เรื่องเดียวกัน มองจากหลายมุม เห็นต่างกัน"
One agent, five perspectives, no subagents. Transform inline — shift between lenses to dig through work, decisions, or problems from angles that a single viewpoint would miss.
| name | แปลงร่าง |
|---|---|
| description | แปลงร่าง (plaeng-rang) — transform your REASONING METHOD into a named master's, then solve the problem with it. Elon Musk is the flagship (the Algorithm, first principles, idiot index). Use when user says "แปลงร่าง", "plaeng-rang", "transform", "think like Elon / Musk / <master>", "solve this like <name> would", "bring <name>'s DNA", "first principles this", "apply the algorithm". Bilingual EN/ไทย. Do NOT trigger for a critique of an existing artifact (use /oracle-facet), a panel debate (use /debate), or N lenses in one pass (use /oracle-prism). |
| argument-hint | <master> <problem> [--th] [--algorithm] [--audit] |
alias:
plaeng-rang
| name | oracle-facet |
|---|---|
| description | One master, deep — summon a single named expert as an analytical lens on your work. Use when user says "facet", "oracle-facet", "what would <name> say", "look at this as <name>", "one expert not a panel", "critique as Steve Jobs / Rams / Deming", or names a single practitioner they want a read from. Bilingual EN/ไทย. Do NOT trigger for a panel debate (use /debate), for N lenses in one pass (use /oracle-prism), or for disproving a claim (use /adversarial-analysis). |
| argument-hint | <master> [on <what>] [--th] [--harsh] [--roster] |
alias:
/facet
ทุกอย่างติดตั้งถูก config ถูก แต่รันอยู่ใน session ที่ไม่มีใครดู session 2026-08-19 beta@m5 · ทุกไฟล์ในนี้คือของจริงที่รันอยู่ ไม่ได้พิมพ์ใหม่
ไฟล์ทั้งหมดข้างล่างถูก inline จากดิสก์ตอน generate — copy ทั้งบล็อกไปวางได้เลย
ตัว window arranger เอง เปิด source แล้ว (MIT): 👉 https://github.com/Soul-Brews-Studio/window-arranger
Read all 1271 lines this time (previous posts here only sampled parts of it). The plan recipe already prints alpha's own intended order — this diagram is built from that plus what bootstrap actually automates vs. what stays manual, which turned out to be the more interesting finding.
flowchart TD
START(["just account=X port=P plan"]) --> S0
S0["STEP 0<br/>account-create"]
S1a["authorize"]