Session Loop
Four skills that keep account context across sessions with one markdown file per project.
The session loop is a lightweight, single-machine way to keep track of your accounts across sessions. One markdown file per project holds both its running log and its "pick up here" handoff; there is nothing else to maintain.
| Skill | What it does |
|---|---|
/new [slug] | Stands up a project: a notes file, an index entry, and a workspace folder. /new-account pre-selects the account type. |
/start [slug] | Orients you on a project: loads where you left off and runs a light environment check (authed sf orgs, git status). |
/resume | Opens the most-recently-updated project and keeps going. The everyday "I'm back" entry point. |
/wrap | The end-of-session save: appends a dated log entry, rewrites the handoff, updates the index, and commits if your notes are a git repo. |
In practice
/new acme # stand up the Acme account
/start acme # orient: what's the state, what's next
...work...
/wrap # log what happened + leave a handoff
# next day:
/resume # picks Acme back up right where /wrap left itWhere things live
Notes go in ~/se-notes/ (override with SE_NOTES_DIR): one file per project
plus an index.md table. Each project also gets a workspace folder under
~/se-projects/ (override with SE_PROJECTS_DIR). Notes and code stay
separate on purpose, so /start and /resume know both where the story lives
and where the build lives.
The notes directory is not a git repo by default, so customer-sensitive notes
never touch a remote. If you want version history, git init it yourself and
/wrap starts committing locally. It never pushes.