A catalog-design walkthrough that narrows agent capability resolution through a strict hierarchy and documents the file contracts needed to author valid nodes and items.
Original by NiazMorshed2007Agent workflowsRepository READMESource reviewed
Before you dive in
What you’ll find in the original
Resolve a large capability space hierarchically rather than presenting every tool or skill in one decision.
Give each non-root directory a minimal index with an ID and make item IDs unique within their node.
Require every catalog node to contain an item or subgroup and reject unexpected file shapes early.
Worth knowing
The catalog contract is repository-specific; readers should adapt its invariants rather than assume a Jev platform standard.