Commands
Generate production-ready code from your visual schemas using the AeroCoding CLI. Three commands: login, create, and update.
aerocoding login
Authenticate with your AeroCoding account.
Run the login command
A browser window will open for authentication. After logging in, your session is stored locally.
aerocoding loginInfo
aerocoding create
Generate code from your schema for the first time.
Run the create command
Navigate to your project directory and run:
aerocoding createFollow the interactive prompts
The CLI will guide you through the setup process:
Review generated files
AeroCoding creates an aerocoding-manifest.json that tracks all generated files. This is used by the update command.
{ "projectId": "your-project-id", "templateId": "clean-architecture-dotnet", "generatedAt": "2024-01-15T10:30:00Z", "files": [ { "path": "src/Domain/Entities/User.cs", "hash": "abc123..." }, { "path": "src/Application/UseCases/CreateUser.cs", "hash": "def456..." } ]}What gets generated
A complete, production-ready architecture based on your schema.
Backend
- Entities, Value Objects, Enums
- Use Cases (CQRS pattern)
- DTOs and Mappers
- Repository interfaces + implementations
- REST Controllers with OpenAPI
- Database configurations (EF Core)
- Unit and integration tests
Frontend
- Typed models and interfaces
- API client with typed methods
- Data fetching hooks
- Validation schemas (Zod)
- Form components
aerocoding update
Regenerate code after making changes to your schema.
Make changes in the editor
Add new entities, modify attributes, create relationships — whatever your domain needs.
Run the update command
From the same directory where you ran create:
aerocoding updateThree-way merge (diff3)
The CLI uses diff3 to intelligently merge your changes with schema updates:
| Scenario | Action |
|---|---|
| New entity in schema | Creates new files |
| Entity removed from schema | Asks confirmation before deleting |
| File not modified by you | Overwrites with new version |
| File modified by you | Three-way merge (diff3) |
| Merge succeeds | Combines your changes + new schema |
| Merge has conflicts | Creates .new and .conflict files |
Tip
Typical workflow
How to use the CLI in your development process.
Next steps
Continue learning about AeroCoding.