What problem does it solve? Navigating the bpmn.io and Camunda modeling ecosystem is hard because functionality is spread across 100+ repositories organized in layers, making it difficult to know which repo owns a package or where a new feature should live. ## Core Features & Use Cases - Repository-to-layer mapping: Look up which repo owns an npm package and which architectural layer it belongs to, from primitives up to the Modeler application. - Dependency chain tracing: Follow chains like feel-editor → properties-panel → bpmn-js-properties-panel using the included dependency graph and conventions. - Programmatic lookup: Filter the bundled repositories.json by layer, repo, or npm name for fast, scriptable queries. - Use Case: You want to add a new FEEL editing feature. Query the skill to learn that FEEL tooling lives in Layer 6, that feel-editor is consumed by @bpmn-io/properties-panel, and that changes likely belong in bpmn-io/feel-editor or bpmn-io/lang-feel. ## Quick Start Ask which bpmn.io or Camunda repository owns a given npm package or where a specific modeling feature should be implemented.
