rdf-ontologies

Master RDF ontologies and Turtle (TTL) syntax. Use for creating feature specifications, domain models, architecture plans with semantic web standards. Covers: Turtle syntax, SPARQL queries, Oxigraph RDF store, SHACL validation, .specify/ workflow. When designing features, modeling domains, writing specifications, or querying RDF data.

⭐1stars🔀1forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

This Claude skill enables advanced domain modeling and architecture planning using RDF ontologies and Turtle (TTL) syntax. It streamlines the creation of technical feature specifications by treating semantic data as the 'source of truth,' integrating with tools like Oxigraph and SHACL for rigorous validation and automated documentation rendering to ensure architectural consistency.

Use Cases

  • Domain Modeling: Define complex system entities and their relationships using semantic web standards to create a machine-readable and logically consistent architectural foundation.
  • Feature Specification Management: Utilize Turtle (TTL) files as the primary source of truth for software features, enabling automated validation and markdown generation through specialized workflows.
  • Architecture Documentation: Develop structured architecture plans that leverage SPARQL queries and SHACL validation to maintain high-quality, verifiable, and synchronized technical documentation.
namerdf-ontologies
description"Master RDF ontologies and Turtle (TTL) syntax for feature specifications, domain models, and architecture plans."
allowed_tools"Read, Write, Edit, Bash(cargo make speckit:*)"

RDF Ontologies Skill

What is RDF?

Resource Description Framework: Semantic web standard for expressing knowledge as triples

Subject → Predicate → Object
Alice → hasEmail → alice@example.com
Feature-001 → hasTitle → "Test Audit"

Turtle (TTL) Syntax

@prefix spec: <http://ggen.io/spec/> .

spec:feature-001 a spec:Feature ;
    spec:title "Feature Title" ;
    spec:priority spec:P1 ;
    spec:hasUserStory spec:us-001 .

spec:us-001 a spec:UserStory ;
    spec:title "As a user..." ;
    spec:hasAcceptanceCriterion spec:ac-001 .

Workflow

  1. Create .specify/specs/NNN-feature/*.ttl
  2. Validate: cargo make speckit-validate
  3. Render markdown: cargo make speckit-render
  4. TTL is source of truth (never edit .md)

Reference

See CLAUDE.md sections:

  • Development Workflow (Create Feature Specification)
  • File Organization (.specify/)
  • Agents: speckit-architect