Determine monolithic or composition structure for UI components from spec requirements.
npx skills add https://github.com/aziontech/webkit --skill structure-decide
Please help me install this Agent Skill. Skill: structure-decide Source: https://github.com/aziontech/webkit/tree/main/.claude/skills/structure-decide Command: npx skills add https://github.com/aziontech/webkit --skill structure-decide
structure-decide removes guesswork when deciding whether a UI component should be monolithic or composition-based, ensuring consistent alignment with the shadcn-vue criterion.
structure: monolithic or structure: composition outcome based on reordering/omission needs.Use the structure-decide skill to analyze a component spec and output whether its structure should be monolithic or composition along with a one-sentence rationale tied to consumer reordering/omission needs.
High-intent search queries and answers about installing and using this skill.
Component architecture decisions rely on consumer reordering and omission requirements, evaluating whether a monolithic props and slots structure or a composition pattern better fits the spec. This approach aligns UI structure choices with shadcn-vue criteria.
Use composition over monolithic props when consumers need to reorder or omit sub-components within the UI structure. The structure-decide mechanism outputs a composition verdict specifically when these flexible reordering and omission needs are present in the component spec.
Spec validation checks the component's Purpose, Props, Slots, and Sub-components sections against shadcn-vue criteria. If required spec sections are missing, the validation blocks processing and returns a targeted missing-section message instead of a structure verdict.
Structuring a shadcn-vue component spec requires defining Purpose, Props, Slots, and Sub-components to evaluate monolithic versus composition patterns. Applying the structure decision during spec creation and re-checking it during component creation ensures spec validation consistency.
Yes, figma-discover JSON can optionally be provided to evaluate regions and determine whether a component design should use monolithic props and slots or a composition pattern based on consumer reordering and omission requirements.
Component structure validation returns a blocked message when required spec sections such as Purpose, Props, Slots, or Sub-components are missing. The system only emits a valid structure verdict and one-sentence rationale when all mandatory spec inputs are present.
openyakGenerate structured markdown developer handoff specs from Figma URLs or design descriptions.
aziontechGenerate canonical Storybook CSF3 story files for Azion Webkit Vue components.
zircoteValidate interface code against a strict 4px grid and depth strategy.
srivtxAnalyze codebase metrics with pygount for lines of code and language composition.