git404hub

what is build-discipline fr?

rohansx/build-discipline — explained in plain English

Analysis updated 2026-05-18

3Audience · developerComplexity · 1/5LicenseSetup · easy

tl;dr

A single Markdown file of nine engineering principles you drop into an AI coding assistant so it builds reliable software instead of a fragile demo.

vibe map

mindmap
  root((repo))
    What it does
      Nine engineering principles
      Drop-in rules file
      Guides AI coding agents
    Tech stack
      Markdown
      Claude Agent Skills
      Cursor rules
    Use cases
      Claude Code skill
      Paste into CLAUDE.md
      Human PR checklist
    Audience
      Developers
      AI-assisted builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Install SKILL.md as a Claude Agent Skill so it triggers automatically during coding tasks.

VIBE 2

Paste the file into a CLAUDE.md or .cursorrules file to guide any AI coding agent.

VIBE 3

Use the nine principles as a personal checklist before starting a non-trivial build.

VIBE 4

Keep the file open while reviewing a pull request to catch fragile shortcuts.

what's the stack?

Markdown

how it stacks up fr

rohansx/build-discipline000madz000/payload-test-api-route-handler0marildo/imago
Stars333
LanguageTypeScriptPython
Setup difficultyeasyeasyeasy
Complexity1/52/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

in plain english

build-discipline is a single file you add to an AI coding assistant so that it builds software the way a careful senior engineer would, instead of producing a demo that looks fine at first but breaks under real use. The whole project is one Markdown file called SKILL.md, meant to be dropped into Claude Code, Cursor, or any other coding agent that can read a skills or rules file. The idea behind it is that AI models are already good at writing code that looks plausible, but they tend to skip the habits that make code reliable: measuring the numbers they would otherwise guess, keeping different kinds of state separate so nothing goes stale, checking correctness against invariants rather than just hoping the output looks right, and building things in small, checked stages instead of all at once. The author is clear that this file does not make a model smarter, it just gets the model to actually follow the same discipline a careful engineer would apply on their own. Inside SKILL.md are nine principles, each one tied to a real mistake the author made while building two different projects, a self improving knowledge system and a multi agent simulation. The principles cover things like separating source of truth data from data that can be recalculated, keeping a core piece of logic pure and reproducible so it can be tested, always calibrating constants from printed data rather than guesswork, preferring rules that combine cleanly over special cases, and designing for the worst case state so the system stays coherent even when something goes wrong. There are three ways to use it. You can install it as a Claude Agent Skill so it triggers automatically during coding tasks, paste or reference it inside another agent's rules file such as CLAUDE.md or .cursorrules, or simply read it yourself as a checklist before starting a non trivial build and keep it open while reviewing a pull request. The project has no code, dependencies, or setup beyond copying the file, and it is released under the MIT License.

prompts (copy fr)

prompt 1
Install SKILL.md from this repo as a Claude Agent Skill and apply it while we build this feature.
prompt 2
Paste the build-discipline principles into my CLAUDE.md file and follow them for the rest of this session.
prompt 3
Review my current code against the nine principles in build-discipline and flag anything that violates them.
prompt 4
Explain principle 3 about calibrating gating constants from printed data and show me how to apply it to my code.
prompt 5
Use build-discipline's isolate, stabilize, compose, tune, verify staging to plan how I should build this next feature.

Frequently asked questions

what is build-discipline fr?

A single Markdown file of nine engineering principles you drop into an AI coding assistant so it builds reliable software instead of a fragile demo.

What license does build-discipline use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is build-discipline to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is build-discipline for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.