Actions
Local composite actions under .gitea/actions/ capture reusable orchestration steps, while the logic they orchestrate stays in the build system.
.gitea/actions/
3Trait
Lives beside the thing it describes or configures, not in a distant central location.
Local composite actions under .gitea/actions/ capture reusable orchestration steps, while the logic they orchestrate stays in the build system.
.gitea/actions/
3Machine-readable repository identity that tells catalog systems what a repository is and produces, and where the authoritative definitions live.
.descriptor/
2Architecture decision records are a last resort, written only when the repository’s structure, code, tests, and owner documentation cannot make a choice clear.
docs/pdlc/decisions/
2A single .linter/ directory holds the repository’s own lint configuration and overrides, layered over organisation defaults from the environment.
.linter/
2Conventions are described beside the thing that owns them — a directory’s layout in its own README, a command’s behaviour in its module or script.
<area>/README.md
4docs/pdlc/ holds the durable product context behind a repository — problems, constraints, tradeoffs, and decisions — and nothing short-lived.
docs/pdlc/
2Each fact is stated once, where it is maintained, and every other place that needs it points there instead of keeping a copy.
./
2make help is generated from ## comments on the targets themselves, so the list of commands cannot drift from the real ones.
scripts/build/
1Each child of www/ is a self-contained site root whose content, layouts, assets, and configuration travel together and whose output is disposable.
www/
3Repository tooling with stable command entry points and documented contracts — small applications that own a workflow, rather than glue around one.
tools/
2No specification matches every filter.