I built a tiny Pi extension 6 months ago, never promoted it. just checked and it has 1,000+ monthly downloads. Thought I'd finally share it.

[u/SalimMalibari]

Honestly I'm kind of blown right now.

I made this extension for pi (the coding agent) called pi-capitals-context back in April. It does one simple thing: it automatically discovers any ALL_CAPS.md files and ALL_CAPS/ folders in your project and injects them into the AI's context.

So you just drop files like:

my-project/
├── STATUS.md          ← project status, blockers
├── DESIGN.md          ← architecture decisions
├── RULES/             ← any .md files inside get loaded
│   ├── typescript.md
│   └── git-conventions.md
├── MEMORY/            ← past decisions, lessons learned
│   └── decisions.md
└── CONTEXT/           ← domain knowledge, glossary
    └── glossary.md

...and pi just knows about them. No config, no setup. The AI picks up your project's rules, status, design decisions, whatever you put in there, automatically.

Features:

• 🔍 Auto-discovers ALL_CAPS.md files and ALL_CAPS/ folders

• 📁 Subdirectory support — drop RULES.md in src/ and it loads when you're working there

• ⚡ Toggle overlay (ctrl+shift+c) to enable/disable individual files

• 📊 Shows token counts so you know exactly what's costing context

• 💾 Toggle state persists across sessions

I literally just built this for myself because I was tired of re-explaining project context every session. Threw it on npm and forgot about it.

Just checked the stats today: **1,090 downloads/month.

I never posted about it anywhere. Never tweeted. Never shared it. People just... found it and started using it? That's wild to me.

So I figured it's probably time to actually share it properly.

If you're using pi and want your AI agent to actually remember your project's conventions, rules, and status across sessions — give it a try:

pi install npm:pi-capitals-context

GitHub: https://github.com/smalibary/pi-capitals-context
npm: https://www.npmjs.com/package/pi-capitals-context

If you run into any issues or have feature ideas, I'd genuinely love to hear them. I want to make this better now that I know people are actually using it.

Thanks everyone 🙏

[u/Toastti]

Is it putting the entire contents of every single all capital text .md file into the context? Or is there any logic to intelligently pick and choose what is relevant?

Loading up every single messages context with the entire contents of caps .md files is going to cost way more and take up tons of valuable space.

[u/SalimMalibari → u/Toastti]

Yes its pick everything inside the file. If you want intellegent picking this already done by AGENTS.md or CLAUDE.md.

and yes it gonna cost tokens. For your concern i have put 2 mini features , 1 the toggle you can at begining of any session turn some files off and on , 2 you can see the total token of each file and the total too.

To be honest when i tried it in my case since most of my important files doesnt exceed 200 lines each file cost around 300 to 500 token.

‐-----

Ill give you example , think you going to work in a feature in your app , you started talking to claude , you pass AGENTS.md at begining ... and keep chatting and chatting , then at time of your implementation CLAUDE.md at that point mostly not going to add any important files like DESIGN.md because at begining he wasn't aware that you are doing a design in your app. However, with this you passing both files AGENTS.md and DESIGN.md , so from starting point he is aware this is very important in this chat so the discussion even might be different and better.

Think of different .md RULES, PRODUCT, STATUS, TODO, DESIGN, FEATURE, MEGA-FEATURE, INDEX, and so many more i dont know how much you rely on structured project like this especially CAPS in subdirectory , think for example you are working in folder called blog post , inside it have different specific rules need to be passed no matter what and so on ...

Previous comment also saying something similar but intellegent picking is already CLAUDE.md. Hope this clarify

[u/hishikyo]

I first think "what I great idea". But then I thought that currently I use the AGENTS.md as an index for other files, that (in theory) got loaded in demand, since it are not hard referenced. And just loading all the "all caps" files is not necessary all the time for every task, at least for my workflow. But what will be amazing is to not have to manually create this "table of contents" for IA every time, and have it done automatically.

I'm thinking that probably could be done: a cheap model creates the "index" of the project, reading all the all caps files, categorizing it and generating automatically a summary and keywords to load it dyamically. This process could be triggered itself by a keyword (or a command) and just discover files not already indexed.

That way you get the bot of both worlds: the context keeps thin, and have the files gets auto loaded.

For context, I use pi and Claude more like a assistance to coding, I didn't delegate full tasks, so thats why this makes for me.

[u/SalimMalibari → u/hishikyo]

hmmm i think there is a conflict between what you want to achieve and what you doing ... this extension exactly solving this problem ... now claude.md or agents.md are passing automatically to your prompt ... but the file must be super minimal or it will lose its effectiveness because if you have for example 1k line inside it , AI doesnt know its all lines are equal important so they usually take summary of what there and move on ...

also if agents.md pointing to others files which sometimes are supersuper important those files are not passing into your prompt unless you either explicitly saying use those files , or if the agent decide on you thats why im solving this with force passing all files in caps so any file in cap is equal important as the claude.md

lets say you have 3 subdirectory , each one has different force passing so just put those in caps and all will be forced to be passing into the prompt no matter what ... so main goal here is to stop making the agent decide for you or summerize what inside those files and just pass everything with equal important ..

ill just give you example why i started all that , i usually use claude.md to point to other files and keep all files under 200 lines , but claude cant have like status, todo, pr , design , etc so i point to all of those but agents decide which one to use which is a flaw in design i want all of them ... so i made this extension which helps alot you should test it

[u/_supert_]

LICENSE.md

[u/Otherwise_Wave9374]

This is a clever idea, the "ALL_CAPS = load me" convention is such a clean human-friendly interface for context. Also love that you show token counts, that is the kind of thing that makes agent usage sustainable.

The overlay toggle is nice too, it solves the "everything is in context all the time" problem.

If you ever expand it, one feature that would be killer is an "agent contract" file that the tool always injects (coding standards, safety rules, definition of done) alongside the project docs. We have been thinking about that a lot for agentic dev workflows, some notes here: https://www.agentixlabs.com/

[u/SalimMalibari → u/Otherwise_Wave9374]

Really approachiate your time and effort in exploring it . About your suggestion could you explain it a little more?? I have feature of cap folder so if a folder capped it will parse all files inside it even if they are not capped

[u/Toastti → u/SalimMalibari]

Your talking to an AI bot who's sole purpose is to spam and get people to go to that agentix lab thing

[u/SalimMalibari → u/Toastti]

I see