stadium-builder 0.0.1-pre.47

Stadium Builder Bootstrapper

Stadium Builder is a framework for building full-stack applications with Claude Code. It contains project conventions and a spec-driven workflow for guiding the development process using Claude Code.

Requirements

• git
• .NET SDK 10.0
• Claude Code

Recommended tooling

• Visual Studio Code with the following extensions:
  • Claude Code for VS Code
  • C# Dev Kit
  • Cucumber (Gherkin) Full Support

Getting started

1. Install / update the stadium-builder .NET tool.

   Install

   From the Windows command prompt, run:

   dotnet tool install stadium-builder --global --prerelease
   

   Update

   From the Windows command prompt, run:

   dotnet tool update stadium-builder --global --prerelease
   

2. Change to the folder where you would like to start your new project and invoke the stadium-builder tool. The tool creates a new folder named <project-name> and scaffolds the project inside it.

   From the Windows command prompt, run:

   stadium-builder init <project-name>
   

3. Open the <project-name> folder in Visual Studio Code / Claude Code. Claude Code will pick up CLAUDE.md automatically.

4. Build features the BDD way. For every new feature or bug fix, ask Claude Code to implement it. It will:

   • Update the OpenAPI spec in the app-backend/docs folder (for REST API changes).
   • Write a failing Gherkin scenario.
   • Implement the minimum production code to make them pass.
   • Refactor, then ask you to confirm manual testing before committing.

   The exact sequence is specified in CLAUDE.md. No need to memorise it; Claude Code follows it for you.

Running the application

Once the application has been initialized using the stadium-builder init command, it can be run by either executing the Debug: Start Debugging command in Visual Studio Code (default key binding F5) or by running dotnet run --project app-backend/<ProjectName> in the command line. The C# project name <ProjectName> is the PascalCase form of the project name (for example, the project name my-app produces the C# project MyApp).

To run the tests, run dotnet test app-backend from the command line.

To build and run the application as a Docker container — locally with Docker Desktop or in a remote Docker environment — see the Docker guide.

Sample prompts

Below are a few examples of prompts for achieving specific tasks while developing.

Add a service

Add a REST service host.

Claude will generate the initial OpenAPI spec before writing tests and implementing the service.

Databases

Database setup

Database creation and versioning setup:

Have the app create a database called MyApp on the configured connection string if it doesn't yet exist. Install a mechanism whereby the application will apply update scripts as necessary to get the database schema to the current version.

Database MCP integration

Once a database has been created in the development environment, an MCP integration can be added so that Claude can easily connect to the database. This can be useful for adding sample data for manual testing.

Add an MCP integration for connecting to the database using the connection string in the app settings. The MCP server must be able to both read and write to the database.

Note: After adding an MCP integration, Claude Code needs to be restarted before it can use it. If you're working in Visual Studio Code, the Claude Code extension can be restarted by opening the Command Palette (Ctrl+Shift+P) and running the Developer: Restart Extension Host command.

Once an MCP integration has been added, the database can easily be populated with sample data using a prompt such as:

Add some users to the "user" table.