Ui architecture
UI component and frontend architecture — structure, states, separation of logic and presentation. Apply when building screens and web interface components.From its SKILL.md
npx -y skills add Neznakometz/StackForge --skill ui-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 213 tokens by cl100k_base, as published. Nobody here has run it
UI Architecture
- Logic separate from presentation. Business logic lives in hooks/stores/composables, not in JSX/templates. A component renders, it doesn't compute.
- States are mandatory. Every screen/component with data implements: loading (skeleton, not a bare spinner) · empty · error · success. A missing state is a review bug.
- Components are reusable and free of required side effects. Props are typed; no required props without defaults where avoidable.
- Accessibility from the start (see the
web-a11yskill), not an after-the-fact patch. - Design via tokens only (see the
design-systemskill): hardcoded hex/px is a review bug. - i18n from the start: strings via dictionaries, not hardcoded.
- Performance: don't ship needless code to the client; lazy boundaries, memoization where needed (not everywhere). Stack specifics (RSC, useMemo, Nuxt islands) come from the stack's knowledge pack.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.