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+).
TYPO3 Documentation Skill
Create and maintain TYPO3 extension documentation per docs.typo3.org standards.
Core Workflow
-
No
Documentation/yet? Run this, do not type the file out. The namespace is the part that comes out wrong when it is written from memory --guides.phpdoc.organdguides.typo3.orgare both addresses nobody serves -- and a file in the wrong namespace is well-formed XML that renders nothing:mkdir -p Documentation && cat > Documentation/guides.xml <<'XML' <?xml version="1.0" encoding="UTF-8"?> <guides xmlns="https://www.phpdoc.org/guides" links-are-relative="true"> <project title="TITLE" version="MAJOR.MINOR" release="MAJOR.MINOR.PATCH"/> </guides> XML grep -Fc 'xmlns="https://www.phpdoc.org/guides"' Documentation/guides.xmlSettings.cfgis the fileguides.xmlreplaced. Nothing reads it any more, so writing one leaves the extension with no rendered documentation and no error to show for it.The
grepprints1when the namespace is right and0when it is not. Then replace TITLE and both versions.<project>carries them as attributes; an element whose text is the extension key has no title and no release.assets/guides.xml.distholds the full file -- extension element, interlinks, build configuration -- and is the better starting point wherever the skill directory is reachable. -
Run extraction first to find gaps:
scripts/extract-all.sh /path/to/extension scripts/analyze-docs.sh /path/to/extension -
Consult the matching reference
-
Use TYPO3 directives, not plain text
-
Validate:
scripts/validate_docs.sh /path/to/extension -
Render:
scripts/render_docs.sh /path/to/extension
Critical: For "show docs", render HTML, not raw RST.
Element Selection Guide
| Content Type | Directive |
|---|---|
| Complete code | literalinclude (preferred) |
| Short snippets | code-block with :caption: |
| Config options | confval with :type:, :default: |
| PHP API | php:method:: -- :returntype: for nullable/union |
| Notices | note, tip, warning, important |
| Feature grids | card-grid with footer stretched-link |
| Alternatives | tabs (synchronized) |
| Screenshots | figure with :zoom: lightbox + border/shadow classes |
Critical Rules
Official docs are canonical; on conflict the live manual wins -- report
drift (references/canonical-sources.md).
Upstream:
- UTF-8, 4-space indent (no tabs), LF; wrap at 80 chars where possible
- CamelCase files, sentence case headings
- Permalink anchors (
.. _label:) before every heading - Index.rst in every subdirectory
- PNG/AVIF images with
:alt: - PHP domain: no
?Type/Type|nullinphp:method::; use:returntype:
NR policy: no mailto: (upstream allows it; spam/PII -- use
Issues/Discussions); .editorconfig in Documentation/.
Heuristic: ~250 lines per RST, split with toctree; screenshots where
they help (backend modules, config, workflows).
Code Example Validation
Cross-reference examples against source: grep method names in
Classes/, compare CLI arguments with configure().
See references/extraction-patterns.md.
Pre-Commit Checklist
- Code blocks have
:caption:, inline code uses proper roles - Screenshots exist with
:alt:and:zoom: lightbox scripts/validate_docs.shpasses, render has no warnings- README and Documentation/ synchronized
References
references/canonical-sources.md-- topic-to-upstream map, provenance labelsreferences/file-structure.md-- layout, namingreferences/guides-xml.md-- the guides.xml skeleton, build config, interlinksreferences/coding-guidelines.md-- CGL deltas, .editorconfigreferences/rst-syntax.md-- headings, punctuation pitfallsreferences/text-roles-inline-code.md--:php:,:guilabel:,:ref:references/code-structure-elements.md-- code blocks, confval, PHP domainreferences/typo3-directives.md-- confval, versionadded, deprecatedreferences/content-directives.md-- accordion, tabs, card-gridreferences/screenshots.md-- figures, image rules, SVG diagramsreferences/rendering.md-- Docker commands, live previewreferences/intercept-deployment.md-- webhook, build triggersreferences/asset-templates-guide.md-- templates, screenshot workflowreferences/architecture-decision-records.md-- ADR patternsreferences/documentation-coverage-analysis.md-- coverage scoringreferences/scripts-guide.md-- script optionsreferences/typo3-extension-architecture.md-- extension layoutreferences/upstream-docs-contribution.md-- upstream docs PRsreferences/render-guides-development.md-- changing the renderer itself: directive options, interlink parsing, integration-fixture semantics, Composer updates, commit and ADR conventions of TYPO3-Documentation repositories
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: 319k | 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: 197k | 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: 118k | 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 |