claude-webdev

Use when writing German marketing copy, product descriptions, feature announcements, landing page text, technical blog posts, case studies, or email campaigns. Triggers on requests for persuasive or audience-facing German content that needs to convert or inform non-developer readers.

Use when writing German sales copy, landing pages, service pages, booking pages, or any persuasive text aimed at non-technical readers who need to be guided from awareness to decision. Triggers on homepage copy, about pages, service descriptions, booking flows, or any text where the goal is trust-building and conversion.

Use when writing, reviewing, or optimizing blog posts, landing pages, meta tags, titles, descriptions, headings, URLs, or any user-facing web content for search engines. Triggers on SEO questions, content audits, structured data, Open Graph tags, schema markup, or on-page optimization. Also use for German-language SEO specifics (umlauts, hreflang, Flesch DE).

Use when creating a new Symfony project, scaffolding a Symfony application, or setting up the project skeleton - covers directory structure, bundles, services config, Vite/pentatrion, DDEV, PHPUnit, base template, i18n, CAPTCHA, and deployment.

Use when writing any German technical text — PR descriptions, README files, architecture docs, technical emails, bug reports, Slack messages, or documentation. Triggers on requests for technical writing in German or when the audience is developers, architects, or technical stakeholders.

Use when writing or reviewing tests for web pages, API responses, CLI output, or any user-facing output. Ensures tests verify actual content and structure, not just status codes or response types. Triggers on test files, test methods, assertResponseIsSuccessful, assertResponseStatusCodeSame, status code checks, HTTP response tests, controller tests, endpoint tests, integration tests, functional tests.

Use when writing PHP code - modern PHP 8 features, strict typing, enums, readonly, OOP patterns, PSR standards, security (file inclusion, SQL injection, XSS, CSRF, sessions, password hashing, file uploads). Triggers on .php files, composer.json, PHP classes, declare(strict_types=1).

Use when developing ASP.NET Core applications - Minimal APIs, dependency injection, middleware, Entity Framework Core, SignalR, authentication (JWT/Identity), configuration, health checks, caching, MassTransit, rate limiting. Triggers on .csproj, Program.cs, DbContext, MapGet/MapPost, IServiceCollection.

Use when writing C# code - modern C# 12/13 features, records, pattern matching, nullable reference types, LINQ, async/await, collections, generics, sealed classes, required properties, file-scoped namespaces. Triggers on .cs files, .csproj, C# classes, interfaces, records.

Use when working in a DDEV project - running commands, customizing containers, configuring nginx/PHP, installing PECL extensions, managing add-ons, or troubleshooting DDEV issues. Triggers on .ddev/ directory, ddev commands, container configuration, PHP extension installation, custom nginx/apache config, Docker build failures, web-build Dockerfile changes.

Use when running Shopware 6 console commands, building assets, managing plugins/themes, or working with the database in a DDEV environment. Quick reference for all important ddev and Shopware CLI commands.

Use when developing Shopware 5 or Shopware 6 plugins, working with the Enlight framework, DAL, event system, Twig/Smarty templates, Storefront JS, or Admin Vue components. Triggers on plugin development, entity definitions, event subscribers, template blocks, SW5 hooks, SW6 DAL queries.

Use when working with the dustin/shopware-utils library in Shopware 6 plugins — creating Plugin or AdditionalBundle classes, registering bundles, themes, migrations, configuration objects, or auto-installing resources (custom fields, document types, payment methods, mail templates).

Use when developing Svelte 5 components with TypeScript - both standalone mounting in Symfony/Twig and SvelteKit full-stack apps. Triggers on .svelte files, Svelte 5 runes ($state, $derived, $effect, $props), Vite Svelte plugin, SvelteKit routes/load functions.

Use when developing with the Symfony framework or any of its components - service container, forms, serializer, messenger, mailer, security, validator, routing, console commands, Twig, Doctrine integration. Triggers on Symfony bundles, DI configuration, kernel events, PHP attributes for routing/messenger/security.

Use when writing TypeScript code - type system, generics, utility types, type guards, discriminated unions, tsconfig, strict mode, DOM typing, async patterns, module patterns. Triggers on .ts files, tsconfig.json, type annotations, interfaces, generics.

Production-grade UI animation decisions: timing, easing, springs, transform-origin, interruptibility, stagger patterns, and perceived performance. Use when reviewing animations, building micro-interactions, or when UI 'feels sluggish/wrong'. Triggers on: animation review, motion design, dropdown/modal/toast animation, 'feels slow', 'animation wirkt falsch', micro-interactions, hover/active states.

Systematic workflow to audit and upgrade existing UIs from generic/AI-slop to premium quality. Scan current design, diagnose weak patterns, fix with targeted upgrades. Use when UI 'looks generic', 'feels like AI', 'needs polish', or for any redesign of existing interfaces. Triggers on: UI audit, redesign, 'sieht nach AI aus', 'wirkt generisch', 'Design verbessern', 'UI aufwerten', 'looks like a template'.

Use when developing Vue.js components - Vue 2 Options API, Vue 3 Composition API, script setup, reactivity (ref, reactive, computed, watch), props, emits, slots, provide/inject, lifecycle hooks, directives, TypeScript integration. Triggers on .vue files, Vue components, Shopware 6 Administration.

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.

Apply Gestalt principles of visual perception to UI design. Use when you need to: (1) group and organize UI elements effectively, (2) create intuitive visual relationships between components, (3) audit layouts for perceptual clarity, (4) design navigation, cards, forms, or dashboards that users understand instantly. Based on Gestalt psychology research applied to digital interfaces.

Optimize web performance through network protocols, resource loading, and browser rendering internals. Use when the user mentions "page load speed", "Core Web Vitals", "HTTP/2", "resource hints", "network latency", "render blocking", "TCP optimization", "service worker", or "critical rendering path". Also trigger when diagnosing slow page loads, optimizing time to first byte, choosing between WebSocket and SSE, or reducing bundle sizes. Covers TCP/TLS optimization, caching strategies, WebSocket/SSE, and protocol selection. For UI visual performance, see refactoring-ui. For font loading, see web-typography.

Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "engagement loops", "habit formation", "push notifications", "variable rewards", "daily active users", "habit zone", or "user retention loops". Also trigger when designing notification strategies, building streaks or progress systems, or analyzing why users stop using a product after initial signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.

Write accessible HTML that works with screenreaders and keyboard navigation. Use when you need to: (1) build forms with proper labels, fieldsets, and error messages, (2) structure pages with semantic landmarks and heading hierarchy, (3) add alt text, ARIA attributes, or skip links, (4) audit HTML for accessibility violations, (5) make interactive components keyboard-accessible. Triggers on: HTML templates, Twig files, Vue/Svelte templates, form elements, ARIA attributes, "accessible", "screenreader", "keyboard navigation", "a11y", "WCAG", "barrierefreiheit". Minimum viable accessibility for every project -- no excuses.

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users drop off", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", "user activation", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

Apply evidence-based UX laws to interaction design decisions. Use when you need to: (1) size and position interactive targets effectively, (2) reduce cognitive load and decision complexity, (3) design progress indicators, feedback timing, and memory-friendly interfaces, (4) resolve design trade-offs with psychological evidence. Based on Laws of UX by Jon Yablonski, synthesising research from psychology, cognitive science, and HCI.

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", or "pass-through method". Also trigger when reviewing interface designs for simplicity, evaluating whether an abstraction is pulling its weight, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.

Apply proven UI component patterns and scanning behaviour to build effective interfaces. Use when you need to: (1) design navigation, forms, buttons, cards, modals, or tables, (2) understand how users scan pages and place content accordingly, (3) choose between competing UI patterns (dropdown vs radio, modal vs inline, carousel vs static), (4) build loading states, notifications, and search interfaces. Complements gestalt-ui (visual grouping) and laws-of-ux (behavioural principles) with concrete component-level guidance.

Apply evidence-based UX and UI design principles when building user interfaces. Use when creating layouts, navigation, forms, buttons, dashboards, landing pages, or any user-facing component. Triggers on: "design a page", "build a form", "create navigation", "improve usability", "visual hierarchy", "user experience", "layout design", "whitespace", "spacing", "readability", "scanning pattern", "F-pattern", "Gestalt", "Fitts law", "Hick law", "cognitive load", "form validation", "button design", "color contrast", "typography". Complements frontend-design (aesthetics) with functional design theory. For pure visual aesthetics, see frontend-design. For browser performance, see high-perf-browser.