Interface craft

The how of Danny's human-facing UI: copy, composition, and interaction shape. Broader design-engineering craft (taste, motion detail, library choice, prototyping) lives in Emil Kowalski's skills. Whether the feature should exist lives in ask-why.

Skill markdown in this repo stays ASCII. Curly punctuation is for user-facing copy the agent writes into the product, chat, or PR prose.

Language and typography

• Sentence case for headings, buttons, labels, and navigation. Not title case. Exception: the document H1 may use title case when it is a brand or product name (e.g. README # Danny's Skills). Proper nouns keep their usual casing.

• Typographic punctuation in UI. Prefer curly apostrophes and quotes in user-facing strings:

  Use	Example
  Apostrophe	You’re all set
  Quotes	Say “Continue” to proceed

  Keep straight ' " in code, paths, shell, JSON, and exact literals the user types (trigger phrases, template section names).

• No em dashes, except a matching pair that wraps an aside in the middle of a sentence: to split up—wow, did you see that?—like this.

• Keep copy scannable. Short sentences. Say who acts next. Avoid vague "processing" when a clearer actor and action are known.