Documentation
Guides

Day-to-day use

Use mini-trellis when previous decisions matter, and record conclusions that will help a later change. The examples below follow one callback fix from lookup to reuse.

Look up the existing rule

mini-trellis mem recall "callback idempotency"

Read the source and its conditions. Expand a returned reference when the excerpt is missing context:

mini-trellis mem read "<ref-from-recall>"

If nothing matches, inspect the current code and relevant documentation. Search guidance explains source coverage and warnings.

Make and verify the change

Implement the fix with your usual tools. Keep the test result and any new conclusion that a future change should use. For example: repeated callbacks return the first result, and a regression test now covers duplicate delivery.

Save the conclusion

Update the existing callback spec with the confirmed idempotency rule.
Add the rejected approach and its reason to the research note.
Use mini-trellis-remember to record the changed files, verification result,
and links to these topics.

Check the actual topic and journal. The topic holds the current explanation; the journal records this session’s changes and verification. New installations leave Git commits to you.

Keep the project description current

Update the relevant section of the existing README, docs page, or spec. Check implemented behavior against current code or tests. Put agreed future work in a clearly identified section. Keep the file’s original language, and update paths or symbol names affected by a rename.

A formatting change or rename can be handled as a normal documentation edit. Use a journal entry when the work adds knowledge worth finding later. See writing and updating knowledge.

Reuse it in the next session

Use the project's recorded callback rule to add a retry-limit test.
Find the current note with mini-trellis mem recall, read its conditions,
and use that source in the implementation.

When the rule changes, update the topic before recording the new decision. A new session should retrieve the revised text and its source.

OpenCode V1 and V2 setup

CodeBuddy CLI and IDE setup

Pi / OMP setup

Kiro setup

Upgrade and refresh

ZCode setup

Cursor setup

Organize selected history

After compact

Troubleshooting

Search documentation