Name: webiny-project-structure
Rating: 68.8 (1 reviews)
Author: webiny

webiny-project-structure

Webiny project layout, webiny.config.tsx anatomy, and extension registration. Use this skill when the developer asks about folder structure, where custom code goes, how to register extensions, what webiny.config.tsx does, or how the project is organized. Also use when they need to understand the relationship between extensions/, webiny.config.tsx, and the different extension types (Api, Admin, Infra, CLI).

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, executable content with strong tables and copy-paste-ready code, organized into clear sections with sensible cross-skill navigation. Its main weakness is the absence of a sequenced workflow with validation checkpoints for build-sensitive registration steps, and it could offload some reference detail to bundle files.

Suggestions

Add a short numbered workflow (e.g., 1. create extension file with `export default`, 2. register via JSX in webiny.config.tsx with full path + extension, 3. run build and validate it compiles) with an explicit validation/retry checkpoint for the build-failure rules already documented.

Move the Infrastructure Components and Extension Types tables (or detailed JSX reference) into a references/ file and link to it from SKILL.md to improve progressive disclosure and keep the overview leaner.

Trim the large inline webiny.config.tsx example to the minimal illustrative subset and reference a complete sample in a bundle file, reducing token cost while preserving actionability.

Dimension	Reasoning	Score
Conciseness	Mostly lean and token-efficient with well-targeted tables and code blocks; assumes Claude's competence and avoids explaining basic concepts, though the full webiny.config.tsx example and repeated JSX element tables add some length that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TSX code plus concrete commands (yarn webiny extension), tables mapping JSX elements to purposes, and explicit MUST rules with correct vs incorrect examples covering common cases.	5 / 5
Workflow Clarity	Content is organized by topic rather than as a sequenced workflow, and the build-affecting operations (registering extensions, BuildParam placement) include explicit failure warnings but no validate/retry feedback loop, so it sits at the listed-but-no-checkpoints anchor.	3 / 5
Progressive Disclosure	Well-structured overview with clear section headers and one-level-deep cross-skill links (Related Skills); however no bundle reference files exist, so all detail is inlined with minor organization gaps rather than split across files.	4 / 5
	Total	16 / 20 Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill covers and gives explicit, natural 'Use when...' trigger guidance with good keyword coverage. Minor room for enumerating more concrete actions, but distinctiveness and completeness are excellent.

Dimension	Reasoning	Score
Specificity	Names the domain (Webiny project layout, webiny.config.tsx anatomy, extension registration) with several concrete capabilities and specific extension types (Api, Admin, Infra, CLI), but stops short of enumerating many distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers 'what' (project layout, config anatomy, extension registration) and 'when' with concrete 'Use this skill when...' and 'Also use when...' trigger clauses covering multiple scenarios.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a developer would actually say — 'folder structure', 'where custom code goes', 'how to register extensions', 'what webiny.config.tsx does', 'how the project is organized' — including synonyms and concrete file/term references.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Webiny-specific niche keyed on webiny.config.tsx and extension types, with triggers unlikely to fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webiny/webiny-js
Path: skills/user-skills/project-structure/SKILL.md
Commit: d98a4e8

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.