Skip to content
This feature requires ACT Pro. Compare plans →

Compound

Capture the most valuable insights from a coding session and save them as reusable reference documents.

Terminal window
/act:workflow:compound [optional context]

Arguments (all optional):

  • Title hint: "auth middleware rewrite"
  • File paths: ai_specs/auth-plan.md
  • Work type hint: "feature", "refactor", "bug"
  1. Collects context — gathers information from the current session, optional arguments, and referenced files
  2. Extracts insights — identifies decisions, tradeoffs, patterns, and pitfalls from the session
  3. Synthesizes — creates a compact, scannable document focused on transferable learning
  4. Saves — writes to ai_docs/solutions/<category>/<slug>.md

Compound documents are organized by category:

CategoryUse for
feature-deliveryNew features shipped end-to-end
bug-fixesBugs diagnosed and resolved
refactorsCode restructuring and cleanup
performancePerformance improvements
testingTesting strategy and infrastructure
toolingBuild, CI, and developer tooling
architectureArchitectural decisions and patterns
investigationsResearch and analysis
cross-cuttingInsights spanning multiple categories

Each compound document includes:

---
title: Short descriptive title
date: 2026-03-17
work_type: feature
tags: [auth, middleware, riverpod]
confidence: high
references: [ai_specs/auth-plan.md]
---
## Summary
What was accomplished and why it matters.
## Reusable Insights
Key patterns, decisions, and lessons that transfer to future work.
## Decisions (optional)
Choices made and alternatives considered.
## Pitfalls (optional)
What went wrong and how it was resolved.
  • After completing a feature with /act:workflow:work
  • After a complex debugging session
  • After a significant refactor
  • Any time you learn something worth documenting for future sessions

Future sessions can reference compound documents for context. Instead of re-learning the same lessons, the AI starts with your accumulated insights:

  • “Last time we set up auth, we used this pattern because…”
  • “This pitfall was encountered before — here’s how to avoid it…”
  • “The team decided on this approach for these reasons…”