Author SEA-DSL files with CQRS annotations and namespace conventions.
npx skills add https://github.com/GodSpeedAI/SEA --skill sea-dsl-authoring
Please help me install this Agent Skill. Skill: sea-dsl-authoring Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/sea-dsl-authoring Command: npx skills add https://github.com/GodSpeedAI/SEA --skill sea-dsl-authoring
This Skill helps engineers and architects author semantically valid SEA-DSL specifications with correct CQRS annotations, validation patterns, and namespace conventions, reducing errors and enabling governance-ready designs.
Start by creating a SEA-DSL file for your bounded context, declare a namespace and version, add Entities, Resources, and Flows with the required CQRS annotations, and run the standard validation steps (sea-validate, sea-parse, flow-lint) to ensure correctness.
High-intent search queries and answers about installing and using this skill.
To add CQRS annotations to SEA-DSL specifications, you declare entities, flows, resources, and policies using nested CQRS annotations. This enforces proper namespace conventions and validation patterns, ensuring your artifacts are semantically consistent and governance-ready.
The best way to validate SEA-DSL files is to run standard validation steps including sea-validate, sea-parse, and flow-lint. These checks enforce nested CQRS annotation rules and namespace conventions to catch syntax and semantic errors.
You need namespace conventions in SEA-DSL authoring when creating or modifying specifications across a bounded context. Enforcing namespaces ensures consistency across entities, flows, resources, and policies, making the design validation-ready.
Yes, SEA-DSL supports defining both entities and flows with validation rules. You can create specifications that include entities, resources, and policies alongside flows, applying required CQRS annotations to maintain semantic validity.
To structure a bounded context in SEA-DSL for production readiness, you create a file, declare a namespace and version, add components with CQRS annotations, and run validation steps like sea-validate to ensure correctness.
Your SEA-DSL validation may fail when modifying bounded context specifications if nested CQRS annotations are missing or namespace conventions are violated. Enforcing these rules ensures entities, flows, and policies remain semantically valid.
GodSpeedAIAuthor SDS YAML documents mapping to SEA-DSL for domain models and CQRS operations.
GodSpeedAIValidate governance constraints and architecture boundaries across SEA project changes.
RomualdPGenerate CQRS commands, queries, handlers, and read models with class-validator DTOs.
XaxisGuide creation of bix.bot domain schemas with traits, entities, and constraints.
