intelligence-learn-from-contextlisted

# Learn from Context Use after repository onboarding is complete and a meaningful preference, working pattern, or recurring friction emerged during the current session and should persist. It runs analyze (read-only), then apply after approval. This skill extends an established project; it does not perform first-run repository analysis or migrate legacy instructions. ## Onboarding gate 1. Locate `<manifest>`, `<content-dir>`, and `<module>`, then run `intelligence status --check`. 2. If setup is missing or inconsistent, stop and ask the user to repair it with `intelligence init`; then use `/intelligence-learn-from-repository`. Do not reproduce CLI mechanics. 3. If the generated header says onboarding is pending, or preserved legacy evidence still has unresolved instructions, stop and route to `/intelligence-learn-from-repository`. A retained `<content-dir>/_backup/manifest.tsv` or converted legacy config alone does not mean onboarding is incomplete; those may remain as intentionally kept evidence after the transitional header and conflicts are resolved. ## Principle: positive framing LLMs follow whatever is named. Negation ("never do X") often draws attention to X. Positive framing ("default to Y", "prefer Y") steers behavior more cleanly. This skill translates user-stated lessons before encoding: - "Don't use NOT-comparison structures" → "State positively what IS" - "Stop generating 3 options" → "Default to one strong recommendation" - "Never pus