{
  "skill": "data-wiring",
  "note": "Trigger-routing suite (gh#369). expect=trigger: the skill should fire on the prompt in a fresh session. expect=no-trigger: a near-miss owned elsewhere (owner named per case) or generic knowledge with no AdiaUI skill involved. Cases derived from evals/routing-corpus.json's phrases array (gh#355 vetted corpus, with rationale) plus the SKILL.md description's own trigger/NOT-fence language.",
  "cases": [
    { "id": "t01", "prompt": "Wire up the data for this dashboard's summary cards", "expect": "trigger" },
    { "id": "t02", "prompt": "Pick a state pattern for this table — signals or DataClient?", "expect": "trigger" },
    { "id": "t03", "prompt": "Add CRUD with undo support to the invoice list", "expect": "trigger" },
    { "id": "t04", "prompt": "Connect the table-ui to the backend via typed reads and pure mappers", "expect": "trigger" },
    { "id": "t05", "prompt": "Why does my chart-ui drop rows appended after connect?", "expect": "trigger" },
    { "id": "t06", "prompt": "The state change isn't round-tripping through the signal — mutate doesn't update the projection", "expect": "trigger" },
    { "id": "t07", "prompt": "Seed the server-fetched props into this SPA island's client-boot state", "expect": "trigger" },
    { "id": "t08", "prompt": "The SSR framework already fetches the data — wire the initial props into the components", "expect": "trigger" },
    { "id": "t09", "prompt": "Share this piece of state across two components that aren't in the same effect() tree", "expect": "trigger" },
    { "id": "t10", "prompt": "Replace my hand-rolled pub/sub store with something that plugs into effect()/computed()", "expect": "trigger" },
    { "id": "n01", "prompt": "Register the client-side components for this new SPA host", "expect": "no-trigger", "owner": "host-wiring" },
    { "id": "n02", "prompt": "Getting 'HTMLElement is not defined' after upgrading to Next.js", "expect": "no-trigger", "owner": "host-wiring" },
    { "id": "n03", "prompt": "Manage the state for the streaming chat responses in the chat box", "expect": "no-trigger", "owner": "llm-wiring" },
    { "id": "n04", "prompt": "Build the markup for this data table's screen", "expect": "no-trigger", "owner": "screen-composition" },
    { "id": "n05", "prompt": "Pick the on-disk shape for this new rollup app", "expect": "no-trigger", "owner": "project-scaffolding" },
    { "id": "n06", "prompt": "Fix the double route owner — router-ui is mounted alongside the framework's router", "expect": "no-trigger", "owner": "host-wiring" }
  ]
}