agilentics / boiler

Starting points that already made the decisions.

Each of these is lifted out of an application that is actually running in production, then cut back until only the parts worth copying are left. They are deliberately small. The value is in the conventions file, not in the line count.

The demo is webapp-skeleton itself, running — not a screenshot and not a fork. Everyone shares one account: demo@agilentics.com / demo-demo-demo. Change the password if you like; it is put back every hour.

How to use one

Copy the directory, drop the git history, and run the rename step in its README. There is no generator and no CLI: a template you can read in an afternoon beats one you have to trust.

How they stay honest

Boilerplate rots. When a fix in a child application turns out to be generic, it comes back here — that question is the only thing keeping these from being a snapshot of how things were done once.