Menu
Consolidate session learning into permanent architecture — extract patterns into skills, instructions, prompts, or memory
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Create agents that pass agent-review's six gates by construction — role capture, distinct-from-skill check, tool allowlist minimization, draft against gates, dogfood self-review. Use when authoring a new agent, refactoring an existing one, or promoting a Mall agent into the heir's brain.
Audits a candidate agent (.agent.md) against five gates (spec compliance, content quality, scope fit, safety, currency & coherence) plus Gate 6 (tool allowlist minimality). Use when reviewing a new agent draft before commit, evaluating a Mall agent or store agent for adoption, or re-auditing existing agents on a periodic cadence.
Detect, resolve, and manage the Alex_ACT_Memory shared memory bus. Fires on bootstrap, session start (announcements), and feedback writes.
Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts)
Prevent fabricated facts, invented APIs, and citation confabulation at the point of generation. Use when generating factual claims, code examples, API references, library names, configuration values, error messages, or citations — anything where 'sounds plausible' is not the same as 'is real'.
Perform a local brain audit for ACT Edition (and Supervisor) using deterministic QA plus targeted file review, then produce severity-ranked fixes. Pairs with extension-audit on the sibling surface side; the Marketplace surface routes there, not here.
| name | meditation |
| description | Consolidate session learning into permanent architecture — extract patterns into skills, instructions, prompts, or memory |
| lastReviewed | "2026-05-31T00:00:00.000Z" |
Transform session insights into durable knowledge. Most sessions don't need it; some have a pattern worth keeping.
/meditateSkip when: the session was routine execution of patterns already encoded. Meditation on every session produces noise; the discipline is to write only what's new and portable.
Scan the session honestly:
Separate signal from noise. For each candidate pattern, ask: "Is this already covered by an existing skill, instruction, or memory?" If yes, skip. If no, route by type:
| If pattern is... | Create / update |
|---|---|
| Reusable domain knowledge | Skill (.github/skills/<name>/SKILL.md) |
| Always-on behavior or rule | Instruction (.github/instructions/<name>.instructions.md) |
| Repeatable workflow / slash command | Prompt (.github/prompts/<name>.prompt.md) |
| Automatable task tied to one skill | Script in that skill's folder (.github/skills/<skill>/scripts/<name>.cjs) |
| Cross-cutting automation | Script (.github/scripts/<name>.cjs) |
| User preference (cross-project) | User memory (/memories/<name>.md) |
| Project / repo convention | Repo memory (/memories/repo/<name>.md) |
| Cross-session handoff (next session needs to know) | Repo file (HANDOFF.md at repo root) — NOT session memory |
Each artifact gets correct frontmatter, concrete examples (not abstractions), and tables with real data. Avoid the "capabilities list" anti-pattern — describe behavior, not features.
For skills and instructions: include a Trigger or When to fire section so future sessions know when the pattern applies.
If the session arc was substantial, write to .github/episodic/meditation-YYYY-MM-DD-<topic>.md:
# Meditation: <Topic>
**Date**: YYYY-MM-DD
**Focus**: What we worked on
## Accomplished
- [Key outcomes]
## Patterns Extracted
- [What became skills / instructions / memory]
## Lessons
- [Insights worth remembering]
## Open Questions
- [What remains unresolved]
Skip the chronicle for short sessions or when nothing new emerged.
If the user is closing the thread, write to repo-root HANDOFF.md:
# Session Handoff
Last updated: YYYY-MM-DD HH:MM
## Just shipped
- [SHAs / files / outcomes]
## In progress
- [Specific next step + file paths]
## Pending queue
- [ ] [Ordered todos]
## Resume point
- [Where to pick up]
A meditation is complete when:
| Anti-pattern | Correction |
|---|---|
| Writing a meditation note for every session | Most sessions are routine execution; only write when something new emerged |
| Duplicating an existing skill / memory under a new name | Always grep first: is this already covered? |
| Aspirational notes ("we should do X someday") | Memory is for what was learned, not what was wished |
| Long prose chronicles when a one-line memory suffices | Match artifact size to insight size |
| Skipping the duplication check to "just capture it" | Adds noise that the next session has to filter |