claude-config-self-development-researchlisted

# Self-development research Simon's config is a living system. It drifts in three directions at once, and none of them announce themselves: - **The platform moves.** Claude Code ships features that make a hand-built mechanism redundant, or quietly changes one his config depends on. - **The packs move.** Third-party skills are cloned once and then sit there. Upstream keeps shipping. - **The config rots in place.** A rule claims a behaviour that no longer happens. A doc names a mechanism that was replaced. Nothing fails, so nothing surfaces it. This skill goes and looks. It produces a proposal, not a change. ## The bar — the whole point of this skill Simon's instruction: **not so loose that it suggests minute half-improvements, not so tight that it misses genuinely new developments.** The bar is what makes this skill useful rather than noise, so apply it hard. **A finding qualifies only if at least one is true:** 1. Something is **silently broken or not doing what it claims** — a rule that never loads, a guard that cannot fire, a doc that describes a mechanism that no longer exists. 2. The platform now has a **first-class feature** that replaces something hand-built, or that closes a gap his own rules say is open. 3. A dependency, pack or tool is **stale enough to matter** — months behind, deprecated, abandoned, or superseded by something with clearly wider adoption. 4. A **new capability** exists that would change how he works, not just how something is s