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/un... [1] https://github.com/cursor/plugins/blob/main/pstack/skills/te...

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/un...

I can't do much about the amount of text I gotta read, I do have a line in my claude.md file to ask Claude to keep telling me about stuff that I missed or haven't responded to yet so I 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/un... 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 r

It's understandable, I don't think most of us like getting to the actual documentation of our project and would rather keep coding and/or prompting. I think this is a message more for everyone that feels this way than just you but... I'd suggest having a model go through it using pstack's unslop skill and see if you like that copy better. But in all honesty we should be proofreading readmes before sending instructions out to millions of people. I've tried setting up a few that just didn't work when following instructions because of incorrect info or just completely leaving necessary steps/info out... Usually totally useless info in its place. There's a conundrum there where we're so excited to show off our project that we present it in this streamlined way that makes people unable (or unwilling) to even digest what it's for and how to pro

I think you need to catch a lot of it before it becomes a PR. Spend a lot of time teaching the agents how you code in your prompts, AGENTS.md files, etc. Make sure they know what your desired architecture is, how you want them to talk to you, how to identify and speak to their perceived blast radius, what kind of documentation you like, and so on. So when something an agent wrote does come to your desk for review, you can optimize your time/impact. 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

I use this one and it's ok https://github.com/cursor/plugins/blob/main/pstack/skills/br...

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/in...

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/...