The real problem is it’s going to contain wheat. It’s no longer safe for those who NEED to be gluten free. Yes, the are going to label it accordingly. But mistakes will happen because people have been eating it safely for years and will not expect to need to read the labeled again.

What models are you using? What hardware are you running them on? I’m curious if I can replicate your success

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!!!

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

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

1. brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

2. using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

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

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

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

6. requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.

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

• plan only
• read the spec file I just wrote
• 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.

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-fork is the Android client. Not the main repository.

Spicy pan

Cats are liquid