Starraider

Battle-tested TYPO3 Fluid template patterns for site package development. Use this skill when building or maintaining a TYPO3 v12+ site package — regardless of CSS framework. Covers the full template hierarchy (Layouts → Pages → Partials → Atoms), CMS-first content architecture with lib.dynamicContent, colPos propagation for sidebar-aware styling, responsive image handling, WCAG 2.1 AA accessibility patterns, and progressive-enhancement JavaScript. Complements the typo3-playwright-ddev and typo3-tailwind-migration skills.

Use when merging two TYPO3 site packages, side-packages, or theme extensions into one TYPO3-compliant site package, consolidating files, TypoScript, site sets, Fluid templates, TCA overrides, Composer metadata, assets, or version compatibility.

Use when securing TYPO3 frontend forms (typo3/cms-form), frontend user registration forms (evoweb/sf-register), or installing/configuring Google reCAPTCHA (evoweb/recaptcha) in TYPO3 projects.

Migrate a TYPO3 theme from legacy/custom CSS to Tailwind CSS v4 in a DDEV environment. Use this skill when a TYPO3 project needs to convert its existing CSS-based site package to Tailwind utility classes while maintaining 1:1 visual parity. Covers the complete workflow from visual regression baseline capture through build pipeline setup, design token mapping, Fluid template migration, content element conversion, accessibility auditing, and cross-browser verification. Critical emphasis on regression-test-first approach — always capture baselines before any migration work begins.

Use when upgrading TYPO3 11 to TYPO3 12, checking extension compatibility, Composer blockers, Rector/Fractor migrations, deprecations, platform requirements, or planning a major-version migration. Covers analysis, planning, and execution of TYPO3 11 to 12 upgrades in Composer-based projects.

Use when upgrading TYPO3 12 to TYPO3 13, checking extension compatibility, Composer blockers, Rector/Fractor migrations, deprecations, platform requirements, or planning a major-version migration. Covers analysis, planning, and execution of TYPO3 12 to 13 upgrades in Composer-based projects.

Use when upgrading TYPO3 13 to TYPO3 14, checking extension compatibility, Composer blockers, Rector/Fractor migrations, deprecations, or planning a major-version migration. Covers analysis, planning, and execution of TYPO3 13 to 14 upgrades in Composer-based projects.

Configure TYPO3 v14 XML sitemaps with EXT:seo, multi-language support, page sitemaps, custom record sitemaps, PageType route enhancer mapping, and speaking URL generation for record detail pages. Use when adding, fixing, or extending `/sitemap.xml`, `RecordsXmlSitemapDataProvider`, custom sitemap data providers, EXT:news sitemap setup, hreflang-aware record links, or sitemap route enhancer configuration in a TYPO3 v14 project.

Use when analyzing one webpage's primary topic, finding DataForSEO-backed keyword opportunities, or producing evidence-based search, Open Graph, and Twitter metadata in a Markdown report.

Use when creating or maintaining a persistent SEO keyword watchlist, discovering ranked domain keywords, checking Google positions across runs, comparing gains and losses, listing or removing tracked entries, or producing a ranking-change report.

Use when consolidating dated SEO reports for one domain into a concise full SEO report, prioritizing critical next actions, or surfacing cross-analysis ranking opportunities from files under SEO/<domain>/ with a current DataForSEO MCP validation snapshot.

Use when auditing one webpage for technical SEO, indexability, links, metadata, structured data, or desktop/mobile rendering and performance, then producing a prioritized report with DataForSEO-derived Technical Scores.

Use when performing SEO analysis with the DataForSEO MCP, selecting or sequencing DataForSEO tools, interpreting their responses, estimating request scope, troubleshooting calls, or explaining the MCP and underlying API contracts.

Use when detecting pages competing for the same keywords, selecting canonical target pages, deciding whether to merge, redirect, canonicalize, differentiate, or retain overlapping content, or recommending evidence-based internal links with DataForSEO MCP.

Use when detecting declining organic content, separating ranking decay from seasonality, prioritizing existing pages for refresh, or producing evidence-based content refresh briefs with DataForSEO MCP.

Use when estimating achievable incremental organic traffic from SEO improvements, forecasting ranking scenarios, or prioritizing keywords and pages by growth potential versus difficulty with DataForSEO MCP.