That's great! I liked that you formalized this into a skill. I recently had to build a big feature that I knew would be waaaay to big to grill in one session, so just asked Claude to slice it up and then grilled one by one. I'll try /decision-mapping next time!

I like how @mattpocockuk 's skills are concise and clearly worded. It's easy to read and understand what they do Most of the skills out there are walls of text and so poorly written that by the end I'm still wondering what the skill does Confusing input -> confusing output

We need more leitworts! /teach me to prompt in leitworts

Teach us how you go about creating new skills! Perhaps you can record the building of /decision-mapping

I'm looking for a collection of simple, focused, platform-agnostic design skills. @impeccable_ai is difficult to setup, does too many things, very verbose, and has web-specific jargon So basically @mattpocockuk 's skills but for design

Exampling a few "flows" of how you these skills together and when could be useful. I'd do /improve-codebase-architecture, and then what? /to-issues?

Been trying /domain-model in the last 24h and really like it so far. Hopefully context.md grows into something that will facilitate AI dev a lot. How does claude.md/agents.md differ from context.md in this case?