mattpocock/skills

Look up the grilling skill[0]. To make it even better, tell Claude to modify it to use the AskUserQuestion functionality. It's so much better than plan mode. 0. https://github.com/mattpocock/skills/blob/main/skills/productivity/grilling/SKILL.md

I have been using this super simple skill[0] to make Claude ask exhaustive questions about the implementation of larger features. It has been absolutely amazing and felt like a step change in the output quality. For complex features there can be 10 or more questions but I have a very strong sense of understanding the changes about to be made and Claude is very good at following all the decisions exactly. It's like working with an engineer who is both excellent at soliciting requirements and fast at implementation. [0] https://github.com/mattpocock/skills/blob/main/docs/productivity/grilling.md

TIMTOWTDI. "[T]hings shared with the team (in the repo)" implies project-specific skills. See e.g. https://github.com/mattpocock/skills for a stellar example of third-party skills for battle-hardened workflows.

I believe these are called Architectural Decision Records. Matt Pocock's skills [0] make use of them. They're one of the more useful things I've gotten out them. [0] https://github.com/mattpocock/skills

If you start with a spec you understand at the beginning then you don't need the LLM to generate high-level information about the changes at review time. The grilling (grill-with-docs) skills [1] are amazing for ensuring you produce a through spec that covers all the edge cases. The /code-review skill from there helps ensure that the code changes meet the spec. I use an intermediate detailed plan stage (done by a more expensive model) before implementation. Information from that plan is posted on the PR to give pretty much all the intermediate level context reviewers need. I do like incorporating the idea of this article into my flow- that the spec and PR context could be presented in a m…

I’ve used the following teach skill by mattpocock to learn Java concurrency concepts in 20 bite-sized hands-on lessons starting from creating a new thread to building a Thread-safe Connection pool. I’m pretty sure I can adapt this to learn Concurrency in any language like Go or Rust. https://github.com/mattpocock/skills/tree/main/skills/productivity/teach The point is not that I’m learning Concurrency in a better way using LLMs, it’s that I can apply this style of learning using bite-sized, hands-on, visual explanations, quiz to any topic in the future. The lessons it generates are just code, and you can ask it to type check the examples, validate with recent libraries, use analogies to le…

Thanks. I have been doing this tdd abd it's a big improvement but the code is still pretty awful. Two skills I rely on are Matt pococks grill-me and his tdd. These massively helped, and technically the code generated is correct but it's still hard to follow and bloated. https://github.com/mattpocock/skills/blob/main/skills/productivity/grill-me/SKILL.md

I've found this skill to work well: https://github.com/mattpocock/skills/tree/main/skills/productivity/teach

… the 90's polygon rendering from screen to world space. It spun its wheels a few times doing a large mostly mechanical change. After resetting and improving my prompts it was able to get through it. I'm using Matt Pocock's skills[1] for this work, which has been quite nice. [0]: https://github.com/FatalDecomp/ROLLER [1]: https://github.com/mattpocock/skills

…s from thin air, the coding bit may only be 2x faster with a poorer-quality outcome, but working out what's needed is a good 5x faster. And yes, I'm using the same adversarial AI MO as @wood_spirit, combined with Matt Pocock's excellent /grill-me and /grill-with-docs skills [1] and Plannotator [2] to review the plans. 1. https://github.com/mattpocock/skills 2. https://github.com/backnotprop/plannotator

…uage. * Invariants (always/must, never) * Precedence * Guidelines/Opportunistic Inspection (softest instruction) * Patterns * Concrete commands/actions - all of which can be mixed and matched. The prose he writes often has very little utility, wrapped up in a ball of wax. I would at least expect that an engineer would run AI skill files through an impartial LLM to look for cruft. eg "if this document is for an LLM to consume, is there any noise in the instructions? https://github.com/mattpocock/skills/blob/main/skills/engineering/wayfinder/SKILL.md "