dx-authoring

Create and validate dx language declarations in Markdown specifications.

1|Updated May 12, 2026

Search Tags:#architecture #linting #markdown #specification #dx #contracts

Ready to run

npx skills add https://github.com/dewitt/dx --skill dx-authoring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dx-authoring
Source: https://github.com/dewitt/dx/tree/main/skills/dx-authoring
Command: npx skills add https://github.com/dewitt/dx --skill dx-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in software architecture by providing a standardized, machine-verifiable way to document system intent, invariants, and contracts.

Core Features & Use Cases

Structural Enforcement: Ensures all declarations follow the canonical dx grammar, preventing structural errors in system specifications.
Assumption Tracking: Provides a formal protocol for recording heuristic choices before they leak into implementation code.
Use Case: Use this skill when drafting a new system specification to ensure your intent, invariants, and contracts are clearly defined and lint-ready for coding agents.

Quick Start

Load this skill and ask it to validate your current markdown declaration file against the dx structural rules.

Frequently Asked Questions about dx-authoring

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

FAQPage Schema

How do I define architectural contracts and invariants in markdown specifications?▼

To define architectural contracts in markdown specifications, you use the dx language to standardize system intent, invariants, and assumptions into a machine-verifiable format. This enforces structural grammar to support automated linting and diffing.

What is the best way to lint system specifications for architectural consistency?▼

The best way to lint system specifications for architectural consistency is by validating your markdown declarations against strict dx structural rules. This process checks logical constraints and structural grammar to eliminate ambiguity in your software architecture.

Can I track assumptions and heuristic choices before they leak into implementation code?▼

Yes, you can track assumptions before they leak into implementation code by using a formal protocol within dx declarations. This provides a standardized method for recording heuristic choices directly inside your markdown-based system specifications.

How do I validate my current markdown declaration file against structural rules?▼

To validate your markdown declaration file, you load the dx-authoring skill and request validation of your document against canonical dx grammar. This enforces strict structural constraints to ensure your declarations are lint-ready for coding agents.

When do I need machine-verifiable documentation for software architecture intent?▼

You need machine-verifiable documentation for software architecture intent when you want to eliminate ambiguity across software implementations. It ensures system invariants and contracts are clearly defined and structurally enforced before coding agents begin processing.