Map request keywords to business domains using repository routing documents.
npx skills add https://github.com/hellopoisonx/aim --skill aim-repo-mapping
Please help me install this Agent Skill. Skill: aim-repo-mapping Source: https://github.com/hellopoisonx/aim/tree/main/skills/aim-repo-mapping Command: npx skills add https://github.com/hellopoisonx/aim --skill aim-repo-mapping
When a feature request, bug fix, or change request lands without a clear ownership boundary, this Skill helps you quickly determine which business domain and supporting documentation/config should be used first.
Use the aim-repo-mapping skill to locate the correct domain and references for a request by first checking references/request-to-module-map.md, then references/module-routing.md, and finally switching to the domain Skill named by the routing result.
High-intent search queries and answers about installing and using this skill.
To find the correct business domain for a microservices request, map requirement keywords to the primary domain using the request-to-module-map and module-routing references. This directs you to the specific domain Skill and avoids spending time in the wrong module.
The best way to discover module boundaries for cross-domain changes is to apply repository routing documents that map request keywords to domains. This enforces gateway REST/WS rules and cross-domain handoff conventions to isolate scope accurately.
To locate controller, workflow, or configuration references for an impact assessment, check the request-to-module-map and module-routing documents. This identifies the supporting modules and primary business domain affected by the change request.
Yes, this domain routing approach handles operational questions by pointing to the most relevant references for Docker build conventions and Kafka operational pitfalls. It maps run and infra-related queries to the appropriate module routing rules.
You can use this for bug fixing scoping as well as feature and change requests. It determines the correct business domain and supporting documentation whenever a request lands without a clear ownership boundary.
You should not use request-to-module mapping when the entry point and ownership boundary are already clearly defined. The Skill is designed specifically for situations where the initial domain and supporting modules are unclear.
vndkubiDetect business domains from source code and generate domain-registry.json.
SimHackerList, invoke, and define protocols from a central registry.
CodenburgSearch and install skills from the open agent skills ecosystem via command line.
shanevAnalyze code changes for complexity, coupling, and separation concerns.
