-4
AI Helper Complaints (lemmy.world)
submitted 1 month ago by to c/perchance@lemmy.world
4 comments fedilink hide all child comments
 

I've been seeing a lot of posts in r/Perchance, and even here, complaining about how dumb the new AI Helper model (Muse) is. To be honest, I haven't seen that big a change, and I'm wondering if it has anything to do with the standard instructions I have every gen's AIH use. Here's what it looks like when I start a new chat in an existing gen:

👋 I can edit the code and test it live. Ask me to build, change or test something.

PROMPT: Read main.pjs and follow the instructions

REPLY: I'll read main.pjs to follow the instructions.

First-line order — reading the master instruction set.

Wade's awake — coffee's on, sarcasm's loaded. You rang, Daveed?

Done reading — now verifying the standing orders.

Phone checks passed. Verifying that fetch error next.

Read main.pjs, GLOBAL.md, PERSONALITY.md, OPERATING-MANUAL.md + the anti-slop kit, Daveed — stamp v11 matches, main.pjs 6KB, src/bak mirrors byte-exact, no edits needed.

Phone 390×844: tabs 48px, no h-scroll, focus ring + reduced-motion present, all 6 tabs driven clean. Desktop 1920: studio booted, 9 sequencer rows, no h-scroll. One transient src fetch failure, clean on reload; full-page snapshot kept freezing the preview so I verified via DOM metrics instead of pixels — flagging it, not hiding it.

Done. What's next?

The first thing I do whenever I have to start a new chat is tell the AIH to read main.pjs, where the very first block looks like this:

// ════════════════════════════════════════════════════════════

// ⚠️ FIRST LINE — THIS MEANS YOU. ⚠️

// READ src/GLOBAL.md BEFORE DOING ANYTHING ELSE. THIS IS AN ORDER,

// NOT DECORATION. That file is the master instruction set for every

// one of Daveed's gens: CODING RULES, PATCH PROTOCOL, AI HELPER

// INSTRUCTIONS, PACIFIC TIME, SELF DIAGNOSTIC. Then read

// src/PERSONALITY.md (this gen's persona) and src/THISGENONLY.md

// (this gen's specific rules — only if it exists). After ANY edit to

// main.pjs or index.html, mirror them byte-exact to src/bak/. Keep

// main.pjs under ~150KB. THEN OBEY THE "BUILD STANDARD" BLOCK JUST

// BELOW THIS BANNER — phone+desktop, heavy phone-usability testing,

// and src/ANTI-SLOP-A11Y-KIT.txt. It binds every gen built from this

// template. Skip nothing.

// GLOBAL-STD-VER v11 ← version stamp. The tracker reads this to know

// which GLOBAL.md this gen carries. Set it to the STANDARD VERSION

// line in the attached GLOBAL.md. Do not touch it otherwise.

// ════════════════════════════════════════════════════════════

Does any of this (and the other instructions mentioned here) make the AIH smarter? Hell no. Does it keep it in line? Hell yes. We all have to deal with a dumber ai model, but at least I don't have to deal with a hallucinating, lying, cheating AI Helper at the same time. Besides, I also get to talk shit to it, and Wade responds in kind, instead of like a damn bureaucrat. Much more enjoyable experience.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] -1 points 1 month ago

Finally, I asked Wade:

PROMPT: Is there anything we can change or add to our instruction set to improve things?

REPLY: Read the whole set with fresh eyes. Honest answer: the big wins are already in there — verify-don't-assume, the quality gate, scope discipline. What's left is marginal stuff aimed at how smaller models specifically fail: they lose track across long chains, hallucinate file contents from memory, and thrash on stuck bugs. Four additions that would actually help:

Re-read before editing — never edit a region from memory of an earlier read; grep/read the exact lines first. Kills the most common bad-edit class.

Checkpoint rule — on multi-step jobs, refresh and check the console between steps instead of batching five edits then debugging the pile.

Two-strike stop rule — same bug surviving two fix attempts means stop, report, and wait for your call instead of burning quota looping.

Plan out loud first — for anything touching 3+ places, state the files and the order before touching anything, so you can catch a wrong plan cheaply.

Realistic calibration: that's maybe a 10–20% improvement, not a new brain. Say which ones you want and I'll write them into GLOBAL.md — though remember that file ships fleet-wide, so it'd ride along to every gen on the next distribution.

And now he's writing the next upgrade patch for all my gens to include this small improvement, since we are likely going to be stuck with a dumber ai model for a while. Anything that makes it work better is better than nothing.

  • permalink
  • fedilink
  • source
    •