Guardrail·E-commerce

Shopware PHP Code

Apply Shopware PHP/server-side coding guidance. Use when editing PHP under src/Core, src/Administration, or src/Storefront — including…

You say
Buy it · $35 Read it before you buy $35 Written by shopware · unverified publisher
Context cost
2.2k tokensestimated from the bundle, loaded when it triggers
Bundle
2 files · 8.7 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Apply Shopware PHP/server-side coding guidance. Use when editing PHP under src/Core, src/Administration, or src/Storefront — including migrations, API schema, deprecations, or BC-sensitive code.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Guardrail

Constrains what the agent is allowed to do.

shopwarephpstorefrontconventions
Filed under

E-commerce

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md8.5 kB · 66 lines
--- name: shopware-php-code description: Apply Shopware PHP/server-side coding guidance. Use when editing PHP under src/Core, src/Administration, or src/Storefront — including migrations, API schema, deprecations, or BC-sensitive code. license: MIT ---
7# Shopware PHP Code
8
9Prefer the existing Shopware extension point over a new abstraction.
10
11## Structure
12
13- Keep application/domain services hexagonal: controllers, CLI commands, subscribers, and handlers translate infrastructure details (Request, IO, database, filesystem, HTTP) into plain inputs before calling services.
14- Services must not perform direct infrastructure work or depend on framework objects. Depend on narrow abstractions instead, such as repositories, filesystem interfaces, HTTP clients, or gateways.
15- Where code legitimately touches the local filesystem, inject and use the Symfony Filesystem component instead of raw PHP functions like mkdir, file_put_contents, copy, unlink, or rmdir. It throws IOException instead of warnings plus false returns, handles recursive operations, and keeps the dependency mockable.
16- Services must be unit-testable without external systems; test infrastructure adapters with integration tests.
17- Mark infrastructure adapters @internal by default.
18- Mark supported/public concrete classes as @final when they are not intended for extension.
19- Use a real final class for simple value objects/structs that do not need extension, decoration, or mocking; use @final for supported services where tests or framework mechanics may still need to subclass/mock them.
20- Do not add @final to classes already marked @internal; the internal marker is enough for implementation details.
21- Do not repeat @internal on constructors or methods inside an @internal class.
22- Prefer existing Shopware extension mechanisms over new provider interfaces when they already express the contract, for example Twig inheritance, DAL entities, Admin API routes, or explicit Twig blocks.
23- Be conservative with DTOs/value objects. Add one only when it expresses a meaningful domain concept, crosses a real boundary, or simplifies a public contract. Prefer scalars or arrays for simple internal data, and do not create DTOs solely to model private handoffs inside one class.
24- For transparent struct-style value objects, prefer public readonly properties over private properties plus trivial getters.
25- Name the arguments when a call passes several values that do not describe themselves — true, false, 0, 1, [], null — or when naming lets you skip defaults you only passed in order to reach a later argument. Leave a short, self-explaining call positional.
26
27## Public Surface
28
29- For new feature designs, explicitly separate the BC-promised public surface from internal implementation services. Document public REST/Admin/Store API contracts, DAL entities, template context, and supported extension points; mark controllers, subscribers, loaders, renderers, and discovery services @internal unless they are intended extension points.
30
31## API Schema
32
33- When adding core Admin API or Store API action routes, add the matching OpenAPI JSON schema under src/Core/Framework/Api/ApiDefinition/Generator/Schema/<AdminApi|StoreApi>/paths.
34- Run tests/integration/Core/Framework/ApiRoutesHaveASchemaTest.php for new or changed core API routes to catch missing paths, method mismatches, and stale schema entries.
35- The HTTP route contract can be public even when the PHP controller class is internal; document those separately.
36
37## Deprecations
38
39- Use a BC-change attribute from Shopware\Core\Framework\Deprecation\BCChange for a planned major-version change to supported API when there is no replacement to migrate to today. It is planning metadata, not a deprecation: keep the API usable until the announced version and do not use @deprecated reason:* markers.
40- Use the most specific attribute. CallSiteCompatibilityChange means calling the method can break (including parent:: calls from subclasses); ExtenderCompatibilityChange means an overriding declaration or inheritance relationship can break. Attributes that implement both affect both audiences.
41- Use @deprecated only when functionality is actually removed or has a replacement that external code must migrate to. Executable deprecated paths need Feature::triggerDeprecationOrThrow(); when an attribute's legacy usage is detectable at runtime (BecomesAbstract, NewRequiredParameter, ParameterRemoval, or ParameterTypeNarrowing), add the same conditional signal unless the method is framework-invoked.
42- Keep attribute values machine-readable: use a vX.Y.Z version, parameter names without $, ::class for class references, and the real default value for NewOptionalParameter.
43- Core code should never trigger self-deprecation notices. If core must keep calling deprecated behavior for BC, wrap that call with Feature::silent($majorFlag, static fn () => ...) so the deprecation notice is suppressed, the code path is explicitly tied to the major feature flag, and the branch will disappear when the flag is removed.
44- Do not mark DI service definitions as deprecated while Shopware core still references that service id anywhere. Internal DI references still trigger container deprecations and spam logs during warmup/compile. Deprecate the PHP API or class if needed, but only add the DI <deprecated> service tag once core no longer uses that service internally.
45- When adding an @deprecated annotation to executable PHP code, add a matching Feature::triggerDeprecationOrThrow() in the deprecated code path unless the deprecation uses an explicit exception reason supported by the PHPStan deprecation rule.
46- Do not leave new Shopware core code paths calling deprecated functionality. Move internal callers to the replacement API/service and keep legacy behavior only in focused BC tests.
47- For private implementation cleanup reminders, do not add method-level deprecations. Use a short inline // @deprecated tag:vX.Y.Z - ... comment near the branch or code that should be removed later, with enough detail to simplify the future cleanup.
48- When adding a temporary BC/deprecation branch for future feature-flagged behavior, guard it with the relevant Feature::isActive(...) check so the new path already exists, can be toggled, and the deprecated branch can be removed directly when the flag is removed.
49- If a deprecated API remains for BC, add or keep dedicated legacy tests that are easy to remove with the deprecation. Guard them for the relevant major feature flag when needed.
50- For any developer-facing deprecation or upcoming BC break, document both the currently available replacement and the future break/removal: use RELEASE_INFO-6.<minor>.md to explain the new replacement, why the old behavior/API is deprecated, and who is affected; use UPGRADE-6.<next-major>.md to explain what will break or be removed and the concrete migration steps.
51- If both REST/Admin/Store API contracts and PHP-level APIs or extension points are affected, document them as separate entries in the relevant sections, for example API for REST routes and Core for services, interfaces, abstract classes, decorators, or extension points.
52- In both release notes and upgrade guides, write from the perspective of extension authors, API consumers, operators, or other outside users. Include whether adjacent APIs remain unchanged when that distinction prevents migration mistakes.
53
54## Migrations
55
56- Use the exact current Unix timestamp for new migration class names, file names, and getCreationTimestamp() values. Do not use placeholder or rounded timestamps.
57- Do not add tests for empty/no-op updateDestructive() implementations; cover meaningful migration behavior in update() or destructive migrations that actually change state.
58
59## Detailed Guidelines
60
61- Read coding-guidelines/core/internal.md and coding-guidelines/core/final-and-internal.md when marking PHP API surface as internal, final, or supported for extension.
62- Read coding-guidelines/core/extendability.md and coding-guidelines/core/decorator-pattern.md when adding or changing extension points.
63- Read coding-guidelines/core/database-migations.md when adding or changing migrations.
64- Read coding-guidelines/core/feature-flags.md when adding feature-flagged behavior, deprecations, or BC branches.
65- Read coding-guidelines/core/6.5-new-php-language-features.md when reaching for a newer language feature, named arguments included.
66
In the file
SKILL.md1,157 words
Files2
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,115
on trigger
The instruction body and 1 supporting file, read only when the skill fires.
1.1%
of a 200k window
Ten skills this size would take about 11% of the window before you open a file.
050k100k150k200k context window

2.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

2 files, 8.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md8.5 kB
  • agents/openai.yaml0.2 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 2 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$35 once
Shopware PHP Code · MIT · shopware
one-time
Price$35 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$35
Referenceshopware/shopware-php-code

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

SH
shopware

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0