START THE FIRST PROJECT

Clone. Choose.
Generate locally.

The intended local workflow is visual-first: run Core Studio on your machine, compose the project in the browser, validate through the canonical Composer engine and generate into generated/<ProjectName>.

Open repository ↗Understand Composer

LOCAL REQUIREMENTS

Keep the setup boring.

Docker Desktop

Runs the local Workbench/Core Studio stack and SQL Server boundary.

.NET 10 SDK

Builds and opens the generated solution on the host machine.

PowerShell

Runs the repository launcher on Windows.

Git

Recommended for cloning and updating the reusable Core baseline.

1. Clone FoundationKit

git clone https://github.com/a2sn2/foundationkit-dotnet.git
cd foundationkit-dotnet

2. Start Core Studio

.\foundationkit.ps1 start -Target Workbench

The launcher brings up the local stack and opens the Workbench at http://localhost:8080. The Visual Composer is available at http://localhost:8080/compose.

3. Choose → Validate → Generate

Choose project settings

Project/profile, modules/resources, ID shapes and supported behaviors.

Build the manifest

The visual form writes the canonical Composer schema.

Validate

The same parser/analyzer used by CLI validation checks the model.

Generate Project

Output is created inside generated/<ProjectName>.

4. Open the generated solution

generated\MySystem\MySystem.sln

During local development the generated solution intentionally keeps project references to the local FoundationKit Core, so the generated product and reusable foundation can be exercised together.

Local generation is bounded

The browser does not receive arbitrary filesystem write access. Generation is constrained to the repository-owned generated/ workspace, while Core source is not exposed as an unrestricted writable area to the local UI.

Localhost-boundGenerated workspace onlyOwnership/hash safety