It struck me as very similar. Just to let you know. Here is intro from the documentation: "Introduction How an eve agent is laid out as files, what runs when a message arrives, and the building blocks you add as it grows. eve is a framework for building durable agents as ordinary files in a TypeScript project. Instead of one large configuration object, each part of your agent gets a clear home. Instructions go in one file, tools in one folder, channels in another. eve discovers that structure and turns it into an agent that runs locally, serves HTTP, connects to other platforms, and keeps working across many turns." and a sample structure: my-agent/ ├── package.json └── agent/ ├── agent.ts ├── instructions.md ├── tools/ │ └── get_weather.ts ├── skills/ │ └── plan_a_trip.md └── channels/ └── slack.ts

🔍 Three things to notice. 👇 1️⃣ Numbered folders set the execution order, so 01- always runs before 02-. 2️⃣ Each stage carries its own CONTEXT.MD, references/, and output/. 3️⃣ The handoff between stages is dead simple. Stage 1's output/ is what stage 2 reads as input. ================== 📂 The folder structure workspace/ -------------------------------------------# the whole operation CLAUDE.md ------------------------------------------# L0: orientation, "where am I?" (always loaded) CONTEXT.md --------------------------------------- # L1: the map, "where do I go next?" stages/ ------------------------------------------------ # all the steps in order 01-research/ ---------------------------------------- # step 1: gather the source material CONTEXT.md ---------------------------------------# today's job description references/ ------------------------------------------# rules for this step output/ -------------------------------------------------# what this step produced 02-script/ -------------------------------------------- # step 2: turn research into a draft CONTEXT.md -------------------------------------- # today's job description references/ ----------------------------------------- # voice rules, examples output/ ----------------------------------------------- # the draft lives here 03-production/ ------------------------------------# step 3: ship the final artifact CONTEXT.md ------------------------------------- # today's job description references/ -----------------------------------------# design system, build conventions output/ ----------------------------------------------- # the finished product _config/ -----------------------------------------------# L3: brand, voice, design (configured during setup) shared/ ----------------------------------------------- # L3: assets every stage might use skills/ -------------------------------------------------- # L3: bundled skills the agent can call setup/ --------------------------------------------------# first-time configuration