project-learningslisted

# Project Learnings Capture project-specific patterns and anti-patterns into the project's agent configuration file. This creates a self-improving feedback loop where discoveries from debugging, development, and review make future sessions smarter. **Important:** Only project-specific knowledge qualifies. Generic programming advice does not belong in the project configuration. --- ## Step 1: Evaluate Discovery Determine if the finding qualifies as project-specific. The finding must pass at least ONE of these criteria: | Criteria | Example That Qualifies | Example That Doesn't | |----------|------------------------|----------------------| | Would a developer unfamiliar with this project likely hit this issue? | "The `processOrder()` function expects amounts in cents, not dollars" | "Always validate function inputs" | | Is this pattern specific to this codebase's architecture, APIs, or conventions? | "The `UserProfile` type has an optional `metadata` field that is always present at runtime" | "Use TypeScript strict mode" | | Is it something training data wouldn't cover? | "Never call `db.query()` without the `timeout` option — the default is infinite" | "Use async/await instead of callbacks" | **If NO to all criteria -> STOP.** Do not add generic programming knowledge to the project configuration. Return to the calling skill and report that no project-specific learning was found. **If YES to any -> proceed to Step 2.** --- ## Step 2: Read Existing Configuration 1. **