WCAG 2.1 AA accessibility patterns for TYPO3 v13/v14 LTS sitepackage frontend development, distributed as a Claude Code skill.
typo3-a11y-skill/
├── skills/typo3-a11y/ # Skill definition and references
│ └── SKILL.md # Skill metadata, trigger description, inline guidance
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (name, version, license)
├── .github/workflows/ # CI caller workflows (all call netresearch/skill-repo-skill reusable workflows)
├── composer.json # Composer package definition (type: ai-agent-skill)
├── LICENSE-MIT # MIT license (applies to code, configs, CI workflows)
├── LICENSE-CC-BY-SA-4.0 # CC-BY-SA-4.0 (applies to skill content, docs, references)
└── README.md # Human-facing documentation
No Makefile. Key operations:
- Install PHP dependencies:
composer install - Validate skill repo structure: run
skill-repo-skill'svalidate-skill.shagainst repo root - Release: bump
.claude-plugin/plugin.jsonversion, open PR, merge, signed tagvX.Y.Z, push tag — therelease.ymlcaller builds the GitHub release
- Skill behavior is defined by skills/typo3-a11y/SKILL.md — its
descriptionfield must begin withUse whento activate correctly in Claude Code. - Licensing follows the Netresearch split model: code under LICENSE-MIT, documentation and skill content under LICENSE-CC-BY-SA-4.0. SPDX expression:
(MIT AND CC-BY-SA-4.0). - Do not add a
versionfield to composer.json — versions are derived from git tags by the Release workflow. - All CI workflows in .github/workflows/ must remain thin callers of
netresearch/skill-repo-skillreusable workflows — never inline actions in this repo. - Release discipline: tag only after the bump PR is merged to
main; tag-before-bump runs the release against the wrong version and produces a locked broken release. - Conformance with the
skill-repo-skillstructural standard is enforced by thevalidate.ymlcaller on every PR.
- README.md — human-facing documentation
- skills/typo3-a11y/SKILL.md — skill content and triggers
netresearch/skill-repo-skill(external) — source of truth for reusable CI workflows and structural conventions