No description
  • Shell 34.3%
  • Python 22.6%
  • TypeScript 20.4%
  • Dockerfile 19%
  • Mako 1.6%
  • Other 2.1%
Find a file
Jochem de Boer b718c5f263 docs(proposals): add harbour-rewrite and mdis-frontend-components kickoff briefs
Two kickoff briefs intended to be opened in Claude Code sessions with access to the target codebase (Harbour, MDIS) to drive Epic-planning conversations against the ai-development-stack standard.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-13 14:01:10 +02:00
.devcontainer chore(devcontainer): surface tea login errors 2026-05-13 14:01:10 +02:00
docs Add Renovate Bot policy to enforce the standard's pinning tiers 2026-05-04 14:16:36 +00:00
proposals docs(proposals): add harbour-rewrite and mdis-frontend-components kickoff briefs 2026-05-13 14:01:10 +02:00
template Scaffold template/ for issue #14 (foundation) 2026-05-04 14:25:16 +00:00
.gitignore Add devcontainer setup, MCP config, and scaffold validation research 2026-05-02 12:08:35 +02:00
.mcp.json Add devcontainer setup, MCP config, and scaffold validation research 2026-05-02 12:08:35 +02:00
AGENTS.md first commit 2026-05-01 13:01:02 +02:00
README.md first commit 2026-05-01 13:01:02 +02:00
renovate.json Add Renovate Bot policy to enforce the standard's pinning tiers 2026-05-04 14:16:36 +00:00
validation_prompt.md Add devcontainer setup, MCP config, and scaffold validation research 2026-05-02 12:08:35 +02:00

AI Development Stack

An opinionated stack for software projects where coding agents (Claude Code, Cursor, Codex) do most of the implementation work. Includes the rationale, a full specification, and a working template.

What's in this repo

  • docs/standard.md — The case for the standard. The "why." Suitable for sharing with collaborators, customers, or anyone evaluating whether to adopt it.
  • docs/scaffold.md — The full specification. The "what" and "how": directory layout, configuration files, AGENTS.md content, recipes, and verification checklist.
  • template/ — The working scaffold the spec describes. New projects use this as a template.

How to use it

For a new project: copy or clone the template/ directory, run scripts/bootstrap.sh, pick a backend lane (Python by default), and start building.

For a deeper read: start with docs/standard.md for the rationale, then docs/scaffold.md for the implementation details.

Status

Initial commit captures the standard and the scaffold spec. The template/ directory will be populated incrementally against the verification checklist in docs/scaffold.md §13.

License

[Choose a license — MIT or similar recommended.]