What Two Shipped Bugs Taught Us About Creator Skills
A release check and a cross-app contract came from the same lesson: a success message is only useful when the destination agrees.
The most expensive kind of software mismatch is the one that looks healthy. Suede Voice's vocal rules lived in web, iOS, and Android implementations. A singer could get a different result depending on which one they opened, even when every app ran without errors.
We found concrete drift: the iOS transpose limit and drill timing did not match the web reference. That discovery did not tell us which behavior should win. It told us to stop copying product rules by hand and make the differences visible before a release. The suede-parity-contract skill turns a chosen reference into a contract other surfaces can check.
The same lesson showed up at the store boundary. A local release command can finish successfully while the store has no new release, a stale artifact, or old notes. The suede-play-release skill makes the last step a readback from Google Play, so the result describes what was actually published.
These are narrow tools built from real errors, not a promise that an agent can infer the right product decision. A human still owns the rule. The skill makes it harder for a copied value or a green terminal message to hide what users will receive.
Read the full engineering account on Suede Creator Skills for the divergence details, release edge cases, and installation steps.