Ask me about the food poisoning my whole family got from a store bought shelf stable pie crust!! We made the pie within a couple weeks of buying the crust, but determine after the fact that it expired a year prior! 🤮
allowScripts defaults to off: npm install will no longer execute preinstall, install, or postinstall scripts from dependencies unless they are explicitly allowed in your project. This includes native node-gyp builds (i.e., a package with a binding.gyp and no explicit install script still gets blocked, because npm runs an implicit node-gyp rebuild for it). prepare scripts from git, file, and link dependencies are blocked the same way. To see what would be blocked, run npm approve-scripts --allow-scripts-pending. Then allow the packages you trust with npm approve-scripts and block the rest with npm deny-scripts. The resulting allowlist is written to package.json and should be committed. If your install routine runs scripts, you can observe warnings in npm 11.16.0+.
Note that the current version injects a lot into the system prompt, and it’s always on. If you using Claude Code, install it in a second profile, so that you choose when to use it. I exploring its features now.
brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.
using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.
writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.
subagent-driven-development or executing-plans - Activates with plan. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.
test-driven-development - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.
requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.
finishing-a-development-branch - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.
The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.
optionally ask me questions in ‘qa.md’, I’ll reply inline
Repeat until it stops asking me questions, then switch to a different model and ask again. I usually use both gpt5.3-codex AND Claude Sonnet
Then I have it update the spec. I start a new session to have it implement. Finally review the code. If I don’t like it, undo and revisit the spec. Usually it’s because I’m trying to do too much at once. And I need to break it down into multiple specs.
Ok. Let’s pretend that’s what happens. Many people would gladly make that trade if they kept / recovered brain function. Of course, it would depend on many things like how pain and timeline of the cancer vs dementia.
Why? The new LLM features are opt-in. Just don’t turn it on if you don’t want them. Or is there something else you don’t like?
Ask me about the food poisoning my whole family got from a store bought shelf stable pie crust!! We made the pie within a couple weeks of buying the crust, but determine after the fact that it expired a year prior! 🤮
My wife has this “superpower”. It’s only useful is rare circumstances. Most of the time it’s a curse.
Finally!!!
Superpowers has brainstorming
Note that the current version injects a lot into the system prompt, and it’s always on. If you using Claude Code, install it in a second profile, so that you choose when to use it. I exploring its features now.
https://github.com/obra/superpowers
The Basic Workflow
brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.
using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.
writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.
subagent-driven-development or executing-plans - Activates with plan. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.
test-driven-development - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.
requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.
finishing-a-development-branch - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.
The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.
My preferred way of using LLM coders is:
Then I have it update the spec. I start a new session to have it implement. Finally review the code. If I don’t like it, undo and revisit the spec. Usually it’s because I’m trying to do too much at once. And I need to break it down into multiple specs.
Ok. Let’s pretend that’s what happens. Many people would gladly make that trade if they kept / recovered brain function. Of course, it would depend on many things like how pain and timeline of the cancer vs dementia.
Sorry, I’ve no idea. I don’t use the mobile versions. I was just confused on what was going on
For anyone who’s confused:
syncthing-forkis the Android client. Not the main repository.Spicy pan
Cats are liquid
What you want is a Community Association. They can legally manage the shared property, while having little to no power over your property.
Boop
Moopsy
I see he paid the Internet Cat Tax
Aww! Here's one of my cuties
I think the laundromat case is more "don't complain to management when you're stuff gets stolen" than it is about preventing lawsuit.
I’ve finally figured out this logic!! The developer must be a wheelchair user. Most wheelchair users would find that impossible to pass without help.
Unfortunately, in many areas, lawsuits are the main way the ADA is enforced.
That being said… these lawyers are ambulance chasing scum. Their formula is purely for profit, “enforcing” the ADA is only a side benefit.
FTL. It’s a simple fun cheap game. Steam says I’ve played this for over 3,000 hours!
https://subsetgames.com/ftl.html#_