Curating Domain Taxonomies
Automated clustering offers a quick starting point, but portfolio presentations often require deliberate narrative choices. repotographer separates taxonomy generation from graph rendering so you can curate domain groupings before publishing.
The Curation Workflow
┌─────────────────────────┐│ 1. Suggest Taxonomy │ repotographer suggest <owner> --out taxonomy.json└────────────┬────────────┘ │┌────────────▼────────────┐│ 2. Edit Taxonomy │ Hand-edit domain labels, descriptions, and assignments└────────────┬────────────┘ │┌────────────▼────────────┐│ 3. Render Outputs │ repotographer render graph.json --taxonomy taxonomy.json└─────────────────────────┘Step-by-Step Curation
-
Generate the taxonomy proposal
Run
repotographer suggestto query Gemini and emittaxonomy.json:Terminal window repotographer suggest ghchinoy --out ./taxonomy.json -
Understand the taxonomy schema
taxonomy.jsoncontains two top-level fields:{"generated": "2026-08-22T17:48:26Z","account": "ghchinoy","domains": [{"id": "domain_agentic_ai_protocols","label": "AI Agents, A2A & MCP Systems","blurb": "Architectures, protocols, skills, and tooling for autonomous agents."},{"id": "domain_cloud_api_platform","label": "Cloud Infrastructure, Security & API Platforms","blurb": "Cloud integration middleware, enterprise API tooling, and microservices."}],"assignments": {"repo_a2acli": "domain_agentic_ai_protocols","repo_apikeyscan": "domain_cloud_api_platform"}} -
Apply manual adjustments
- Rename Domains: Change the
labelstring to match your team terminology. - Update Descriptions: Adjust the
blurbstring to clarify the focus of each pillar. - Move Repositories: Change the target domain ID in
assignmentsto reassign a project. - Add New Domains: Append a new object to
domainsand assign repositories to itsid.
- Rename Domains: Change the
-
Render your visual assets
Apply the curated taxonomy to your base graph:
Terminal window repotographer render ./out/graph.json --taxonomy ./taxonomy.json --out ./dist