{"version":"2.1.232","anchor":"prototype-skill-behavior-prototypes-one-design-question-veri","canonical_anchor":"prototype-skill-behavior-prototypes-one-design-question-veri","heading":"Prototype skill: behavior prototypes, one design question, verified shell reuse","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/prototype-skill-behavior-prototypes-one-design-question-veri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Prototype skill: behavior prototypes, one design question, verified shell reuse\n\nThe prototype skill now covers behavior prototypes and asks for one named design question.\n\n**What**\n\nThe prototype skill now covers prototyping how something behaves rather than how it looks, asks you to name the single design question at the top of the page, and adds a checked procedure for reusing a hosted app shell.\n\n**Details**\n\n- Behavior prototypes keep the logic in a pure module with no DOM access, show full state after every step, and include a guided walkthrough.\n- Variations go into one artifact behind a visible switcher, and they must differ structurally rather than cosmetically.\n- Reusing a hosted shell means hashing the local copy and comparing it to the registry's recorded `artifact_sha256` in a single command that prints only MATCH or MISMATCH, instead of comparing digests by eye.\n\n**Evidence**\n\n`## When the question is behavior`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}