I've recently added support for AGENTS.md so I don't need to tell it how I want to do testing and code style checking every time and generally save some extra file reads whenever it starts a new feature. Next I'm gonna play with "skills" so I can load up commonly used instructions instead of repeating myself.

I haven't had much of a need for skills so far because the models are pretty capable even with minimal prompting and I found that skills often fill up the context more than is strictly necessary. I was thinking for ergonomics I'd have users define skills in their "documents" folder to make it more intuitive for graphical interface users.

@mauve

I created a skill for this too. It works like a charm. Has all the standard engineering rigor, best-practices, security, tests, accessibility, etc, applied as a step by step workflow which must be validated before marking any task complete. It's a total game changer, improving the output by an order of magnitude. Highly recommended.

@toiletpaper Is your skill published somewhere I could read? :o

I found I haven't needed to spell out how rigorous it needs to be because it's pretty good at that out of the box and past that I'm guiding it.

@mauve

No. I can send it to you privately if you want. I'd publish it, but I've been doing my best to compartmentalise my personal life from my fedi presence, for hopefully obvious reasons. Happy to share though, just not directly on fedi.