What problem does it solve?
Developers new to Webiny often struggle to understand where custom code belongs, how the project is organized, and how extensions connect to the framework. This Skill explains the flat project structure, the role of webiny.config.tsx, and how to register API, Admin, Infra, and CLI extensions correctly.
Core Features & Use Cases
- Project Layout Guidance: Describes the single-package structure with extensions/, public/, and webiny.config.tsx as the central configuration file.
- Extension Registration: Documents JSX-based registration via <Api.Extension>, <Admin.Extension>, <Infra.*>, and <Cli.Command> components, including required file extensions and default export rules.
- Environment-Conditional Config: Shows how to use <Infra.Env.Is> and build parameters to vary configuration per deployment environment.
- Use Case: A developer wants to add a custom GraphQL content model and an Admin UI column. This Skill tells them to place files under extensions/ and register them with <Api.Extension> and <Admin.Extension> in webiny.config.tsx.
Quick Start
Ask the AI to explain where custom code goes in a Webiny project and how to register a new API extension in webiny.config.tsx.