cursor/plugins

Especially for general purpose technical writing, system design, architecture and code comments, I do use pstack unslop [0] and technical-writing [1] skills. They do wonders. [0] https://github.com/cursor/plugins/blob/main/pstack/skills/unslop/SKILL.md [1] https://github.com/cursor/plugins/blob/main/pstack/skills/technical-writing/SKILL.md

Claude Code, Codex, Pi clis all for varying levels of work. VS Code when needed. I review agent messages, some specs/plans, and conduct local code reviews with Plannotator [1]. For skills, I have a bunch of custom ones for my own workflow. and for public skills I really only use the interrogate skill from cursor's lauren [2]. Key workflow stuff: - Almost all work I do gets done in a git worktree. - ghostty + Mac OS gives me all the organization I need for multi-agenting - turn off all agent memory, this has only ever caused problems for me. [1] https://plannotator.ai [2] https://github.com/cursor/plugins/blob/main/pstack/skills/interrogate/SKILL.md

I've been liking this code review skill lately, it has pointed out some good improvements. https://github.com/cursor/plugins/blob/main/cursor-team-kit/skills/thermo-nuclear-code-quality-review/SKILL.md

It's started rubbing off on me too and I find it irritating when I'm chatting with someone and an AI-ism starts rolling off my tongue. I'm beginning to think I should: a) ask my agents to unslop[1] themselves when communicating back to me, and b) decide upon some writing standard and ask my agents to adhere to that. [1] https://github.com/cursor/plugins/blob/main/pstack/skills/unslop/SKILL.md

…make sure I haven't missed any important stuff, and it's usually at the bottom of every response, Claude does talk a lot, (codex tends to be better at communicating) but what I found a bit helpful is the unslop skill by pstack, it can help your claude talk in a more read-friendly way. https://github.com/cursor/plugins/blob/main/pstack/skills/unslop/SKILL.md when it comes to reading the diffs, I created my own app to review the diffs away from github, manage my PRs and do everything I could on github without relying on it's broken UI https://pyor.review You could also just ask Claude to help you go through stuff bit by bit, you'll slowly build the skill and adapt to reading Claudish.

…mpact. I find it's a lot harder to get an understanding after the fact. After that, I suspect a lot of people already are familiar with the https://github.com/cursor/plugins/tree/main/pstack skills, but in case you aren't they can be a good starting point. The `blast-radius`, `how`, `interrogate`, and several of the `principle-` may be interesting if you haven't already looked at this. There are some types of reviews I find models don't do a great job at: architecture reviews (things can get too complex for them to grasp), security reviews (they get cagey thinking you're a wrong-doer), UI/UX design (they're getting better, but still most models are pretty bad). There are some dedicated too…