netresearch/typo3-docs-skill / skills/typo3-docs
typo3-docs
FlaggedUse when TYPO3 extension documentation has to render on docs.typo3.org, which builds a manual from Documentation/guides.xml and reads no Settings.cfg (a single README.rst serves an extension too small for one): when an extension has no documentation yet, or when creating, editing or reviewing Documentation/*.rst, guides.xml, README.md or XLF translations, rendering docs with Docker, TYPO3 RST directives, screenshots, or XLIFF 2-space indentation (TYPO3 v14+).
scripts/check-guides-xml-schema.sh
View on GitHub#!/usr/bin/env bash
# SPDX-License-Identifier: MIT
# SPDX-FileCopyrightText: Netresearch DTT GmbH
#
# Fail when Documentation/guides.xml will not render.
#
# Usage: ./check-guides-xml-schema.sh [project_root]
#
# Why this exists as its own check.
#
# `validate_docs.sh` used to test `[ -f Documentation/guides.xml ]` and print
# "guides.xml found (modern PHP-based rendering)". It never opened the file, so
# a file named guides.xml containing an invented schema was reported as fine —
# the validator actively reassured on the defect. Checkpoint TD-05 was
# `contains "<project"`, which a hallucinated `<project>my-ext</project>`
# satisfies.
#
# Measured, not assumed: across two recorded series of an agent evaluation
# against a real extension, agents produced SEVEN distinct fabricated
# namespaces and not one correct file. Three of them would have passed both
# gates above. See netresearch/typo3-docs-skill#91.
#
# What is asserted, and why exactly this:
#
# * the root element is in https://www.phpdoc.org/guides. Rendering is done
# by phpDocumentor Guides, so the document lives in phpDocumentor's
# namespace and not in a typo3.org one. Verified against every TYPO3
# project checked: georgringer/news, FriendsOfTYPO3/extension_builder,
# TYPO3-Documentation/TYPO3CMS-Reference-TCA, helhum/typo3-console.
# * <project> carries `title` and `release` as ATTRIBUTES. The renderer reads
# them from attributes; an element with the extension key as text is the
# shape agents reach for and is silently wrong.
#
# Deliberately not a schema validation: guides.xsd lives in the vendor tree and
# is absent before `composer install`, so a check that needed it would be
# skipped exactly where documentation is being created from nothing.
set -eu
PROJECT_ROOT="${1:-.}"
GUIDES="$PROJECT_ROOT/Documentation/guides.xml"
NS="https://www.phpdoc.org/guides"
if [ ! -f "$GUIDES" ]; then
echo "❌ $GUIDES does not exist"
echo " Copy assets/guides.xml.dist and fill the placeholders."
exit 1
fi
if ! command -v php >/dev/null 2>&1; then
echo "⚠️ php not found; cannot parse $GUIDES"
echo " This check needs php, which this skill requires anyway."
exit 2
fi
# PHP's error message goes to a private temporary file, not a fixed name in /tmp.
ERRORS_FILE="$(mktemp)"
trap 'rm -f "$ERRORS_FILE"' EXIT
# The PHP body is single-quoted on purpose: $argv, $doc and $root belong to
# PHP, and letting the shell expand them would substitute empty strings.
# shellcheck disable=SC2016
php -r '
$file = $argv[1];
$ns = $argv[2];
$doc = new DOMDocument();
if (!@$doc->load($file)) {
$e = libxml_get_last_error();
fwrite(STDERR, "not well-formed XML" . ($e ? ": " . trim($e->message) : "") . "\n");
exit(1);
}
$root = $doc->documentElement;
if ($root->namespaceURI !== $ns) {
fwrite(STDERR, sprintf(
"root element is in namespace %s, not %s\n",
$root->namespaceURI === null ? "(none)" : $root->namespaceURI,
$ns
));
exit(1);
}
$project = $doc->getElementsByTagNameNS($ns, "project")->item(0);
if ($project === null) {
fwrite(STDERR, "no <project> element\n");
exit(1);
}
$missing = [];
foreach (["title", "release"] as $attribute) {
if (trim($project->getAttribute($attribute)) === "") {
$missing[] = $attribute;
}
}
if ($missing !== []) {
fwrite(STDERR, sprintf(
"<project> has no %s attribute%s%s\n",
implode(" and no ", $missing),
count($missing) > 1 ? "s" : "",
trim($project->textContent) !== ""
? " (the extension key is in the element text; the renderer reads attributes)"
: ""
));
exit(1);
}
exit(0);
' "$GUIDES" "$NS" 2>"$ERRORS_FILE" || {
echo "❌ $GUIDES will not render: $(cat "$ERRORS_FILE")"
echo " Expected: <guides xmlns=\"$NS\"> with"
echo " <project title=\"…\" release=\"…\" version=\"…\" copyright=\"…\"/>"
echo " assets/guides.xml.dist is that file; copy it rather than writing one."
exit 1
}
echo "✅ guides.xml is in $NS with a <project> carrying title and release"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |