All projects

REPOSITORY STRUCTURE · AGENT WORK & QUALITY

Repo Blueprint

A shared structure for every repository.

Repo Blueprint is the foundation for organising code, documentation, agent instructions and quality checks. Use the same structure in a new or existing repository and keep it updated with rollouts that respect local changes.

Active project

Shared template · Node.js-based tools · Overlays for Node/TypeScript and .NET

Repo Blueprint: shared repository structure, agent instructions, quality gates and document metadata
BUILT WITH
  • Node.js 22+
  • JSON Schema
  • Git hooks
  • GitHub / Gitea CI
  • Node/TypeScript
  • .NET

FEATURES & USE CASES

What Repo Blueprint actually does.

Familiar structure

A base template brings Diátaxis documentation, project governance, tools and agent resources into consistent folders.

USE CASE

Move between repositories and find documentation and status in the same place.

Shared agent instructions

Canonical AGENTS.md files, roles and skills are generated in each client’s format. Instructions can be scoped by folder.

USE CASE

Let different coding agents follow the same project rules.

The same gates everywhere

A shared gate runner is used by Git hooks, CI, builds and releases. Overlays enable checks suited to the technology stack.

USE CASE

Run the same quality checks locally as before a release.

Documents as structured data

Front matter and schemas describe document types and metadata, providing a foundation for DocSaga sync and issue links.

USE CASE

Connect a project plan to its status and issues while keeping the readable Markdown file.

Adoption & updates

Preview rollouts with a dry run. New files are added and unchanged template files can be updated; local changes are not overwritten.

USE CASE

Adopt the same approach in an older project while keeping its customisations.

Technology profiles & security

Node/TypeScript and .NET overlays bring together analysis and tools. Security gates handle container scanning, NuGet and accepted risks with time limits.

USE CASE

Give different technology stacks a shared quality system with relevant checks.