Hi Paul,
a note rather than a request, so feel free to close it.
i build Respira, an MCP layer that lets AI agents edit live WordPress sites. one of its features saves a design direction per site (palette, type pairs, spacing, the designer's own rules in plain language) and checks every page an agent builds against it.
the check had nine rules of my own and they were all about the customer's stated intent: off-palette colour, wrong font, banned phrases. what it could not catch was the stuff nobody thinks to write down, because it never occurred to them an AI would do it. eyebrow labels above every heading. gradient text. zero-blur costume shadows. 01/02/03 section ornaments. emoji standing in for icons. monospace worn as a technical costume.
your craft-floor reference is a catalogue of exactly those. i read it, then wrote independent detection against my own rendered-check pipeline: fourteen rules that run against the real painted page at desktop and mobile widths, three more deterministically on markup. the rule set went from nine to twenty two. they ship as the Manifesto Rules, in plugin v8.6.25.
attribution, since Apache 2.0 asks for it and it is the right thing anyway: NOTICE files in both the plugin and the MCP server naming the source and the adapted rule ids, a provenance: "adapted from impeccable (Apache-2.0)" field on every adapted rule, and a credit on the public feature page and in the launch post. source lives at github.com/respira-press.
two things you might find useful.
every one of the twenty two is a warning, and waivable. they are taste defaults, not defects. hard failures stay reserved for objective breakage: off-palette colour, broken layout, contrast, placeholder names left in real pages. the customer's own don'ts always outrank mine, and a waiver is a recorded decision rather than a silent override. that framing came from reading your material and concluding the check should teach rather than police.
and they are universal on every tier, including the free build. it is the taste of the product, not a thing to sell.
thank you for licensing it the way you did. it turned a line in my backlog into a shipped feature in a day.
mihai
Hi Paul,
a note rather than a request, so feel free to close it.
i build Respira, an MCP layer that lets AI agents edit live WordPress sites. one of its features saves a design direction per site (palette, type pairs, spacing, the designer's own rules in plain language) and checks every page an agent builds against it.
the check had nine rules of my own and they were all about the customer's stated intent: off-palette colour, wrong font, banned phrases. what it could not catch was the stuff nobody thinks to write down, because it never occurred to them an AI would do it. eyebrow labels above every heading. gradient text. zero-blur costume shadows. 01/02/03 section ornaments. emoji standing in for icons. monospace worn as a technical costume.
your craft-floor reference is a catalogue of exactly those. i read it, then wrote independent detection against my own rendered-check pipeline: fourteen rules that run against the real painted page at desktop and mobile widths, three more deterministically on markup. the rule set went from nine to twenty two. they ship as the Manifesto Rules, in plugin v8.6.25.
attribution, since Apache 2.0 asks for it and it is the right thing anyway: NOTICE files in both the plugin and the MCP server naming the source and the adapted rule ids, a
provenance: "adapted from impeccable (Apache-2.0)"field on every adapted rule, and a credit on the public feature page and in the launch post. source lives at github.com/respira-press.two things you might find useful.
every one of the twenty two is a warning, and waivable. they are taste defaults, not defects. hard failures stay reserved for objective breakage: off-palette colour, broken layout, contrast, placeholder names left in real pages. the customer's own don'ts always outrank mine, and a waiver is a recorded decision rather than a silent override. that framing came from reading your material and concluding the check should teach rather than police.
and they are universal on every tier, including the free build. it is the taste of the product, not a thing to sell.
thank you for licensing it the way you did. it turned a line in my backlog into a shipped feature in a day.
mihai