design-api

You can generate detailed API specifications by processing domain names, session data, and domain models to automatically produce an `api-spec.md` file. This file includes comprehensive API lists, precise request/response models, and step-by-step pseudocode for complex logic.

The best way to document request and response models is to define precise fields, data types, validation rules, requirement statuses, and error messages. This ensures strict formatting and clarity for API inputs and outputs within a single Markdown specification document.

You can generate pseudocode for complex API logic by applying domain-driven design principles to your domain models. The system creates clear, step-by-step pseudocode that adheres to strict formatting guidelines while filtering out unnecessary technical jargon.

No, predefined domain models and session data are required inputs. The specification generation process relies on these inputs to accurately define request/response structures, field validation rules, and the pseudocode required for handling complex domain logic.

To include validation rules and error messages, generate your API documentation with strict field formatting. The output Markdown file enforces precise definitions for field types, requirements, validation constraints, and error messaging to ensure complete API clarity.