The patterns in the article might be a starter, but there's so much more to cover:

agents role (Orchestrator, QA etc.), agents communication, thinking patterns, iteration patterns, feature folders, time-aware changelog tracking, prompt enforcing, real time steering.

We might really need a public Wiki for that (C2 [1] style)

[1]: https://wiki.c2.com/

Starred.

I am looking to that exact concept - for a different mean - to develop my agent orchestration hobby project.

LLM working in a «feature folder» where it stores change-logs, documentation, summaries, requirements, attachments, and so on. What I will be looking into very soon, is also storing the session id, for summarisation, history context, and so on.

I will definitely steal some concept from your project.

Glad it might be of use to you, but for your project, that case, a project from someone else (https://github.com/matt1398/claude-devtools) might be able to give you even more for inspiration :). Good luck with your project!

For Claude the most pollution usually comes from Claude itself.

It's worth noting thet just by setting the right tone of voice, choosing the right words, and instructing it to be concise, surgical in what it says and writes, things change drastically - like night and day.

It then starts obeying, CRITICALs are barely needed anymore and the docs it produces are tidy and pretty.

Value makes the world a better place, not profits per-se. Sometimes the two things coincide, sometimes they don't.

For some reason I made my own skills framework.

The LLM instructed to run the initialization script as the first thing, before reasoning about the use request (this proved tricky to achieve). The scripts greps the content matter out of the skill files, along with the file path.

I have no clue if this outperforms an embedded index.

Most often product development involves a lot of legacy. In consultancy you get to start from scratch at least every once in a while.

I am asking my agents to use HTTPie this day, it's more understandable for them in case of error.

The real future: when Claude/ChatGPT/Gemini have banned you, you must leave society, you employment, the planet.

Side question, I am currently using Github copilot, what would be a good reason to switch provider? Looks like I am almost the only one I here using it.

I didn't read the whole article and constitution yet, so my point of view might be superficial.

I really think that helpfulness is a double-edged sword. Most of the mistakes I've seen Claude make are due to it trying to be helpful (making up facts, ignoring instructions, taking shortcuts, context anxiety).

It should maybe try to be open, more than helpful.