What is the difference between a Law Card and a Term Card?

A Law Card documents a specific business constraint or rule (such as 'Available = Total - Reserved'), while a Term Card defines a domain concept, its technical type, and validation boundaries.

How does this skill improve system observability?

Each Law Card requires the definition of Telemetry or Log/Event fields, ensuring that business rule violations are proactively monitored and observable in production.

Can I use this for existing codebases?

Absolutely. It is highly effective for 'Discovery' phases where you document existing logic into a structured Law/Term format to improve maintainability and test coverage.

Why does the skill require linking Laws to Terms?

Linking ensures that every business rule is grounded in a specific domain concept. This prevents 'relation soup' where rules are defined without clear, standardized vocabulary.

ELD Spec Card Generator

Name: ELD Spec Card Generator
Author: CAPHTECH

byCAPHTECH

0•

Learning & Documentation

Standardizes the documentation of business constraints and domain vocabulary through structured Law and Term cards.

This skill provides a robust framework for documenting domain-driven designs by integrating Law Cards and Term Cards. Law Cards define business invariants, pre/post-conditions, and policies with associated severity and observability metrics, while Term Cards standardize domain vocabulary, technical types, and validation boundaries. It is particularly useful for teams needing to bridge the gap between business requirements and technical implementation, ensuring that every business rule is linked to a verifiable test and a clear domain concept to prevent architectural decay.

Key Features

01Severity-based violation handling and ownership assignment for critical business rules.

02Structured Term Card creation for domain-specific vocabulary, technical types, and validation logic.

030 GitHub stars

04Integrated mapping between business laws and domain terms to ensure consistency.

05Standardized templates for verification (testing) and observability (telemetry) requirements.

06Automated Law Card generation for business constraints including Invariants, Pre/Post, and Policies.

Use Cases

01Creating a Grounding Map that links business rules directly to automated tests and runtime monitoring.

02Documenting complex business logic and invariants during the system discovery phase.

03Updating project Law and Vocabulary Catalogs as domain requirements and technical constraints evolve.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add caphtech/claude-marketplace eld-spec-card

For use in Claude.ai and ChatGPT

Key Features

01Severity-based violation handling and ownership assignment for critical business rules.

02Structured Term Card creation for domain-specific vocabulary, technical types, and validation logic.

030 GitHub stars

04Integrated mapping between business laws and domain terms to ensure consistency.

05Standardized templates for verification (testing) and observability (telemetry) requirements.

06Automated Law Card generation for business constraints including Invariants, Pre/Post, and Policies.

Use Cases

01Creating a Grounding Map that links business rules directly to automated tests and runtime monitoring.

02Documenting complex business logic and invariants during the system discovery phase.

03Updating project Law and Vocabulary Catalogs as domain requirements and technical constraints evolve.