Skip to content

betaio/LLMTestProject

Repository files navigation

{{PROJECT_NAME}}

{{DESCRIPTION}}

Template: TheSereyn.Templates.Blazor

Full-stack template for .NET projects with Minimal APIs, Blazor UI, Worker Services, and shared contracts.

Note: Running @workspace /project-setup in Copilot Chat will collect your project details and rewrite this README as your project's own documentation.

Getting Started

Prerequisites

First-Time Setup

  1. Complete the pre-container setup — install prerequisites on your local machine
  2. Click "Use this template" on GitHub to create your new repository
  3. Clone your new repo and open it in VS Code
  4. When prompted, click "Reopen in Container"
  5. Once the container is built, run the environment check then project setup:
    • Open Copilot Chat
    • Type: @workspace /environment-check — verify the environment is healthy
    • Type: @workspace /project-setup — configure your project identity, security baseline, license, and compliance

What's Included

Component Description
Dev Container .NET 10, Node 22, GitHub CLI, Azure CLI
MCP Servers Microsoft Learn, GitHub, Playwright
Spec Kit Spec-Driven Development — specifications, plans, and task decomposition
Squad AI development team — implementation orchestrator after planning
Skills TUnit testing, project conventions, spec-driven development, Blazor architecture, CSS design system, security (modular skill tree), RFC compliance, code analyzers
Prompts Environment check, project setup, compliance setup, pre-container setup, requirements interview, hire security architect
Code Quality StyleCop Analyzers, Roslyn Analyzers, .editorconfig, nullable reference types
Browser Automation Playwright CLI — agent-driven browser testing and automation

Development Workflow

This project uses Spec-Driven Development with Spec Kit and Squad:

  1. /speckit.constitution — Define project governance and principles
  2. /speckit.specify — Capture what to build and why
  3. /speckit.plan/speckit.tasks — Technical plan and task breakdown
  4. @squad — Implementation orchestration with specialist agents

For early-stage discovery, run /requirements-interview before specifying (optional).

Architecture

This template is designed for full-stack projects following Clean Architecture:

src/
├── Domain/           # Entities, value objects, domain events, interfaces
├── Application/      # Use cases, commands, queries, handlers, DTOs
├── Infrastructure/   # Database repos, external service clients, messaging
├── Api/              # ASP.NET Core Minimal API endpoints, DI composition root
├── Web/              # Blazor UI (Server, WASM, or Hybrid — decided per feature)
├── Web.Components/   # Reusable Razor Class Library (RCL) for shared UI components
├── Worker/           # Background processing with BackgroundService
└── Shared/           # Contracts, DTOs shared between projects

Blazor Hosting Models

The hosting model should be decided per feature (this is an ask-first trigger):

Model Use When
Blazor Server Server-only data, real-time updates, thin-client needed
Blazor WebAssembly Offline capability, zero-trust client, reduced server load
Blazor Hybrid Mix of both — feature-level decision

See the blazor-architecture and css-design-system skills for detailed patterns and guidance.

Development

# Build
dotnet build

# Test (TUnit on Microsoft Testing Platform)
dotnet test

# Run the API
dotnet run --project src/YourProject.Api/

# Run the Blazor app
dotnet run --project src/YourProject.Web/

Key Conventions

  • API Style: Minimal APIs with REPR pattern (one endpoint per file)
  • Error Handling: RFC 9457 Problem Details for all errors
  • Testing: TUnit on Microsoft Testing Platform (NOT xUnit/NUnit)
  • Pagination: Cursor-based for all list endpoints
  • Observability: OpenTelemetry (traces, metrics, logs)
  • Blazor: Hosting model per feature, RCL for reusable components, minimal JS interop
  • CSS: Design Tokens + CUBE CSS + Blazor CSS Isolation

See the project-conventions, tunit-testing, blazor-architecture, and css-design-system skills for detailed guidance.

Dependencies

  • Roslyn Analyzers — code quality and style analysis via Directory.Build.props
  • StyleCop Analyzers — formatting and structure rules via Directory.Build.props
  • TUnit — testing framework on Microsoft Testing Platform
  • Squad — AI development team, installed via DevContainer
  • Playwright CLI — browser automation for coding agents, installed via DevContainer

License

License is configured during first-time setup.


Composed from TheSereyn.Templates @ v0.5.0

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages