Continue learning
This handbook is a stance and a map, not the whole library. Prefer How work flows and Architecture before collecting more tabs.
Companion skill ecosystems
Section titled “Companion skill ecosystems”| Companion | When to go deeper |
|---|---|
| DecisionNerd/dev-skills | The plays this guide maps — install with npx skills add DecisionNerd/dev-skills |
| ProductFeeling | How the product should feel; customer discovery; TTPs for emotion |
| Impeccable | Frontend craft: shape, audit, polish |
| DocSlime | Product docs tree, ADRs, KISS review |
Vendored .agents/skills / .cursor/skills |
Repo-local truth — prefer when present |
Themes to study outside the meme
Section titled “Themes to study outside the meme”- How work flows — Discover → Deliver → Operate → Maintain → Retire
- Habit and return design (without compulsion)
- Incident response and blameless postmortems
- Trunk-based development and small batches
- Observability as product empathy
- Quality regimes — compute vs product vs generative evidence
- Bugs & debt — BugSplat lineage; debt types as named interest
- Quality trace — DocSlime docs + lightweight BDD scenarios
- Agent evals, Langfuse-style tracing, and stop conditions
- Monorepo affected CI and package boundaries
Primary sources worth keeping
Section titled “Primary sources worth keeping”The curated bibliography lives in Sources & grounding — DORA, GitHub Docs, Fowler/Beck, Google SRE & SWE book, OpenTelemetry, OWASP LLM / NIST AI RMF, Diátaxis, and more. Each practice links the subset that justifies that TTP.
Also keep close:
- Norman — emotional design / everyday things
- Kahneman — peaks, ends, and noisy judgment
- Your own
PRODUCT.md/ DocSlimedocs// git history — the only vision that counts for this repo
When stuck, don’t collect more tabs. Run idk-now, reopen Orientation, or return to your path.