Contribute an improvement back to the upstream Egregore framework as a cross-fork pull request. Use for /contribute, or submitting a framework fix upstream — not saving org work (/save) or filing a bug (/issue).
See what is happening across the team — recent sessions, handoffs, quests, and open PRs. Use for /activity, catching up after time away, or checking team-wide status at a glance.
Send an announcement to the Telegram group with a draft-then-approve flow. Use for /announce, telling the team something, or notifying everyone at once — not messaging one person or a structured handoff.
Capture an effective prompting technique or steering pattern as reusable knowledge. Use for /archive, or when a prompt worked especially well and is worth reusing — not insight about the work itself (/reflect).
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
Run diagnostics on your Egregore environment and render a health report, auto-fixing what it can. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
Use when generating or modifying any visual output that renders in a browser or artifact viewer: HTML pages, CSS, React SSR components, Egregore artifacts, markdown renderers, web components, design-system tokens, Tailwind themes, or standalone demos.…