Skip to content

Method

Four years building applications in a company, since graduating my own products, in part AI-assisted. That is why six projects were finished in nine months, and it is also where fair questions come up. So this page does not say that I work carefully; it says where that can be checked.

The sequence

Eight steps, each with the file that backs it. The repository of this site is private and open on request.

  1. Discovery and requirements

    A conversation with the stakeholders before anything is built: what the project has to do, who works with it, what is fixed and what is negotiable. It ends with a scope both sides understand the same way.

    Backed byDECISIONS.md

  2. Mockup

    The interface is drafted before it is coded. An hour of mockup shows whether the requirement holds; the same insight after implementation costs days.

    Lives inEntrio-Repository, coach-dashboard-mockup.html

  3. Decision before code

    For everything structural, the context, the options considered, the choice and its consequence are written down before building. Later it is possible to say why something is the way it is, not only that it is.

    Backed byDECISIONS.md

  4. Rules and skills

    A project's conventions live in the project: folder layout, names, language, test strategy. Recurring procedures are written down, so the tenth run goes like the first.

    Lives inCLAUDE.md, dazu ~/.claude/skills

  5. Conventions from the installed version

    The tooling reads the versions that are actually installed and supplies the conventions for them. Otherwise the code follows a state older than the project itself.

    Backed by.mcp.json

  6. Implementation, AI-assisted

    The part that may be delegated. The result is checked against the decisions and rules before it, not against memory or habit.

    Backed bysrc/

  7. Check and commit

    Before every commit, formatting, static analysis and the project rules run over the changed files. The commit message explains the decision, not the lines.

    Backed by.husky/pre-commit

  8. Automated checks, then live

    On every change, static analysis, tests, the production build and checks in a real browser run through. One of the steps computes the contrast ratios from the colour tokens instead of estimating them. If one fails, nothing ships.

    Backed by.github/workflows/ci.yml

Built and operated end to end

From the architecture through payment processing to a signed Windows distribution, I built and operated every layer myself, with real payments since March 2026 and users who report bugs.