Contact
Development

TYPO3 TypoScript Reference

Version-aware TypoScript, TSconfig and Fluid reference lookup with always-on best practices. Keyword search across cached documentation, 14 ready-to-use recipes, code review checklists, deprecation checks, migration guides, debugging reference. Supports TYPO3 v12, v13, and v14.

Latest release v1.6.4

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace 
    /plugin install typo3-typoscript-ref@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection 
    npx skills add https://github.com/netresearch/typo3-typoscript-ref-skill

    Requires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from skills.sh Installs skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route.

  3. composer require PHP project, as a package 
    composer require netresearch/typo3-typoscript-ref-skill

    Allow the Composer skill installer to activate and approve skill registration when prompted. Requires netresearch/composer-agent-skill-plugin Discovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup.

  4. composer skills:add PHP project, direct source 
    composer skills:add netresearch/typo3-typoscript-ref-skill

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by netresearch/composer-agent-skill-plugin Pins source repositories without a Packagist package and records them in composer.skills.lock. Runtime dependencies remain separate.

What you can do with it

  • Writing or editing TypoScript, TSconfig or Fluid templates in a TYPO3 project (v12, v13 or v14)
  • Reviewing TypoScript/Fluid changes for deprecations and anti-patterns
  • Migrating a TYPO3 site between major versions (v12 to v13, v13 to v14)
  • Debugging TypoScript errors such as "The page is not configured" or "No TypoScript template found"
  • Looking up cObjects, stdWrap functions, DataProcessors, conditions or ViewHelpers without guessing property names

What you get back

  • Reference excerpts from the official TYPO3 documentation for the detected TYPO3 version, prefixed with best-practice annotations (required/recommended/deprecated/tip)
  • Ready-to-use recipes (page setup, menus, Extbase plugins, Site Sets, ...)
  • Code review findings with deprecation tables, checklists and project lint rules
  • Migration guidance with before/after TypoScript snippets
  • Debugging hints mapping error messages to causes and fixes

What it expects in your project

  • gh CLI (authenticated with GitHub) for fetching the documentation cache
  • Python 3 (for rST conversion and JSON parsing)
  • Bash 4+
  • Network access on first run (scripts/lookup.sh --update); all lookups are served from the local cache afterwards
  • A composer.json or composer.lock in the project for automatic TYPO3 version detection from typo3/cms-core (without it, the lookup uses main, the development branch of the upstream documentation)

Tags

  • development
  • typo3