Latest article
One ruleset, three persistence models in i-have-adhd
Trace startup injection, per-turn transformation and Pi session state without flattening them into a generic plugin diagram.
Nine source-backed lessons on output structure, reversible installation, host lifecycles and honest evaluation, with fourteen isolated adapter cases.
Latest article
Trace startup injection, per-turn transformation and Pi session state without flattening them into a generic plugin diagram.
By publication date
01 → 09
Trace startup injection, per-turn transformation and Pi session state without flattening them into a generic plugin diagram.
Compare response-style delivery options by persistence, review surface and rollback rather than unmeasured product rankings.
Distinguish a Markdown skill from executable adapters, pin the reviewed revision and plan a narrow rollback before global installation.
Use a small learning task to check activation, explanation quality and exit behavior before considering always-on configuration.
Design a small, auditable project with clean conditions, blinded review and blocker-first decisions; distinguish the proposal from a shipped tool.
Learn what this output-style skill changes, how its adapters deliver instructions, and where readability claims stop short of evidence.
Account for injected context, output, retries and judging, and interpret the upstream failed release gate without cherry-picking improvements.
Review executable hooks, configuration boundaries and unsupported certainty before turning a response style into a persistent team default.
Follow actual source branches and fourteen offline cases, including an empty rules file and preservation of an existing OpenCode command.