What problem does it solve?
Building backend extensions in Webiny requires consistent architectural decisions across features, use cases, services, repositories, and DI registration. This Skill provides the central reference for structuring Webiny API code so features are discoverable, correctly scoped, and free of common anti-patterns.
Core Features & Use Cases
- Architecture Patterns: Defines the Extension → Feature → UseCase/Service/Repository hierarchy with clear scoping rules (transient vs singleton) and DI decision trees.
- Feature Templates: Provides naming conventions and directory structure templates for event handler features, service features, and complex multi-use-case features.
- Anti-Pattern Detection: Lists concrete mistakes to avoid, such as technical feature naming, generic errors, unfiltered event handlers, and process.env usage at runtime.
- Use Case: When adding a new backend capability like syncing CMS entries to an external translation service, use this Skill to decide whether to build a Service or UseCase, how to name the feature directory, and how to register everything in the DI container.
Quick Start
Use the webiny-api-architect skill to design a new API feature that creates and stores a custom entity with a GraphQL mutation.
