Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
netresearch avatar

Typo3 Site Conformance

  • 3 installs
  • 1 repo stars
  • Updated August 3, 2026
  • netresearch/typo3-site-conformance-skill

Scores and hardens a deployable TYPO3 site/project repo against a gold standard covering structure, container topology, CI supply-chain gating, secrets, and deploy config.

About

Assesses a TYPO3 project repo (composer type:project plus Docker Compose) against seven rule families using a bundled Python checker that prints PASS/FAIL per rule. A developer uses it when reviewing or bootstrapping a deployable TYPO3 site's container, CI, supply-chain, and secret-handling conformance.

  • Bundled checker/check.py scores a repo against machine-readable rules.json
  • Seven rule families: STRUCT, CONTAINER, CI, DEPLOY, DEP, SEC, DOC

Typo3 Site Conformance by the numbers

  • 3 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #1,119 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/netresearch/typo3-site-conformance-skill --skill typo3-site-conformance

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs3
repo stars1
Last updatedAugust 3, 2026
Repositorynetresearch/typo3-site-conformance-skill

What it does

Scores and hardens a deployable TYPO3 site/project repo against a gold standard covering structure, container topology, CI supply-chain gating, secrets, and deploy config.

Files

SKILL.mdMarkdownGitHub ↗

TYPO3 Site / Project Conformance

Score and harden a deployable TYPO3 site distribution against the Netresearch gold standard. This is the site/project counterpart to typo3-conformance (which scopes to extensions).

When to use

  • A repo with composer.json "type": "project" and a root Compose file.
  • Reviewing container topology, Concourse CI, supply-chain gating, secret

handling, or TYPO3 site config (config/system, config/sites).

  • Bootstrapping a new customer site from the gold skeleton.

Extension repos (ext_emconf.php, Classes/, TER) → use `typo3-conformance`. Generic supply-chain hardening → `enterprise-readiness`; Docker/Compose → `docker-development`; Concourse → `concourse-ci`.

The ruleset lives here (this skill is the source of truth)

The canonical rule catalogue and the executable checker are bundled in this skill — it needs no external checkout to run:

  • Rules: checker/rules.json (machine-readable; generated by

checker/gen_rules.py).

  • Checker: checker/check.pypython3 checker/check.py <repo-path>

(only pyyaml required). Scores a target repo and prints PASS/FAIL per rule.

Downstream artifacts derive from this catalogue, they are not its source: typo3-14-gold is a runnable reference implementation that scores 100 %; typo3-project-standard is the human-readable companion narrative. Both are Netresearch-internal and optional — propose rule changes here.

The seven rule families

FamilyIntent
STRUCTTYPO3-native layout: config/ at composer-project root, no build/config, config/sites/*/config.yaml, committed composer.lock, .gitignore excludes vendor/var/public + live-env files
CONTAINERcompose.yaml (not docker-compose.yml); images pinned (third-party by @sha256 digest, first-party Netresearch-registry images by explicit version tag); no :latest/alpine:edge; healthchecks + deploy.resources.limits + restart on persistent services; no direct docker.sock mount
CIcomposer audit → Trivy gate → SBOM → cosign; CI task images pinned; fly download checksum-verified; secret detection; test gate; updates via MR
DEPLOYValkey (auth + eviction + no persistence); ofelia scheduler via socket-proxy; weekly restore-verification; logs to stdout/stderr
DEPdeclared PHP platform constraint; no dev-branch constraints; minimum-stability: stable; committed lock
SECno committed secrets (settings.php/additional.php secret-free, env-driven); no committed live-env files; no debug/host wildcards
DOCAGENTS.md + CLAUDE.md→symlink; README documents setup/env/make

Workflow

1. Gate. Confirm type: project + root Compose. Otherwise N/A (extension → typo3-conformance). 2. Score. Run python3 checker/check.py <repo>, or evaluate the families above. ERROR blocks; WARN should fix; INFO advisory. 3. Scope. Architecture/estate/runtime rules (three-repo split, uptime, php-fpm status, ci-colocation) are advisory — report, don't gate. 4. Fix → re-score. Keep repo-scope rules at 100 %.

See references/migration-from-reference.md for transforming a legacy support/typo3-NN/app-style repo (app/ wrapper, build/config, committed secrets, Redis, :latest) into a conformant one.

Related skills

DevOps & CI/CDdeployinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.