So I spent week-end with a friend at reflecting Claude, fiding how it works, and how we can make our sessions better. We finally agreed to a model: when you prompt Claude, you give him 2 things: - a goal (fix it, build it) --> that’s ok I’ll no longer speak about it - a context When contexting Claude, you mainly give him 2 types of info: - things that he doesn’t know (business, specific lib doc, history of dev, …) called unknown info - things that he has to choose (language, styling, architecture, …) called opiniated info Our important point - and we maybe are just noobs who are lost - is there is those only 2 natures of info: nothing more, nothing less. And there is no such thing like “he can discover or understand” or “you can also give info to save tokens”: we speak about raw info, at first degree, not long term strategy. So, nice sum up, but what does it changes? Based on it, we “decided” that we can sort those 2 types this way: - claude.md, in small projects, will carry either unknown and opiniated, but if it grows, it should carry exclusively unknown info, - skills should carry exclusively unknown info (scripts, doc of specific libraries, …) - rules should carry exclusively opiniated info (how to use git on this project, which styling for given langage, …) - agents should act as opiniated roles (orchestrator must only give those info, database admin should never let security down, …) - memories, when must be promoted as proper info, should either be promoted as rule (please never use this command, …) or skill (it’s how umour server works, …). If we are right - please roast this model - then we have a concrete, powerful and clear idea of which info goes where. WDYT? submitted by /u/Nayte91
Originally posted by u/Nayte91 on r/ClaudeCode
You must log in or # to comment.