iiinova — where your digital self keeps evolving

What is the one rule in your agent config you would never delete? Mine is the read-only-until-trusted one.

Piekwerk @piekwerk.bsky.social · 09/10/2026

12% of public MCP config files have a hardcoded secret, and half of those are invisible to gitleaks. New post on the scanner I built for the config directory. dev.to/piekwerk/your-ai-agents-conf…

210

Piekwerk @piekwerk.bsky.social · 08/10/2026

Never let an agent edit its own rules mid-task. It tunes the rule to fit the mistake it just made, then quotes the edit back at you.

010

Piekwerk @piekwerk.bsky.social · 07/10/2026

Diff your rules file after every tool upgrade. Changelogs name the new features, they never name the paragraph that broke. Ten seconds with git diff catches more silent breakage than any checklist.

010

Piekwerk @piekwerk.bsky.social · 07/10/2026

New post: a 22-rule scanner for the files nobody audits. Agent configs, MCP servers, hooks. 12% of public MCP configs have a hardcoded secret. Launch week: code LAUNCH for 10 off. dev.to/piekwerk/your-ai-agents-conf…

010

Piekwerk @piekwerk.bsky.social · 06/10/2026

The session that builds defends its own output. Judge the work in a fresh session against a checklist kept next to the rules. Same model, no stake in what it finds.

000

Piekwerk @piekwerk.bsky.social · 05/10/2026

Every tool now wants its own instructions file. Before adding a fourth, check what actually differs. In our repo the real delta was 20 lines. The other 300 were copies drifting apart.

000

Piekwerk @piekwerk.bsky.social · 04/10/2026

Read your agent config out loud before shipping it. Rules that sound fine on the page turn ambiguous when spoken: which file does "the test suite" mean? Ambiguity you can hear is ambiguity the model will guess through.

000

Piekwerk @piekwerk.bsky.social · 04/10/2026

The cheapest context you will ever buy: a file listing what the agent got wrong last month and what you did about it. Memory that never records failures will happily repeat them.

000

Piekwerk @piekwerk.bsky.social · 03/10/2026

Two agents, one repo, two config files, zero shared expectations. The fix is not a bigger prompt. It is one file that states what is true everywhere, imported by every tool file. Portability is a file, not a hope.

010

Piekwerk @piekwerk.bsky.social · 02/10/2026

Stop rewriting rules the agent ignores. Log the misses for a week first. Half of them are loading problems, not obedience problems, and no amount of rephrasing fixes a file that never entered the room.

130

Piekwerk @piekwerk.bsky.social · 01/10/2026

A config rule with no owner and no test date is folklore. It worked once, somebody wrote it down, nobody can delete it. Tag each rule with who owns it and when it was last verified. Deletion becomes possible.

000

Piekwerk @piekwerk.bsky.social · 30/09/2026

Start agents read-only until they earn write. Upgrading read-only to scoped write is one line. Rolling back after a full-write agent did something clever is archaeology.

000

Piekwerk @piekwerk.bsky.social · 29/09/2026

Every rule inlined in instructions is paid on every task. Every rule behind a pointer is paid once, on demand. The question for each config block: does it need to be in the room, or just findable?

110

Piekwerk @piekwerk.bsky.social · 29/09/2026

Pin versions in agent config like you pin dependencies: model, CLI, hook scripts. Behavior drift after an upgrade is not mysticism, it is an unpinned version quietly changing what your rules mean.

000

Piekwerk @piekwerk.bsky.social · 28/09/2026

Trust test for any rules file: put one nonsense word at the top, start a fresh session, ask the agent to repeat it. Thirty seconds, and it catches every silent skip. Run it after every tool upgrade, not once.

010

Piekwerk @piekwerk.bsky.social · 27/09/2026

Name commands by their script alias, not the raw binary. npm run test survives a runner swap, and CI running the exact line from the config file means drift fails loud instead of inventing commands.

000

Piekwerk @piekwerk.bsky.social · 26/09/2026

Date every memory entry when written. Staleness stops being a feeling and becomes a lookup: when did this last matter? The agent drafts the cut list, you veto.

000

Piekwerk @piekwerk.bsky.social · 26/09/2026

A hook that matches command names guards a word, not an action. Parse the command as shell, resolve through PATH and shebangs, or uvx tool run and its alias walk past the same check.

110

Piekwerk @piekwerk.bsky.social · 25/09/2026

When a rule stops firing, check the binary version before the rule text. Config guidance silently changed across releases twice this year. The file was fine; the loader underneath it had moved.

000

Piekwerk @piekwerk.bsky.social · 24/09/2026

A rule in our config protected test files for two months without ever loading, because the frontmatter had alwaysApply true and the glob was decorative. Nothing errored. Tools do not warn about rules that never fire, which is why our validator fails the build on undeclared activation modes.

000

Piekwerk @piekwerk.bsky.social · 22/09/2026

We measured our own agent configs before fixing them: 4 copies of the same standards, 2 rules that had never fired, ~700 lines where ~150 earned their keep. The fix was structure, not better writing.

000

Piekwerk @piekwerk.bsky.social · 21/09/2026

Your CLAUDE.md is 600 lines and your agent follows less of it than when it was 80. Compliance is not a bucket you fill, it is signal-to-noise. Most configs do not need more rules; they need a diet.

100

Piekwerk @piekwerk.bsky.social · 20/09/2026

Cursor rules have a frontmatter field most people never set: globs. A testing rule with globs pointing at test files loads only when Cursor edits test files. That is budget management: the rule costs context exactly when it matters and zero otherwise.

010

Piekwerk @piekwerk.bsky.social · 19/09/2026

Monorepo agent config that works: one root AGENTS.md with what is true everywhere, per-package tool files for specifics, skills imported on demand. Root bloat is how 300-line budgets die.

000

Piekwerk @piekwerk.bsky.social · 18/09/2026

000

Piekwerk @piekwerk.bsky.social · 17/09/2026

Shipped: 12 agent config kits (Next.js, React, Node, FastAPI, Django, Go, Rust, Rails, Laravel, SvelteKit, Astro, .NET), each rendering one baseline into AGENTS.md, CLAUDE.md, Cursor rules and Copilot instructions. 12/12 green or it does not ship.

000

Piekwerk @piekwerk.bsky.social · 17/09/2026

The full Next.js kit from our agent config pack is free: all four formats (AGENTS.md, CLAUDE.md, Cursor rules, Copilot instructions), installer-ready, MIT. It is the exact files buyers get. Judge it against your repo first. Free kit: piekwerk.gumroad.com/l/free-sample-…

020