@letterstory/design 0.2.10 → 0.2.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/PRINCIPLES.md +16 -2
- package/package.json +1 -1
package/PRINCIPLES.md
CHANGED
|
@@ -87,7 +87,9 @@ Add a third for surfaces:
|
|
|
87
87
|
|
|
88
88
|
## Letterpress: Build, Plan, Fix
|
|
89
89
|
|
|
90
|
-
The founders' definitions (All Hands 2026-10-29). Detail in `docs/architecture/one-recipe-engine.md`.
|
|
90
|
+
The founders' definitions (All Hands 2026-10-29). Detail in `docs/architecture/one-recipe-engine.md`. Members see
|
|
91
|
+
the tabs as **Build, Ideas, Fix** (Mathew, 2026-11-07): Ideas is the Plan, one flat list with a goal filter and a
|
|
92
|
+
count (`docs/architecture/plan-strategies.md`); the code keeps the names Plan and Fix.
|
|
91
93
|
|
|
92
94
|
- **Build is unbounded.** It does what the member asks ("build X", "answer Y"). Its execution may read
|
|
93
95
|
the Plan's recipes and Fix's known issues through the MCP, but it has no list of its own, and it never
|
|
@@ -98,10 +100,22 @@ The founders' definitions (All Hands 2026-10-29). Detail in `docs/architecture/o
|
|
|
98
100
|
nothing beats showing a weak row. The fit runs in the app over the account's stored facts and probes
|
|
99
101
|
(checking `llms.txt` is a probe), never in a sandbox: a sandbox takes minutes to start. Plan is reached
|
|
100
102
|
through one headless door, `ask_letterpress` on the MCP, which the dashboard, Slack and the terminal
|
|
101
|
-
all use.
|
|
103
|
+
all use. A row is only what Letter can do fully automatically (Mathew, 2026-11-07): nothing on Ideas asks
|
|
104
|
+
the member a question, and a recipe that needs their input before it can run is not a row.
|
|
102
105
|
- **Fix finds and fixes what is broken.** Models are good at finding errors, so Fix gets more room than
|
|
103
106
|
Plan. It works from a list of known issues (`recipes.kind = known_issue`), not recipes, and also
|
|
104
107
|
catches problems outside that list. A known issue is a family of one mistake with its cases as variations: the
|
|
105
108
|
finder reads only the patterns, the check reads when it is not a mistake (`lib/recipes/known-issues.ts`). Technical problems a rule can decide (broken or missing
|
|
106
109
|
structured data, link previews) are rules (`lib/site/observations/`). A "Z is broken" row belongs
|
|
107
110
|
in Fix's known issues, never in the Plan.
|
|
111
|
+
|
|
112
|
+
## UI copy
|
|
113
|
+
|
|
114
|
+
Headlines, labels, buttons, nav items and data only (Kaya, 2026-11-09: explainer copy makes people ask "can I just
|
|
115
|
+
give this to my Claude?"). No subtitle under a heading, no helper paragraph, no "what this does" blurb, no option
|
|
116
|
+
description, no tooltip that restates its control. Where a line is truly needed (an empty state, an error the user
|
|
117
|
+
recovers from), one plain sentence, ideally under 8 words. No AI tells: "seamlessly", "effortlessly", "powerful",
|
|
118
|
+
"unlock", "leverage", "supercharge", "in just a few clicks", "Whether you're…", em-dash asides, lists of three
|
|
119
|
+
adjectives, "AI-powered". Model-written text shown in the UI follows the same rule: keep the field for agents, and
|
|
120
|
+
either keep it off the page or tighten its prompt. The words themselves are decided once in
|
|
121
|
+
`docs/architecture/copy-pass.md`.
|
package/package.json
CHANGED