• Prompts and skills explain intent. Good abstractions turn that intent into executable contracts.
    • Can this rule be enforced through types?
    • Can it be moved into a safer default?
    • Can the component itself own accessibility and interactions?
    • Can we split abstractions so that once the user chooses a purpose, the rest follows naturally?
  • The best harness starts with abstractions, before prompts.