Command Overview
Conceptual documentation explaining the design, organization, and usage patterns of EAC commands. These guides help you understand how commands work together and how to use them effectively.
In This Section
| Guide | Description | Lines |
|---|---|---|
| Command Taxonomy | How commands are organized into categories and the principles behind command design | 475 |
| Naming Conventions | Command naming patterns, consistency rules, and how to interpret command names | 458 |
| Common Flags | Global options available across all commands and flag usage patterns | 603 |
| Output Formats | Understanding JSON vs human-readable output, when to use each format | 678 |
Key Concepts
Command Organization
Commands are organized by verb-noun patterns into 14 categories:
- Information Commands:
get(JSON) andshow(formatted) - Creation Commands:
create(AI-powered generation) - Validation Commands:
validate(contract checking) - Workflow Commands:
work,test,build,pipeline,release - Security Commands:
scan - Utility Commands:
serve,templates,update
Design Principles
- Consistency: Similar commands follow similar patterns
- Predictability: Command names clearly indicate their purpose
- Duality: Information available in both JSON and human-readable formats
- Composability: Commands designed to work together in pipelines
Quick Reference
For immediate command usage, see:
Tutorials | How-to Guides | Explanation | Reference
You are here: Reference — information-oriented technical descriptions of the system.