Shopware Ddev logo

Shopware Ddev

Community
alpham8
shopware-ddev

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.

Overview

Publisheralpham8
Repositoryagentic-webdev
Skill nameshopware-ddev
Stars
4
Forks
0
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by alpham8 on GitHub. Read the source before you install it.

Installation

Install the Shopware Ddev AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/alpham8/agentic-webdev/tree/master/skills/shopware-ddev
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/alpham8/agentic-webdev.git /tmp/agentic-webdev
mkdir -p .claude/skills
cp -r /tmp/agentic-webdev/skills/shopware-ddev .claude/skills/shopware-ddev
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Shopware Ddev in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Shopware Ddev on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Shopware Ddev is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Shopware 6 + DDEV Command Reference

Related skills: shopware (plugin architecture, DAL, events) · shopware-utils (sub-bundles, auto-resources) · ddev-development (DDEV config, PHP/Node/DB version changes, port setup, Dockerfile)

All commands run inside the DDEV container. Prefix with ddev exec or use ddev ssh for interactive use.

DDEV Basics

TaskCommand
Startddev start
Stopddev stop
Restartddev restart
SSH into containerddev ssh
Run single commandddev exec <cmd>
Open browserddev launch
Show URLs / statusddev describe
View logsddev logs
DB exportddev export-db --file=dump.sql.gz
DB importddev import-db --file=dump.sql.gz
Snapshotddev snapshot --name=before-update
Restore snapshotddev snapshot restore before-update

Plugin Management

bash
ddev exec bin/console plugin:refresh
ddev exec bin/console plugin:install --activate PluginName
ddev exec bin/console plugin:update PluginName        # also installs resources (custom fields, etc.)
ddev exec bin/console plugin:deactivate PluginName
ddev exec bin/console plugin:uninstall PluginName
ddev exec bin/console plugin:list

Theme & Storefront

bash
# Compile theme (SCSS → CSS, required after SCSS changes)
ddev exec bin/console theme:compile

# Assign theme to sales channel
ddev exec bin/console theme:change --all

# Dump theme variables
ddev exec bin/console theme:dump

# Build storefront assets (JS/CSS bundle)
ddev exec bin/build-storefront.sh

Administration

bash
# Dump plugin/bundle configuration (required before building)
ddev exec bin/console bundle:dump

# Build admin assets (required after JS/Twig changes in administration)
# Note: bin/build-administration.sh does NOT exist in SW 6.6+
ddev exec bash -c "cd /var/www/html/src/Administration/Resources/app/administration && PROJECT_ROOT=/var/www/html npm run build"

Pitfall: bin/build-administration.sh was removed in newer Shopware versions. Always use the npm run build approach above. Without bundle:dump first, the build fails with a paths[0] must be of type string error because the plugin map is missing.


Asset Watching (HMR / Dev Server)

The Shopware storefront watcher runs a webpack dev server inside the container. DDEV must expose the port so the browser can reach it.

1. Expose ports in .ddev/config.yaml

yaml
web_extra_exposed_ports:
  - name: storefront-watch
    container_port: 9998
    http_port: 9997
    https_port: 9998

Then apply: ddev restart

2. Start the watcher

bash
ddev exec bin/watch-storefront.sh

The watcher is now reachable at: https://<project>.ddev.site:9998

Shopware automatically injects the hot-reload script when APP_ENV=dev and the webpack dev server responds on port 9998.

Administration watcher

The admin watcher uses port 8080 by default:

yaml
# additional entry in web_extra_exposed_ports:
  - name: admin-watch
    container_port: 8080
    http_port: 8079
    https_port: 8080
bash
ddev exec bin/watch-administration.sh

Admin HMR URL: https://<project>.ddev.site:8080

Notes

  • Remove the #ddev-generated marker from .ddev/config.yaml before adding web_extra_exposed_ports, otherwise DDEV overwrites it on restart.
  • Both watchers require APP_ENV=dev in .env.local.
  • ddev describe shows all exposed ports after restart.

Cache

bash
ddev exec bin/console cache:clear
ddev exec bin/console cache:warmup
ddev exec bin/console cache:pool:clear cache.http          # HTTP cache only
ddev exec bin/console cache:pool:clear cache.object        # Object cache only

Database & Migrations

bash
# Run pending migrations
ddev exec bin/console database:migrate --all

# Create new migration for a plugin
ddev exec bin/console database:create-migration --plugin PluginName --name MigrationName

# Create new migration for an AdditionalBundle (dustin/shopware-utils)
ddev exec bin/console database:create-migration --bundle BundleName --name MigrationName

# Show migration status
ddev exec bin/console database:migrate-destructive --all   # run destructive migrations

Scheduled Tasks

bash
ddev exec bin/console scheduled-task:run          # run all due tasks once
ddev exec bin/console scheduled-task:list         # list tasks and their status
ddev exec bin/console messenger:consume           # process async message queue

Search & Indexing

bash
ddev exec bin/console es:index                    # reindex Elasticsearch
ddev exec bin/console dal:refresh:index           # refresh DAL search indexes

Import / Export

bash
ddev exec bin/console import:entity products      # Shopware native import
ddev exec bin/console export:entity products

User & Sales Channel

bash
# Create admin user
ddev exec bin/console user:create --admin --firstName="Max" --lastName="Muster" --email="max@example.com" --password="secret" admin

# List sales channels
ddev exec bin/console sales-channel:list

# Generate storefront URL
ddev exec bin/console sales-channel:update-domain localhost

Composer (inside container)

bash
ddev composer install
ddev composer require vendor/package
ddev composer update vendor/package
ddev composer dump-autoload

Debugging

bash
ddev exec bin/console debug:container              # list all services
ddev exec bin/console debug:router                 # list all routes
ddev exec bin/console debug:event-dispatcher       # list event listeners
ddev exec bin/console debug:config PluginName      # show plugin config
ddev logs                                          # web container logs
ddev logs -s db                                    # database logs
ddev exec php -i | grep memory_limit               # check PHP settings

Running PHPUnit Tests

When running unit tests inside DDEV, DATABASE_URL using localhost resolves to a Unix socket (which doesn't exist). Prefix tests with the TCP address:

bash
DATABASE_URL='mysql://db:db@db:3306/db' ddev exec vendor/bin/phpunit tests/unit/...

Full Reset (when things break)

bash
ddev exec bin/console cache:clear
ddev exec bin/console plugin:refresh
ddev exec bin/console plugin:update PluginName
ddev exec bin/console theme:compile
ddev restart

Frequently asked questions

What does the Shopware Ddev AI skill do?

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.

Why use Shopware Ddev on TypingMind?

Because you install it once and use it with any model. Shopware Ddev is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Shopware Ddev in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/alpham8/agentic-webdev/tree/master/skills/shopware-ddev. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Shopware Ddev?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Shopware Ddev?

As many as you like. As long as a model supports skills, you can use Shopware Ddev with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Shopware Ddev AI skill free?

It is published on GitHub by alpham8. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇