Pending delete tagged todelete: no changes until it is deleted, or a person removes the tag

ai:skills › d3-f-designer · version 1 ·
HistoryMarkdown
name
d3-f-designer
description
The designer's ways of working with its person — design reviews, folding answers, thoughts and streaks into tasks, coder tickets. Read the sections tagged with your role ({role: <your role>} or {role: all}). Errors at the end.
tags
#skill #designer #d3skill #wip #todelete
project
d2spec

d3-f-designer: working with your person✎ edit

Design reviews {role: designer}✎ edit

When your person asks for a design for a design they ask for (a #feature or #idea thought, or in a chat), file one review task for them (kind: review) and say in one line where it is. Its document, in this order:

  1. Look at: the mockup link first (UI always gets a mockup; show it in the chat too).
  2. said: their words quoted verbatim, with where and when; related thoughts or tasks linked, and what you left out.
  3. Design (for review): numbered parts, a few tight bullets each — the behaviour, the small calls decided, names and routes; your pick when they asked for suggestions.
  4. Docs and skills (after your OK) and Coder tasks I'd file (after your OK): what will change, so nothing surprises them.
  5. Questions: numbered, one line each, only what you truly can't decide; then the answer marker **↳ Your answer:**, last.
  • The chat reply mirrors it, short: the link; one small bullet block per part in your own words (it shows you understood); the questions again in one line each; what you left out and why. Never paste the document.
  • When the answers come back (Return on the task, or in a chat): fold each answer, by number, into the design; draft Spec/SpecUi/Design and the skills (the feature skill and the live skill in the same change, with a history entry); file the coder tasks, parked until they say send; append ## Done (<you>) to the review task saying what landed where, and close it. Reply: the answers as folded (by number), drafts and tasks with links and one line each, and anything you noticed on the way (it becomes a task too).
  • Thoughts that became tasks get Became task P-n and are archived; one not fully handled stays unarchived, saying what's missing.

Thoughts and streaks {role: designer}✎ edit

  • A thought @designer and a streak follow d3-f-thoughts › direct and d3-f-thoughts › streak: answer in the thought, terse; bundle a streak into tasks as if typed in a chat; Became task P-n, then archive.
  • When your person says roll up / pick up the #bug thoughts: group them per component or feature (split only when too big, never two tasks on the same code), fold small ones into an open task in the same area if it isn't taken (else a new task waiting on it), mark each thought, archive only what's fully handled.

Coder tickets {role: designer}✎ edit

  • Self-contained (quotes over links, under ~15K with what it links), Look at first, Read only these docs (section links), Code pointers, Decided for you, Changes (codes), Done when (black-box tests), fields summary, size, touches, supersedes, codes, feature. Spec/SpecUi/Design drafted in the same change. Never rewrite a taken item's document — add a note or file a follow-up waiting on it.
  • Send only on your person's word; until then file them parked.

Errors {role: designer}✎ edit

  • E_TICKET / E_TICKET_WARN — the ticket check found a missing part or a doubtful one; the message names each.