aboutsummaryrefslogtreecommitdiff
path: root/inbox/PROCESSED-2026-07-05-0420-from-archsetup-proposal-incoming-ui-prototyping.org
diff options
context:
space:
mode:
Diffstat (limited to 'inbox/PROCESSED-2026-07-05-0420-from-archsetup-proposal-incoming-ui-prototyping.org')
-rw-r--r--inbox/PROCESSED-2026-07-05-0420-from-archsetup-proposal-incoming-ui-prototyping.org5
1 files changed, 0 insertions, 5 deletions
diff --git a/inbox/PROCESSED-2026-07-05-0420-from-archsetup-proposal-incoming-ui-prototyping.org b/inbox/PROCESSED-2026-07-05-0420-from-archsetup-proposal-incoming-ui-prototyping.org
deleted file mode 100644
index 480d006..0000000
--- a/inbox/PROCESSED-2026-07-05-0420-from-archsetup-proposal-incoming-ui-prototyping.org
+++ /dev/null
@@ -1,5 +0,0 @@
-#+TITLE: Proposal incoming (ui-prototyping-process-proposal.org): a U
-#+SOURCE: from archsetup
-#+DATE: 2026-07-05 04:20:42 -0500
-
-Proposal incoming (ui-prototyping-process-proposal.org): a UI/UX prototype process for specs with a non-trivial UI — research-first during brainstorming, then ~5 full working prototype directions, iterate one to final, name <spec-name>-prototype-<N>.html, link final in the spec + keep old iterations in the spec history. Worked example is archsetup's timer-panel spec + its 3 prototypes. Suggested it fold into spec-create/spec-review or a new ui-prototyping rule — your value gate decides placement.