skills.rest
massCodeIO
massCodeIOOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ui-primitives

Enforce local Ui primitives and Shadcn patterns in massCode UI development.

6.9k|262|Updated Mar 29, 2022
Search Tags:#consistency#frontend#shadcn#ui-components#ui-primitives#masscode
One-click install
npx skills add https://github.com/massCodeIO/massCode --skill ui-primitives
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-primitives
Source: https://github.com/massCodeIO/massCode/tree/main/.agents/skills/ui-primitives
Command: npx skills add https://github.com/massCodeIO/massCode --skill ui-primitives

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes UI construction by enforcing the use of local Ui primitives and Shadcn patterns to avoid reinventing common controls across massCode features.

Core Features & Use Cases

  • Local Ui components are available via auto-import with a Ui prefix.
  • Do not re-implement basic controls; prefer existing Ui* variants.
  • If a required element does not exist, implement it under src/renderer/components/ui/ and reuse it in features.

Quick Start

Use the skill to codify and apply shared UI primitives across new features, ensuring consistent styling and behavior.

Frequently Asked Questions about ui-primitives

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize UI components to avoid reinventing basic controls across features?▼

Require existing Ui* primitives, auto-import conventions, and a shared styling approach. Set up local Ui components available via auto-import with a Ui prefix to ensure consistent styling and behavior across your application.

Where should I implement a new UI primitive if an existing variant does not exist?▼

Do not re-implement basic controls; prefer existing Ui* variants. If a required element does not exist, add it under src/renderer/components/ui/ and reuse it across features to maintain a cohesive interface.

What is the best way to maintain consistent styling and behavior when building new frontend interfaces?▼

The best way to maintain consistent styling is to codify and apply shared UI primitives across new features. This standardizes UI construction by enforcing local Ui components and Shadcn patterns during development and refactoring.

Does this UI standardization approach work without existing UI primitives in place?▼

No, this approach requires existing Ui* primitives and auto-import conventions to function. It standardizes UI construction by enforcing the use of these local components rather than reimplementing basic controls from scratch.

Related Skills

Explore More Design & Creative Skills→
redaantarredaantar
15

ui-conventions

Standardize React UI patterns and styling for the Ckourse desktop app.

Community
Intermediate
castlemilkcastlemilk
3

frontend-aesthetics

Create production-grade frontend interfaces with Next.js, Tailwind, and shadcn UI.

Community
Advanced
EsdevenimentsEsdeveniments
2

type-system-governance

Enforce TypeScript type definitions in the /types directory during development and code reviews.

Official
Basic
videojsvideojs
888

aria

Audit React UI components for ARIA accessibility and keyboard navigation.

Official
Basic