matthewwong525/WongStack / .agents/plugins/memory
memory
Verifiedreferences/placing-facts.md
View on GitHub# Placing a fact on a page
How the daily tidy puts a fact on a page. A fact goes on a page only when it passes three tests: **will it help a future task that is not this one, will it still be true in six months, and would it change what a reader does?** A fact that fails one stays in memory.
The fact's topic picks the page:
- **A fact with a topic goes on that topic's page.** A fact tagged `people/ada` goes on `knowledge/people/ada.md`.
- **A fact about one person goes on their page; a fact about everyone goes on a topic page.** Different preferences are not contradictions: keep each on its own person's page.
- **A company fact with no topic goes on the page that owns its subject.** No page owns it → make one, and link it from its hub. Then add the page's topic to the fact: the fact keeps its words, date, and author.
- **Each page you change keeps a true first sentence**: a one-line summary of the whole page, because search quotes it.
- **A page never names a fact by its id.** Write what the fact says.
The wrong turns the tests let through:
- **A preference is how a person wants work done, again and again.** A choice about one product feature is that change's decision and stays in its plan: *measure a speed-up before recommending it* is a preference; *Connect your assistant uses the app's login* is not.
- **An interpretation is not a quote.** A fact marked as the assistant's reading, such as *Interpretation, not his words*, goes on a page only when `memory.mjs source <fact-id>` shows the person said as much, and then in their words.
- **One new line per idea, in the bullet that already owns it**, in the page's format. A page growing by over a third in one pass means the test was too loose: apply it again.
- **Never a private name.** No downstream repo, customer, or account detail the repo's checks would refuse; no health, family, or money in a shared repo.
- **Already said is not new.** Skip a fact the page states. Reword a sentence only when a fact contradicts it.
- **Buried is not missing.** When a chat went wrong because guidance was hard to find, move it or reword it where it is. Never write it a second time: a second copy goes stale.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |