typo3-docs
Use when creating, editing, or reviewing TYPO3 extension documentation (Documentation/*.rst, guides.xml, README.md, XLF translations), rendering docs with Docker, using TYPO3 RST directives, adding screenshots, deploying to docs.typo3.org, improve docs, fix documentation, or XLIFF 2-space indentation (TYPO3 v14+).
What this skill does
# TYPO3 Documentation Skill Create and maintain TYPO3 extension documentation following official docs.typo3.org standards. ## Core Workflow 1. **Run extraction first** to identify documentation gaps: ```bash scripts/extract-all.sh /path/to/extension scripts/analyze-docs.sh /path/to/extension ``` 2. Consult the appropriate reference file for the task 3. Use TYPO3-specific directives, not plain text 4. Validate: `scripts/validate_docs.sh /path/to/extension` 5. Render: `scripts/render_docs.sh /path/to/extension` > **Critical**: When the user asks to "show docs", render and display HTML output, not raw RST. ## Element Selection Guide | Content Type | Directive | |--------------|-----------| | Complete code | `literalinclude` (preferred over `code-block`) | | Short snippets | `code-block` with `:caption:` | | Config options | `confval` with `:name:`, `:type:`, `:default:` | | PHP API | `php:method::` -- use `:returntype:` for nullable/union types | | Notices | `note`, `tip`, `warning`, `important` | | Feature grids | `card-grid` with `stretched-link` in footer | | Alternatives | `tabs` (synchronized) | | Screenshots | `figure` with `:zoom: lightbox` `:class: with-border with-shadow` | ## Critical Rules - **UTF-8**, **4-space** indent, **80 char** lines, **LF** - **CamelCase** files, **sentence case** headings - **Permalink anchors** (`.. _label:`) before every heading - **Index.rst** in every subdirectory - **PNG** screenshots with `:alt:` and `:zoom: lightbox` - **.editorconfig** in `Documentation/` - **Screenshots MANDATORY** for backend modules, config, workflows - **Max 250 lines** per RST -- split with `toctree` - **No `mailto:`** -- use GitHub Issues/Discussions - **PHP domain**: no `?Type`/`Type|null` in `php:method::`; use `:returntype:` ## Code Example Validation Cross-reference code examples against extension source: grep method names in `Classes/`, compare CLI arguments against `configure()`, verify API signatures match. See `references/extraction-patterns.md`. ## Pre-Commit Checklist 1. `.editorconfig` in `Documentation/`, `Index.rst` in every directory 2. 4-space indent, no tabs, max 80 chars 3. Code blocks have `:caption:`, inline code uses proper roles 4. Screenshots exist with `:alt:` and `:zoom: lightbox` 5. `scripts/validate_docs.sh` passes, render has no warnings 6. README and Documentation/ are synchronized ## References - `references/file-structure.md` -- directory layout, naming conventions - `references/guides-xml.md` -- build configuration, interlink settings - `references/coding-guidelines.md` -- .editorconfig, indentation rules - `references/rst-syntax.md` -- headings, lists, tables, formatting - `references/text-roles-inline-code.md` -- `:php:`, `:file:`, `:guilabel:`, `:ref:` - `references/code-structure-elements.md` -- code blocks, confval, PHP domain - `references/typo3-directives.md` -- confval, versionadded, deprecated - `references/content-directives.md` -- accordion, tabs, card-grid - `references/screenshots.md` -- image requirements, figure directives - `references/rendering.md` -- Docker commands, live preview - `references/intercept-deployment.md` -- webhook, build triggers - `references/asset-templates-guide.md` -- templates, screenshot workflow - `references/architecture-decision-records.md` -- ADR patterns - `references/documentation-coverage-analysis.md` -- coverage scoring - `references/scripts-guide.md` -- script options - `references/typo3-extension-architecture.md` -- extension layout --- ## Credits & Attribution This skill is based on the excellent work by **[Netresearch DTT GmbH](https://www.netresearch.de/)**. Original repository: https://github.com/netresearch/typo3-docs-skill **Copyright (c) Netresearch DTT GmbH** — Methodology and best practices (MIT / CC-BY-SA-4.0) Special thanks to [Netresearch DTT GmbH](https://www.netresearch.de/) for their generous open-source contributions to the TYPO3 community, which helped shape this skill collection. Adapted by webconsulting.at for this skill collection
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.