Skip to Content
Meubles Morinière

The project6 min read

Skills and evidence

The skills I claim in full-stack development, architecture, security, UX and quality. Each one has its evidence, read from the repository at build time: code, a test, a diagram or a decision.

Calling software “secure”, “tested” or “well architected” costs nothing. So for each skill, I show what you can check it with: the code that applies it, the test that proves it, the diagram generated from the source, the decision that explains it, and figures counted in the repository.

test suites run against a real Postgres database
111
apps/*/test/db/*.db.test.ts
regression tests, most of which read the source code and reject any departure from a rule
92
apps/*/test/*.regression.test.ts
hand-written CHECK constraints, re-read on the database after every applied migration
169
apps/erp/scripts/constants/db-invariants.ts#EXPECTED_CHECKS
tables, out of the 54 in the schema, the public storefront can write to
6
apps/site/scripts/lib/database-grants.ts#SITE_TABLE_GRANTS
code files still copied from one application to the other, a list that can only shrink
28
scripts/twins.manifest.json
architecture decisions recorded as ADRs
14
apps/docs/content/docs/(public)/architecture/decisions
Measured in the repository at each build of this documentation.

Metrics covers what the project measures (performance, Core Web Vitals, tests, reliability, maintainability), what it doesn’t measure yet, and the protocol to measure it.

AI as leverage, engineering as the standard. In My contribution and AI, I go through how I build with Claude Code and what I keep in hand (design, trade-offs, development, validation), with the records behind it.

What I claim, and what proves it

SkillClaimEvidence
Full-stackA rule written once serves both the storefront and the workshoprule in the shared package, a test that sweeps every day around public holidays
Customers pay what the page showed themserver-side reconciliation, tests for an already-displayed and a changed price
The last unit sells only onceconditional decrement, constraint, concurrency test on Postgres
What you change in the ERP shows up on the storefront right awayrevalidation route, per-content expiry
ArchitectureDependencies go in one directionESLint rule, import graphs generated at build time
Two applications born from a fork no longer drift aparttwin check at push time, figures from the manifest
The applications talk through a typed contractcontracts package, route test
Decisions are written down, with their trade-offsADRs
SecurityA storefront breach can’t mark an order as paidrestricted Postgres role, guard trigger, test run as the storefront role
Every storefront privilege maps to a query in its codetest that collects the storefront’s queries
The storefront refuses to start with the wrong rolestartup check
Every ERP server action opens with its guardtest that reads every action, and its own check
Messages between the applications are signed and timestampedHMAC-SHA256, replay window, constant-time comparison, rejection test
Changing a Stripe secret cuts nothing offdual verification and alert
The assistant can’t quietly pull a number out of thin airfigure check on every turn, test
UXAn ERP page never waits for its slowest querySuspense blocks, shared skeletons, a test of the fallbacks
A visible success gets no toast, and an action can be undoneshared callbacks, undo hook
A dropped connection, a conflict or an expired session loses nothingshared action hook
The storefront works with a keyboard and passes the WCAG rulesaxe rules, keyboard walkthroughs
QualityDatabase guarantees are proven on a real databaserejection tests on Postgres, no constraint without a test, invariants
If someone edits a payment, it showsSHA-256 hash chain in the database, verification
Tests read the code and reject any deviationcache rule, and a check of its patterns
Every commit pushed to main is checked before productionpre-push hook in a detached worktree

How to read these pages

Nobody copies an excerpt by hand. Each one is read from the repository when the docs are built. Its caption gives the file, the quoted element and its line numbers in the file. For an SQL definition, you see the latest one a migration created.

If a function, a test or an SQL definition disappears or gets renamed, the docs build breaks, and the error message says what’s missing. So a piece of evidence can’t stay online without the code it quotes. The build reruns as soon as a quoted file changes (apps/docs/scripts/ignore-build.sh).

The figures aren’t typed by hand either. Each metric says what it counts and where.

The repository is private, so the public evidence is the excerpts. If you have access to the repository, you can replay everything:

What can be replayedCommand
Both applications, with no copied codepnpm check:twins, from the root
The tests that read the ERP’s codepnpm exec vitest run test/ regression, from apps/erp
The ERP’s Postgres suiteDB_BEHAVIOUR_TESTS=1 pnpm test:db, from apps/erp, on a migrated local database
The guarantees of a migrated databasepnpm db:invariants, from the root, with DATABASE_URL set

What these pages don’t prove

The docs build checks that the quoted code and tests exist, but it doesn’t run them. What runs in the pre-push hook is the tests that read the code, the tests for the files a change touches and, when the change calls for it, the Postgres suite. The end-to-end tests are run by hand (Quality). Quality and delivery says what this gate doesn’t cover, and the Architecture decisions explain the accepted trade-offs.

On this page