Activity
Mon
Wed
Fri
Sun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

Clief Notes

35.8k members • Free

10 contributions to Clief Notes
Built a reusable Claude Code project template that wires Jake's three-layer routing system into a full session architecture.
The template integrates three frameworks: Van Clief's routing (the structural backbone), Karpathy's behavioral rules (think before acting, minimum viable scope, surgical changes, goal-driven execution), and IBE intent preservation (the "why" behind every decision). Each tier has a clear job — CLAUDE.md routes, workspace context files carry domain knowledge, skills wire selectively per task. The core addition on top of Jake's routing: a session state pattern (STATE.md) that eliminates cold-start friction. Each session closes by setting the next session's intent. Work becomes a directed sequence rather than a series of isolated conversations. Results from two validations (a meta-framework design project and a non-software operational coordination project): - Zero context re-establishment at session start - Zero intent-misaligned rework - Second project stood up in ~25 min on first attempt, no structural modifications needed Template is public: https://gitlab.com/vigilkeep/ibe-workflow-template Happy to share the ADR that documents the one deliberate deviation from 3.3 guidance (CLAUDE.md runs ~70 lines instead of 40–50 — there's a specific reason).
1 like • 18h
I just added a retrofit case study where 8 in-flight projects across various stages were retrofitted under a single organizational umbrella. There were some issues, but managed to achieve success within a single session (only 50% token limit usage).
0 likes • 7h
@Arjen Stet STATE does not replace the regular memory files maintained by Claude in the .claude directory. It serves as the entry point with Van Clief's three layer architecture to ensure cold start immediately route correctly. STATE functions as a pointer to engage the correct routes at startup, immediately moving to where you left off on the previous session without prompting. The work directory currently contains in-flight work. The drafts are not yet posted to GitHub Discussions and the Wiki for Vigil Keep IBE has not been updated with the relevant patterns and anti-patterns. It is not mere demonstration, it is the actual active workflow as it progresses over several sessions. (I work on this after hours / free time).
🏁 Foundations 4.4 Check-In
You just wrote a CLAUDE.md for one of your projects. Vote below, then drop yours in the comments. Bonus points if you ran the same task with and without it and can tell us the difference.
Poll
214 members have voted
0 likes • 19h
Have been using MD files for ages, but always looking to improve and refine. Test different approaches, surprising sometimes as it challenges previously held assumptions.
0 likes • 18h
@Matt Wiseman Great question and one of the most common real world use cases. I just finished a case study on retrofitting existing projects. It utilizes my IBE-workflow (integrating IBE, Van Clief three-layer architecture and Karpathy's principles). Check it out here if you are interested: https://gitlab.com/vigilkeep/ibe-workflow-template. There are still friction points that I will address, but they are noted in the case study and discussion drafts.
🏁 Foundations 4.3 Check-In
You just used Claude Desktop as a thinking partner instead of a vending machine. Vote below, then tell us in the comments: what was the problem, and what was the insight you walked away with?
Poll
258 members have voted
0 likes • 19h
I have always used AI as a thinking partner, it was my first actual use case. Get thoughts structured, get design intent defined, produce a clear spec and then start building... Some of my friends and I use it as the "10th man" (World War Z concept).
Do you write your md files from scratch?
Just curious, does everyone write your md files from scratch? Or do you ask claude to help you write, by giving it information? And can I say that the recommendation is to have md files lesser than 150 lines?
1 like • 6d
I created a Claude workflow to write the files and set up new projects. It takes less than 30 minutes for a new project where you haven't even fully realized the architecture or concept. Around 5-10 minutes for projects where you have clear objectives and/architecture. You just need to point claude to the template/README.md; Check it out https://gitlab.com/vigilkeep/ibe-workflow-template, feedback welcome!
1 like • 5d
@Adrian Chen "Each framework solves a different problem. The three-tier architecture is the synthesis that wires them together without adding overhead beyond what they individually require." IBE ensures clear intent, well defined objectives and records decision rationale (for future reference). Von Clief's three-layer routing ensures context is scoped to the current task. Karpathy's principles ensure the right problem is being solved in the right way. So the three frameworks compliment each other. It is also designed to be domain agnostic (not just software focused). It stems from work I am doing in both technical design / engineering along with work outside of that (creative industries, etc.).
Second Brain 🧠?
Apologies if this topic has already been covered. My thought was to have Jake’s folder structure as my main Ai Operating System and then have a wiki or second brain where I can dump thoughts, ideas, past decisions, mistakes, lessons etc. Combining Jake and Karpathys concepts into one. The second brain knowledge base would be called on when needed for tasks that I call within the folder structure. Bear with me if I’ve gotten some concepts or terms wrong - still learning lots about all of this stuff 😳🤯 Does this make sense or am I missing something important here?
2 likes • 6d
I just finished building something like that today. My workflow template and case study is available on Gitlab (https://gitlab.com/vigilkeep/ibe-workflow-template) for any who want to check it out or test it for themselves.
1 like • 5d
@Giovanni Garcia STATE.md controls the context window. Only the relevant context to the current state or task is loaded. IBE provides clear intents and objectives, Clief's three-layer routing ensures only relevant context is loaded and Karpathy's principles ensures directed behavior. It keeps the context window scoped to the current iteration (designed as an adaptive feedback loop).
1-10 of 10
Billa Coetsee
3
45points to level up
@billa-coetsee-5912
Seasoned Systems Architect and Technology Executive leading technical strategy and implementation across diverse organizations.

Online now
Joined May 21, 2026
ENTJ
South Africa
Powered by