Semprini
@Semprini
Public Skills
concept-explorer
by Semprini
Use this skill when the user asks "what is [concept]", "how does [feature] work", "explain [section]", "compare MD-DDL to [tool]", "why does MD-DDL [design choice]", or any question about a specific part of the standard. Also use when the user wants to understand the reasoning behind a design decision or the trade-offs between alternatives (entity vs enum, canonical vs bounded context, etc.).
orientation
by Semprini
Use this skill on first contact, when the user asks "what is MD-DDL", "where do I start", "what can I do here", or describes their role and goals. Also use when the user asks for a general overview of the standard, the agent ecosystem, or the workflow.
platform-setup
by Semprini
Use this skill when the user mentions VS Code, Claude Code, Copilot, or any IDE; asks about setup, installation, or configuration; asks "how do I use the agents"; asks "getting started with [platform]"; or needs help with platform-specific workflows, troubleshooting, or effective prompt patterns.
worked-examples
by Semprini
Use this skill when the user asks to see an example, says "walk me through", "show me how [concept] looks in practice", mentions the Simple Customer or Financial Crime example, or wants to understand how a complete MD-DDL model is structured. Also use when a user asks for a concrete demonstration of a concept after it has been explained.
standards-alignment
by Semprini
Use this skill when the user mentions a named industry standard (BIAN, ISO 20022, FHIR, ACORD, TM Forum, etc.), when modelling a recognised industry domain (banking, payments, insurance, healthcare, telecoms, retail), or when populating the Reference column of any MD-DDL summary table. Also use when the user asks whether a concept already exists in a standard, or when two modelled concepts might map to the same standard object.
dimensional
by Semprini
Use this skill when the user asks for a physical dimensional model, star schema, fact/dimension design, bridge strategy. Also use when deciding how existence, mutability, and temporal tracking should influence physical realization.
normalized
by Semprini
Use this skill when the user asks for a normalized operational model, practical/pragmatic 3NF, OLTP schema design, or non-dimensional physical outputs. Also use when producing database DDL, JSON Schema, or Parquet-oriented schema contracts from MD-DDL.
odps-alignment
by Semprini
Map MD-DDL data product declarations to Open Data Product Specification (ODPS) v4.0 YAML manifests for external cataloguing, marketplace publication, and cross-platform interoperability. Use when the user wants to publish data products, generate ODPS YAML, or align with external data product standards.
product-design
by Semprini
Design and declare MD-DDL data products from an existing domain model. Use when the user wants to create, update, or review data product declarations — choosing product class, schema type, entity scope, governance overrides, masking strategies, cross-domain references, or SLA. Also use when populating the domain file Data Products summary table.
compliance-audit
by Semprini
Systematically evaluate MD-DDL domain and entity files for governance metadata completeness and correctness against loaded gulatory frameworks. Use when auditing a domain file or corpus for compliance gaps, when the user asks "is this compliant" or "what's missing", when preparing a gap report, or after a regulatory monitoring pass identifies a potential impact. Always load the regulatory-compliance skill and relevant regulator files before running an audit — this skill defines how to audit, not what the requirements are.
knowledge-graph
by Semprini
Use this skill when the user asks to generate a knowledge graph, graph database schema, Cypher DDL, or Neo4j model from an MD-DDL domain. Also use when the user wants to realize MD-DDL entities, relationships, events, and enums as labeled property graph structures.
wide-column
by Semprini
Use this skill when the user asks for wide-column reporting schemas, denormalized columnar marts, one-table analytics models, or join-minimized read models from MD-DDL.
relationship-events
by Semprini
Use this skill when connecting entities with relationships, when modelling what happens when something changes (business events), when cardinality or ownership questions arise, when the user asks "what happens when X" or "who initiates Y", or when deciding whether something is a relationship attribute vs. an entity attribute. Also use when the user asks about event payloads, downstream impacts, or temporal sequencing of business state changes.
domain-scoping
by Semprini
Use this skill when starting a new domain model, when the user says "model this domain" or describes a business area from scratch, when scoping or boundary questions arise, or when choosing between canonical and domain-driven modelling strategies. Also use when the user asks who should own a concept or whether two concepts are the same thing across different domains.
entity-modelling
by Semprini
Use this skill when modelling entities or their attributes, when the user says "types of" or "kinds of" something, when inheritance questions arise, or when deciding whether a concept should be a first-class entity, an enum, an attribute, or a relationship attribute. Also use when the user is unsure whether two similar concepts are the same entity or separate ones.
domain-review
by Semprini
Use this skill when the user asks to review, audit, validate, or quality-check an existing MD-DDL domain and its detail files. Also use before declaring a domain “complete” or production-ready. This skill performs both structural conformance checks and decision-quality checks for relationship granularity, temporal tracking, existence, mutability, conceptual-to-logical realization, standards alignment, and regulatory posture.
regulatory-compliance
by Semprini
Apply regulatory and compliance metadata to MD-DDL entities based on applicable jurisdictions and frameworks. Use when modeling domains with regulatory requirements or when user mentions compliance, regulations, or specific regulatory bodies (APRA, RBNZ, GDPR, Basel, etc.).