lauren
d7cde2b84e
Punctuation and single-word swaps only. No sentence added or deleted, no restructuring, no new text. - 65 markdown files under pstack/skills. 220 changed lines, every changed line pairs with one base line. - 272 rewrites. 239 semicolons (224 became a period plus a capital, 15 became a comma). 29 connector colons (28 became a period, 1 became a comma). 1 em dash before a list became a colon. 3 word swaps (`public surface` and `smaller surface area` to `API`, `echo the scaffolding` to `echo the structure`). - Label colons, colons before a list or an example, template strings such as `file:line`, and the literal `TL;DR` stay. - Heading, numbered-step, fenced-block, and line counts are unchanged in every file. No frontmatter, code span, or fenced block changes. - o200k tokens of the pstack/skills markdown tree 87,747 before, 87,766 after (+19), because a period plus a capital tokenizes one token longer than a semicolon in a few places. Co-authored-by: Cursor Agent <cursoragent@cursor.com>
1.5 KiB
name, description, disable-model-invocation
| name | description | disable-model-invocation |
|---|---|---|
| principle-foundational-thinking | Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious. | true |
Foundational Thinking
Structural decisions protect option value. Code-level decisions protect simplicity.
Data structures first. Get the data shape right before writing logic. Define core types early, trace every access pattern, and choose structures that match the dominant paths.
At code level, DRY the structure, not every line. Types and data models should converge. Three similar statements still beat a premature abstraction. Prefer explicit over clever. Test behavior and edge cases, not line counts.
Concurrency corollary. Before sharing state between actors, ask "what happens if another actor modifies this concurrently?" If not "nothing", isolate.
Scaffold first. If something helps every later phase, do it first. Ask "does every subsequent phase benefit from this existing?" CI, linting, test infrastructure, and shared types are scaffold. Sequence for option value: setup before features, tests before fixes. Keep commits small and single-purpose.
Each increment should land a coherent abstraction or deepen one that exists. Do not spread a new capability across callers as special-case coordination.
Subtraction comes before scaffolding. Remove dead code first, then lay foundations.