01
Describe the outcome
Explain what should happen, who can do it and what each person can see. Start with the behavior your product needs.
Open source. Ready for your next idea.
Build the part that makes your product yours. Start with identity, users, files, email and infrastructure already connected — and a shared workflow that helps your AI assistant extend them with care.
C# / .NET 10 · Angular 22 · Aspire 13
Built for the way we build now
The first feature should not begin with another round of authentication, storage and infrastructure setup. AspireBoot brings those pieces together, with explicit rules for how new work fits in.
01
Explain what should happen, who can do it and what each person can see. Start with the behavior your product needs.
02
Codex, Claude Code, Gemini CLI and GitHub Copilot follow the same six skills for backend, frontend, testing, security and performance.
03
Ask for working behavior and relevant checks. Review the code and verification results as you evolve your application.
AGENTS.md + .agents/skills
Codex · Claude Code
Gemini CLI · GitHub Copilot
A starting prompt for your assistant
Follow the project's instructions.
Customers can create orders with a description and a
positive amount, see only their own orders, and receive
an email when they confirm an order.
Keep the same look and feel as the rest of the app.
Ask me if any detail is unclear. Check that everything
works and each customer only sees their own orders.Connected from the first run
From the browser to background delivery, the template connects these tools through existing features and shared conventions.
A responsive browser app and an API with explicit contracts.
ASP.NET Core Minimal APIs
Standalone components · signals · RxJS
Responsive UI · light and dark themes
OpenAPI reference in Development
Persistence, account protection and revocable sessions.
Application data · Identity · durable messages
Npgsql · repositories · migrations
Accounts · roles · secure cookies
Cache · session tickets · email limits
Durable events connect account actions to background work.
Transactional Outbox/Inbox · retries
Durable queues · event transport
Asynchronous email · external SMTP service
Private avatars · temporary signed URLs
Local orchestration, telemetry and checks across the application.
AppHost · service wiring · dashboard
HTTPS routing · production static files
Logs · traces · metrics · health checks
Backend unit tests · real-container integration
Frontend tests · HTTP contracts · coverage
Good defaults. Explicit boundaries.
A working starting point for the details that are easy to postpone when you are excited about an idea.
ASP.NET Core Identity, HttpOnly / Secure / SameSite cookies, CSRF protection, password recovery and email confirmation.
Owner and administrator rules, request limits, session expiration and revocation. Each response exposes the fields its reader may access.
S3-compatible storage with private buckets, temporary URLs, server-side avatar validation and scheduled orphan cleanup.
Transactional Outbox/Inbox, RabbitMQ with Wolverine, retries and failed-message storage. Email delivery runs in the worker.
More product. Less assembly.
Use the included account application as a working example, then extend the same patterns into your own domain.
Directory, profile details, name and photo editing, with owner-aware actions.
Email and password changes, access history, session management and account soft deletion.
Responsive Angular, signals, Tailwind, light / dark themes and English / Portuguese.
PostgreSQL and EF Core, Redis caching, events, audit processing and queued email.
OpenTelemetry logs, traces and metrics, health checks, Aspire dashboard and Scalar in Development.
xUnit / Testcontainers, Angular Vitest tests and CI for builds, dependency audits and coverage.
One environment. Clear responsibilities.
Vertical Slice and Screaming Architecture organize the code by capability. Clean Architecture principles separate HTTP contracts in Api, application behavior in Core, adapters in Infrastructure and event consumers in Worker. Aspire AppHost connects the local environment.
AspireBoot.AppHost · local orchestration
01 / Browser request
Shared application boundaries
02 / Durable background delivery
ServiceDefaults → OpenTelemetry · health · resilience
Make it your starting point
Get the source, prepare your local environment and launch the AppHost. Then describe the first feature you want to build.
Local prerequisites
.NET SDK 10.0.403 · Node.js 26.x · npm 12.2.1 · Docker-compatible runtime · mkcert · SMTP service
git clone https://github.com/crisbraatz/AspireBoot.git
cd AspireBoot
# Full setup guide: README.md
dotnet run --project AspireBoot.AppHost \
--launch-profile httpsFollow the README to install dependencies, create trusted local certificates and configure SMTP before starting. AppHost orchestrates the local stack. You can also run the services independently.
It is an open-source application foundation with shared instructions and a feature-delivery workflow for coding assistants. You bring your assistant and review what it builds.
Prepare production configuration first: secrets, HTTPS, SMTP, private storage, migrations, backups and the deployment topology. The README includes a before-deployment checklist.