Interactive walkthrough for new users. Learn by doing — each step creates real content in your vault. Three tracks (researcher, manager, personal) with a universal learning arc. Triggers on "/tutorial", "walk me through", "how do I use this".
Read these files to configure domain-specific behavior:
ops/derivation-manifest.md — vocabulary mapping, platform hints
vocabulary.notes for the notes folder namevocabulary.note / vocabulary.note_plural for note type referencesvocabulary.reduce for the extraction verbvocabulary.reflect for the connection-finding verbvocabulary.topic_map for MOC referencesvocabulary.inbox for the inbox folder nameops/config.yaml — processing depth, domain context
If these files don't exist, use universal defaults.
Target: $ARGUMENTS
ops/tutorial-state.yamlcurrent_stepops/tutorial-state.yaml and start freshSTART NOW. Reference below defines the flow.
Read ops/tutorial-state.yaml. If it exists and tutorial is incomplete, display:
--=={ ars contexta : tutorial }==--
Welcome back.
Track: [track] [step-progress] Step [N] of 5
Resuming where you left off...
Skip to the saved current_step. Do NOT re-ask for track. If current_step > 5, tutorial is complete — offer to reset.
Progress indicator format:
[=> ][==> ][===> ][====> ][=====>]Display header, then use AskUserQuestion:
--=={ ars contexta : tutorial }==--
Which track fits your work best?
(a) Researcher -- academic papers, domain
research, literature processing
(b) Manager -- meeting notes, strategy docs,
decision tracking
(c) Personal -- daily observations, goal
setting, reflective journaling
Wait for response. Map a/b/c to researcher/manager/personal.
Write initial state to ops/tutorial-state.yaml: