Name: webiny-full-stack-architect
Rating: 68 (1 reviews)
Author: webiny

webiny-full-stack-architect

Full-stack extension skeleton and registration pattern. Use this skill when creating an extension that spans both API and Admin — the top-level component with Api.Extension and Admin.Extension entry points, shared domain layer, BuildParam declarations, and package structure. References webiny-api-architect and webiny-admin-architect for layer-specific details.

Quality

81%

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.

A highly actionable architectural guide with concrete, copy-paste-ready patterns and a clear build sequence. Its main weakness is token efficiency — the Checklist, Quick Reference, and inline sections restate the same guidance, and some code examples are illustrative rather than essential.

Suggestions

Collapse the redundancy between the RULE section, Checklist, and Quick Reference into a single source of truth for the entry-point and BuildParam rules, referencing it rather than restating it.

Trim the full MyEntity class in the Shared Domain Layer to the minimal shape (interface + factory) needed to convey the pattern, or move it to a reference file.

Add an explicit verification checkpoint to the Checklist (e.g. "Run the build/extension registration and confirm both API and Admin entry points load without errors") so the workflow has a concrete validation step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the Checklist, Quick Reference, and inline sections repeat the same BuildParam and entry-point guidance, and the full MyEntity class example is illustrative padding that could be tightened.	3 / 5
Actionability	Copy-paste-ready code blocks cover the common cases — top-level MyExtension.tsx, BuildParam declaration/consumption, webiny.config.tsx wiring, shared entity — with explicit CORRECT/WRONG contrasts and concrete failure rules ("will cause a build failure").	5 / 5
Workflow Clarity	The 6-step Checklist gives a clear build sequence, and the RULE section's build-failure warnings act as implicit guardrails, but there is no explicit "verify the build passes" validation checkpoint.	4 / 5
Progressive Disclosure	Well-organized sections with clearly signaled, one-level-deep delegation to peer skills ("→ see webiny-api-architect skill"), but no bundle files exist and the single-file body carries some inline content (e.g. the full MyEntity example) that could be split or trimmed.	4 / 5
	Total	16 / 20 Passed

Description

87%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, well-scoped description that clearly states what the skill produces and when to use it, with a concrete trigger phrase and explicit deferral to sibling skills. Minor room to convert structural nouns into active verbs and broaden natural-language synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete elements — "top-level component with Api.Extension and Admin.Extension entry points, shared domain layer, BuildParam declarations, and package structure" — but these are structural components rather than verbs, so it sits just below the comprehensive-actions anchor at 5.	4 / 5
Completeness	Explicitly answers both what ("Full-stack extension skeleton and registration pattern" with concrete elements) and when ("Use this skill when creating an extension that spans both API and Admin") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	The natural trigger phrase "creating an extension that spans both API and Admin" plus "full-stack extension" give good keyword coverage, though it leans on internal webiny terms and misses a few common synonyms.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche — extensions spanning both sides — and explicitly defers layer-specific work to "webiny-api-architect and webiny-admin-architect," minimizing overlap with those peer skills.	5 / 5
	Total	18 / 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/full-stack-architect/SKILL.md
Commit: ef3b8bf

Reviewed: 1 day 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.