Generate an offline setup plan, require successful current bootstrap PR checks before applying settings, bind contexts to GitHub Actions, and validate readback. Preserve conflicting existing protections and stop instead of replacing them. Propagate the tested human-acknowledged review gate and locked JavaScript tooling to generated apps, including custom owner replacement and CodeQL coverage. Exclude node_modules and worktree metadata from template packages. Document owner bootstrap, least-privilege settings and the remaining live proof. Validation: 13 setup and four coverage Pester tests, seven review Node tests, PowerShell analysis, ESLint, workflow/security/documentation lint. npm verifies 83 signatures and 20 attestations. Actual packed CLI/no-CLI variants generate correct owners and reviewers and pass locked restores and zero-warning builds. Live repository provisioning requires authorized creation/push and hosted CI. Refs: KofTwentyTwo/AppKit#10, KofTwentyTwo/AppKit#13, KofTwentyTwo/AppKit#7, KofTwentyTwo/AppKit#9, KofTwentyTwo/AppKit#20 Co-Authored-By: Codex (GPT-6) <noreply@openai.com> Signed-off-by: James Maes <james@kof22.com>
6.0 KiB
The KofTwentyTwo Windows app template
This repository is a complete, working WinUI 3 app ("Kof22 App") and a dotnet new
template that turns it into a new app with your names. The starter provides the code and quality gates used by the KofTwentyTwo standards: the AppKit shell, a 100%-covered core, FlaUI UI tests, Kingsrook-style quality gates,
repository files, and the shared CI, security, and release workflows. It implements the
Windows desktop reference architecture.
This file is not copied into generated apps.
Create an app
# Install the template from a clone of this repository (or, once published, from NuGet)
dotnet new install .
# Generate
dotnet new k22-winapp -n Contoso.Notes --appId contoso-notes --displayName "Contoso Notes" `
--description "Quick notes that stay out of the way." -o Contoso.Notes
| Option | Default | What it sets |
|---|---|---|
-n, --name |
(required) | Solution, project, namespace, and executable names (Contoso.Notes.slnx, Contoso.Notes.Core, Contoso.Notes.exe), and the repository name in links |
--appId |
(required) | Machine id: data folder %LOCALAPPDATA%\<appId>, its override variable, log files, credential prefix, CLI executable, Velopack package id. Lowercase letters, digits, dashes. Never change it after the first release |
--displayName |
(required) | Product name in the title bar, splash, About, menus, and docs |
--description |
"A KofTwentyTwo Windows desktop application." | One sentence for the README, About, and main window |
--authorName |
James Maes | Copyright holder in license headers, LICENSE, and credits |
--owner |
KofTwentyTwo | GitHub owner in repository links, CODEOWNERS, and badges |
--cli |
true | Include the command-line head and its tests (--cli false to leave them out) |
The copyright year in license headers becomes the current year.
After generating
The generator omits dependency lock files. Before the first commit, run the README's
restore, build, test, coverage and format commands, then commit the resulting
packages.lock.json files. Install the included hooks with
pre-commit install --hook-type pre-commit --hook-type commit-msg after git init.
The generated PowerShell tooling gate uses PSScriptAnalyzer 1.25.0.
- Follow the preview/apply/validate setup runbook.
Create the GitHub repository (public, Product tier), push
main, and apply the repository standard's settings and rulesets, with these required checks:pr / title,pr / dco,pr / dependency-review,security / secrets,security / sca,security / workflows,codeql / analyze (csharp),codeql / analyze (actions),ci / build-test,ci / format,ci / ui-tests,scripts / powershell,scripts / javascript,codeql / analyze (javascript-typescript), andreview / automatedfor the single-maintainer policy. - Create the
releaseenvironment limited tov*tags, and list the repository in the standards repository inventory (K22-REPO-42; the conformance checker fails until it is listed). - Replace the brand mark:
dotnet run --project <AppKit>/tools/BrandTool -- --out src/<name>/Assets/Brand --start "#RRGGBB" --end "#RRGGBB" --glyph "<svg path data>". - Replace the example greeting feature with the app's real one; keep the shape (logic and view model in Core with tests, a thin view in the WinUI project).
- Update
docs/security/threat-model.mdfor the app's real attack surface, and runpwsh <standards>/tools/Test-RepoConformance.ps1 -Repository <owner>/<name> -LocalPath .. - Follow docs/RELEASING.md, including the pending steps.
Maintaining the template
The template is the app: change it like any app (topic branch, pull request, all gates), then check that it still generates cleanly:
dotnet new install . --force
dotnet new k22-winapp -n Smoke.App --appId smoke-app --displayName "Smoke App" -o ..\smoke
dotnet new k22-winapp -n Smoke.NoCli --appId smoke-nocli --displayName "Smoke NoCli" --cli false -o ..\smoke-nocli
dotnet new uninstall .
Placeholders the template replaces, so keep them exactly as written in the source:
Kof22App (the name), kof22-app (the app id), Kof22 App (the display name),
A KofTwentyTwo Windows desktop application. (the description), James Maes (the
author), KofTwentyTwo/windows-app-template (the owner and repository, which becomes <owner>/<name>) and @KofTwentyTwo (the owner), and 2026 after
Copyright (c) followed by a space (the year). Content that only applies with the command line is in
<!--#if (cli) --> blocks (Markdown, XML) or in the app workflow copies under .template.config/with-cli/ and .template.config/no-cli/.
templates/KofTwentyTwo.Templates.WindowsApp.csproj packs the template as a NuGet
package (dotnet pack templates/KofTwentyTwo.Templates.WindowsApp.csproj).
Publishing this template
This source repository publishes KofTwentyTwo.Templates.WindowsApp on protected
v* tags using the shared NuGet builder. Generated applications use separate
Velopack workflows with stable/dev channels. Source CI installs the packed template
and exercises both CLI variants, including build, format, coverage and UI tests.
Before the first publication, configure the protected repository and release
settings, register it in the standards inventory, and set NUGET_USER. The owner
must save a NuGet trusted-publishing policy for owner KofTwentyTwo, repository
windows-app-template, workflow release.yml, environment release, and package
KofTwentyTwo.Templates.WindowsApp. Publication is pending until these steps and
live CI/attestation verification are complete. Do not claim certification from
successful local tests.