From craft-workspace-webconsulting-skills
Assesses external ideas, launches, or articles for TYPO3 extension viability and companion German blog post. Builds GitHub-ready extensions and MDX drafts from verified sources.
npx claudepluginhub dirnbauer/webconsulting-skillsThis skill uses the workspace's default tool permissions.
> Source: https://github.com/dirnbauer/webconsulting-skills
Generates technical blog posts on codebase features, analyzing git history, implementations, and challenges with code snippets. Applies anti-AI writing guides for natural tone.
Writes SEO-optimized blog posts from PRs, git diffs, marketing briefs, codebase paths, or freeform technical descriptions.
Guides creating Content Elements, Record Types, Page Types, and File Types using TYPO3 Content Blocks extension—the single source of truth for YAML-based content modeling in TYPO3 14.x.
Share bugs, ideas, or general feedback.
Turn an external idea into a complete TYPO3 outcome: research, honest assessment, build, Git push, and German MDX publication draft.
Load adjacent skills when they materially improve the result:
grill-me: use this right after the initial source summary to interrogate what the user actually wants to transfer into TYPO3 and to resolve open product decisions one question at a timefirecrawl: fetching the source page, repo pages, and independent coveragetypo3-update: TYPO3 v14-first architecture and API choicestypo3-testing: unit tests and verification structurewebconsulting-create-documentation: help when shaping the MDX deliverableIf the idea is a hoax, April Fools post, abandoned repo, or obvious vaporware, say so immediately and pivot to alternatives.
Start the scoping conversation with grill-me style discipline:
Still keep the total question count lean. Ask at most 10 focused questions. Prefer a structured input tool if the client supports it; otherwise ask concise plain-text questions.
Good questions:
Do not ask questions whose answers are already obvious from the user request or local context.
Write a concise assessment before building. Cover these five areas:
| Area | What to cover |
|---|---|
| What TYPO3 already does better | Core features, mature extensions, existing APIs, reasons not to reinvent |
| What is genuinely new | Transferable ideas, UX patterns, workflow gains, technical differentiators |
| What is needed first | Dependencies, APIs, legal review, infrastructure, third-party services |
| Honest risks | Regulatory, adoption, maintenance, performance, ecosystem mismatch |
| Recommended architecture | TYPO3 mapping such as PSR-15 middleware, PSR-14 events, TCA, Extbase, CLI commands, site sets |
Present this as a short table or tightly written prose. Then stop and get explicit user confirmation before implementation.
Build a complete, push-ready TYPO3 extension when the concept passes review.
Use this structure unless the project clearly needs a smaller variant:
extension-name/
├── composer.json
├── README.md
├── LICENSE
├── .gitignore
├── Configuration/
│ ├── Services.yaml
│ ├── RequestMiddlewares.php
│ ├── TCA/Overrides/
│ ├── Capabilities.yaml
│ └── Sets/
├── src/
│ ├── Middleware/
│ ├── Service/
│ ├── Configuration/
│ ├── Event/
│ ├── Command/
│ └── Domain/Model/
├── Resources/Private/Language/
├── config/
├── ext_tables.sql
├── tests/Unit/
├── phpunit.xml.dist
└── phpstan.neon
declare(strict_types=1); everywhere.typo3-cms-extension.Webconsulting\{ExtensionName}\.Configuration/Services.yaml.$GLOBALS['TYPO3_DB'], hard dependencies on ext_emconf.php, and old signal-slot patterns.Configuration/Capabilities.yaml and keep it honest.Choose the lightest TYPO3-native shape that solves the problem:
#[AsCommand] for imports, sync jobs, and batch tasksIf the user wants the extension pushed:
main.Never leave tokens in shell history, committed files, examples, or config templates.
Create a publication-ready MDX post for webconsulting.at.
Nutzer:innenInclude:
datetitledescriptionauthor set to Kurt DirnbauerstatuscategorieslangAuf einen Blick with 4-6 bulletsFazit with a CTA to /kontaktUse components only where they clarify the article:
Tabs and TabDataTableComparisonTableCalloutAccordionTimelineTechResourceCalloutAlways include a TechResourceCallout pointing to the GitHub repository when one exists.
At the end:
| Signal | Action |
|---|---|
| Real idea, verified, good TYPO3 mapping | Build extension and blog post |
| Real idea, useful analysis, weak TYPO3 mapping | Write blog post only |
| Hoax, April Fools, or empty hype | Say so and suggest alternatives |
| Already solved well in TYPO3 | Point to the existing solution instead of rebuilding |
| Requires language/runtime changes TYPO3 cannot realistically absorb | Document concept only, no extension build |
Before delivering, verify:
Services.yaml wires the real servicesREADME.md explains install, config, usage, and architectureCapabilities.yaml exists and is honestAuf einen Blick, honest assessment, TechResourceCallout, and Timeline