Personal engineering conventions and shared knowledge for repositories owned by
vhco-pro and michielvha. Keep the structure small and the guidance usable.
Agents read AGENTS.md. Humans and agents use these task routes:
| Task | Read |
|---|---|
| Change code or scripts | Coding |
| Write Go | Go |
| Write TypeScript | TypeScript |
| Build or change a React application | React and TypeScript |
| Research React behavior or review React performance | Use upstream React skills |
| Build a container | Containers and the shared Docker security profile |
| Change CI, dependencies, or releases | Delivery, managed dependency updates, shared delivery, and the Go release pilot |
| Bootstrap a new Go application | Bootstrap a Go project |
| Apply these conventions to an existing repo | Onboard a repository |
| Write or reorganize documentation | Documentation and humanize prose |
| Write a commit message, PR, issue or review summary | Humanize prose |
| Specify, plan or implement a feature | Feature documents and feature delivery |
| Ship a change | Feature delivery and delivery |
conventions/: how work is done across repositories.knowledge/: shared capabilities, their boundaries, and where to find them.guides/: concrete procedures.decisions/: durable choices affecting several repositories.
A component's implementation, inputs, and usage remain in that component's repository. Write a fact in one place and link to it elsewhere. Do not create empty categories, repository inventories, or a knowledge mapper.
Shared actions can remain under michielvha; the knowledge home is vhco-pro/docs.
Repository ownership does not decide where an agent looks for a component.
Use Node 24 or newer, run npm ci, then npm run check. The checker validates
local Markdown links, content frontmatter, and decision status. It does not
prove that external components behave as documented; inspect their selected refs.
Personal engineering conventions, shared delivery knowledge, and agent onboarding for vhco-pro and michielvha repositories