← ClaudeAtlas

ontology-buildinglisted

Builds, extends, reviews, or audits an ontology, domain model, conceptual/data model, taxonomy, or knowledge-graph/property-graph schema — deciding what entities, classes, relations, or aggregates should exist, how to shape a class or role hierarchy, how to scope with competency questions, and how to validate coherence (is-a correctness, anti-patterns, agent-actionability). Use when designing a data model, building a taxonomy, modeling a domain, defining a class hierarchy or knowledge-graph schema, or reviewing an existing ontology/domain model for coherence or AI-agent fitness. Skip for trained ML/statistical models, or routine schema tweaks with no structural decision.
mgillett43/ontology-skills · ★ 2 · Web & Frontend · score 73
Install: claude install-skill mgillett43/ontology-skills
# Building a coherent ontology A domain-agnostic methodology for building ontologies, domain models, taxonomies, and knowledge graphs — independent of what you encode the result in (OWL, a property graph, a relational schema, typed code, a Palantir-style object model). It synthesizes several lineages that don't always agree, and says explicitly where they conflict and which one wins. Full source list and how the lineages are reconciled: [conflicts-and-precedence.md](references/conflicts-and-precedence.md). ## How to use this skill 1. Read this file for the core principles, operating modes, and process. 2. Pick your operating mode before running any steps. 3. Use the reference map to load the specific file for the step you're on — don't front-load all of them. 4. When two pieces of guidance seem to disagree, check [conflicts-and-precedence.md](references/conflicts-and-precedence.md) first — most apparent conflicts are already resolved there, not genuinely open. ## Reference map **Core loop — the seven-step process below runs through these:** | File | Load it when... | |---|---| | [competency-questions.md](references/competency-questions.md) | Scoping — eliciting/grading competency questions and peer schema requirements | | [reuse-and-alignment.md](references/reuse-and-alignment.md) | Deciding whether to adopt/map an external standard, vocabulary, or pattern | | [hierarchy-and-structure.md](references/hierarchy-and-structure.md) | Defining classes, hierarchy, or relations