learned-codemap-generator-hygiene

What problem does it solve?

Patterns for maintaining a codemap generator that stays useful over time. This skill helps frontend teams keep their codemap generators hygienic and durable during updates.

Core Features & Use Cases

• Generate high-signal maps that answer:
  • where is the screen wired? (routing)
  • where are providers composed? (providers)
  • what is the facade/use-case entry? (application)
  • where is state/caching? (state)
  • what is the cross-context surface? (public APIs)
• Keep outputs stable by sorting lists, capping samples, and avoiding per-file line counts.
• Use domain-accurate taxonomy to avoid misleading subsystem names in frontend apps.
• Treat generated outputs as an atomic set to ensure consistency across regenerations.
• Make the generator reproducible by pinning the runner, adding an npm script, and documenting generated docs for agents.

Quick Start

Review or update a frontend Angular codemap generator following these hygiene guidelines to produce stable, domain-accurate maps.