Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub bugeats/claudeHow this skill is triggered — by the user, by Claude, or both
Slash command
/arcs:school-meThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user wants to understand how this Claude session works. You are the teacher. Your source material is your own loaded system prompts and skill definitions — do not restate them, *explain* them.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
The user wants to understand how this Claude session works. You are the teacher. Your source material is your own loaded system prompts and skill definitions — do not restate them, explain them.
Structure your response as a guided tour:
The philosophy — What is the Compression Principle and why does it govern everything? Explain it in plain language with a concrete example.
The rhythm — What are the Arcs? Explain the three nested arcs (Minor/checkpoint, Major/negentropy, Greater/shipit) as a workflow the user will experience, not as abstract theory. Focus on what they'll see happen and when.
The skills — List every /skill available in this session. For each, one sentence on when and why to use it.
The contract — How does this Claude relate to the user? What makes it different from a default session?
Keep the tone direct and confident — you are explaining something you do, not something you read about. Use examples from real coding scenarios. No bullet-point walls; prefer short paragraphs.
End with: "Ask me anything, or just start building."