so … I’ve been experimenting with an idea lately For every new session I was doing a “ritual” to get the context up to speed for development. Something like :
Session Start Before searching or coding, load context from these files in order: 1. Read .reporails/backbone.yml for the project structure 2. Read mission.md for the project purpose 3. Read docs/specs/architecture.md for project framework 4. Read config/schemas/ for data schemas …
It was somewhat okay, but I wanted to formalize this. The idea: have a context bootstrapping workflow that combines two patterns I’ve been experimenting with already: backbone.yml
- a YAML map of project topology (dirs, configs, schemas) mermaid workflows
- structured flowcharts + prose The underlying observation is: context = information + process. Read the map, follow the workflow, produce a mental model, and reduce exploration & context building tax. submitted by /u/cleverhoods
Originally posted by u/cleverhoods on r/ClaudeCode
You must log in or # to comment.