Files
t3bootstrap-skills/README.md
T
wappler af9368177b Initial t3bootstrap-skills plugin: three skills for T3Bootstrap on TYPO3 v14
- t3bootstrap-site-package: composer + site sets + when to add a local extension
- t3bootstrap-overrides: 4-layer override surface (Settings → SCSS → Fluid → DataProcessor)
- t3bootstrap-content-elements: 23 t3bs_* CE catalog + migration matrix (HTML/WP/Joomla/older TYPO3) + Flux-bs5 upgrade wizard

Mirrors the structure of wapplersystems/typo3-skills (.claude-plugin/{plugin.json,marketplace.json}, .agents/skills/<name>/{SKILL.md,agents/openai.yaml}).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-15 09:58:33 +02:00

76 lines
3.8 KiB
Markdown

# T3Bootstrap Skills
Agent Skills for working with the **T3Bootstrap** stack on TYPO3 v14 — the WapplerSystems
ecosystem of `t3bootstrap/*` and `wapplersystems/*` extensions that delivers a Bootstrap 5
based site template, content elements, and feature packages.
These skills teach an AI coding agent **what comes from the stack out of the box** and
**how to extend it minimally** so that a customer project stays close to the upstream
packages and remains upgrade-friendly.
> **Companion plugin:** [`wapplersystems/typo3-skills`](https://github.com/Starraider/typo3-skills)
> covers generic TYPO3 v14 topics (Fluid patterns, Extbase, Content Blocks, CSP, Playwright,
> …). The skills here are intentionally **T3Bootstrap-specific** and reference real
> `t3bootstrap/*` package paths.
## Repository Layout
```
.agents/skills/<skill-name>/
├── SKILL.md # Skill definition (description + workflow)
└── agents/openai.yaml # Standardized agent interface
```
## Available Skills
| Skill | Purpose |
| --- | --- |
| [t3bootstrap-site-package](./.agents/skills/t3bootstrap-site-package/SKILL.md) | Set up a TYPO3 v14 project on the T3Bootstrap stack: `composer.json` repositories, the right `t3bootstrap/*` + `wapplersystems/*` packages, site sets in `config/sites/<site>/config.yaml`, when (and when not) to add a local site package, language configuration, route enhancers. |
| [t3bootstrap-overrides](./.agents/skills/t3bootstrap-overrides/SKILL.md) | Minimal-invasive customization: Fluid template overrides via `templateRootPaths.10` / `partialRootPaths.10` / `layoutRootPaths.10`, SCSS variable overrides with `!default`, TypoScript constants, when to override what — without forking `t3bootstrap/template`. |
| [t3bootstrap-content-elements](./.agents/skills/t3bootstrap-content-elements/SKILL.md) | Catalog of the 23 `t3bs_*` content elements from `t3bootstrap/container-bs5-templates`, decision matrix for content migration (static HTML, WordPress, Joomla, older TYPO3, Flux-bs5), and the `t3bsContainerBs5MigrateFluxBs5` upgrade wizard. |
## How Skills Are Invoked
Skills are auto-discovered by Claude Code from the `skills:` entry in `.claude-plugin/plugin.json`.
Each skill's `SKILL.md` declares a description that triggers automatic invocation when the user's
request matches.
Explicit invocation: mention the skill by name in a prompt
(e.g. *"use the `t3bootstrap-content-elements` skill to map this WordPress accordion"*).
## Stack Versions This Plugin Targets
- TYPO3 **v14** (Composer mode)
- `t3bootstrap/template` `dev-release/v14`
- `t3bootstrap/core` `dev-release/v14`
- `t3bootstrap/container-bs5-templates` `dev-release/v14`
- Bootstrap **5**
- PHP **8.3+** (PHP 8.5 on the reference project)
- DDEV-based local dev
Skills assume TYPO3 v14. If a workflow differs on v13, the skill says so explicitly.
## Relation to the T3Bootstrap Page Builder
The reference project (`t3bootstrap14`) hosts a planned **Page Builder** inside
`t3bootstrap/core`. The skills here describe the **current** template-and-content-element
workflow. They will be revised as the builder lands and changes which configuration lives
where (Site Settings YAML vs. TypoScript constants).
## Contributing
PRs welcome at `git.wappler.systems:WapplerSystems/t3bootstrap-skills`.
Conventions:
- **Real package paths.** Skills reference real `t3bootstrap/*` / `wapplersystems/*` paths
rather than abstract placeholders — that *is* the topic. Customer site packages keep the
`my-site-package` / `Vendor\MySitePackage\` placeholders used in `typo3-skills`.
- **English content.** Frontmatter `description` and SKILL.md body in English. German
inline labels (e.g. backend field labels) are quoted verbatim from the upstream packages.
- **One SKILL.md per topic, deep but scannable.** Tables, file paths, code blocks. Avoid prose.
## License
[MIT](./LICENCE).