lde-model-term-card

Create standardized Term Cards for LDE domain vocabulary.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill lde-model-term-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lde-model-term-card
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/eld-model-term-card
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill lde-model-term-card

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts Vocabulary into formal Term Cards, enabling precise domain modeling and observable boundaries.

Core Features & Use Cases

  • Term Card structure for Entity/Value/Context/Boundary
  • Synonyms, Observables, and IO Boundaries
  • Related Laws linkage for S0/S1 Terms

Quick Start

After Vocabulary discovery, generate a Term Card for the term and map it to related Laws.

Frequently Asked Questions about lde-model-term-card

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a Term Card and why do I need one for domain vocabulary?

A Term Card is a standardized structured document that formalizes domain vocabulary by defining a term's type, value, meaning, and observable boundaries. It enables precise domain modeling by classifying terminology and linking related business rules, ensuring consistent interpretation across systems.

How do I create a Term Card for a new domain term?

Generate a Term Card by applying structured classification: define the Term name, assign its Type and Value, specify Meaning and Context, establish IO Boundaries and Validation rules, enable Observable Fields, and link related Laws via a map. Execute this workflow after vocabulary discovery.

What's the difference between Entity, Value, and Context in a Term Card?

Entity represents the domain object being defined; Value captures the concrete data or state it holds; Context specifies the operational environment and boundaries where the term applies. Together they formalize how terminology behaves within your domain.

Can I use Term Cards to document synonyms and related terms?

Yes. Term Cards support Synonyms and Observable Fields to map equivalent terminology, and include a link map to connect related Laws and terms. This enables traceability and consistent vocabulary across multiple representations.

When should I update an existing Term Card versus creating a new one?

Update an existing Term Card when refining meaning, context, or boundaries of a known term. Create a new card only when introducing genuinely distinct terminology. Term-carding applies during vocabulary addition, updates, catalog entry creation, or Phase D formalization.

How do Term Cards enforce validation and observable boundaries?

Term Cards specify IO Boundaries that define input and output constraints, and Validation rules that enforce data integrity. Observable Fields mark which term properties are measurable or traceable, enabling runtime verification and compliance monitoring.