Learning document template
Required: the document must start with YAML frontmatter. It feeds the search index and is how other members discover the learning.
---
title: "<short title naming the core problem or finding>"
author: <username>
date: <YYYY-MM-DD>
tags: [tag1, tag2, tag3]
related:
REFERENCES: [skills/skill-name-1, skills/skill-name-2]
---
## Context
What were you doing? What problem did you hit?
## Solution
How did you solve it? What were the key steps?
## Lessons
- Lesson 1
- Lesson 2Frontmatter fields
| Field | Required | Meaning | Example |
|---|---|---|---|
| title | yes | Short title (under 60 characters) | "Diagnosing K8s Pod OOM kills" |
| author | yes | Contributor's username | jeffyxu |
| date | yes | Date as YYYY-MM-DD | 2026-03-28 |
| tags | yes | 2-5 key tags | [k8s, oom, troubleshooting] |
| related | no | Relations to other team resources, shown on recall hits. A learning may use REFERENCES (any resource), MAPS_TO (a teamwiki page), SUPERSEDES and CONFLICTS_WITH (a doc or learning). Disagreeing with a rule is CONFLICTS_WITH: teamai contribute publishes without review |
REFERENCES: [docs/payments-overview.md] |
| session | no | The session the learning came from. Leave it out: teamai contribute writes it |
{ platform: claude-code, sessionId: 7c1e… } |
Choosing tags
Pick 2-5 from these categories:
- Stack: python, typescript, go, k8s, docker, sglang, cuda
- Problem type: troubleshooting, performance, deployment, config, api
- Pattern: workflow, pattern, tool-usage, best-practice
- Scenario: debugging, testing, monitoring, security