hub-builder

Enforce Azure Builder Hub UI coding standards for components and design tokens.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/unthinkmedia/AzureBuilderHub --skill hub-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hub-builder
Source: https://github.com/unthinkmedia/AzureBuilderHub/tree/main/.github/skills/hub-builder
Command: npx skills add https://github.com/unthinkmedia/AzureBuilderHub --skill hub-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents common coding mistakes and ensures adherence to Azure Builder Hub's design system and coding standards, improving consistency and maintainability.

Core Features & Use Cases

  • Component Standardization: Enforces the use of pre-defined Storybook components over custom implementations.
  • Design Token Mandate: Prevents hardcoded values for colors, typography, spacing, and borders, ensuring consistency with the design system.
  • Accessibility Guardrails: Promotes the inclusion of necessary accessibility attributes for interactive elements.
  • File Structure Enforcement: Guides developers on correct placement and naming conventions for pages and components.

Quick Start

Use the hub-builder skill to ensure the new component adheres to all Azure Builder Hub coding standards.

Frequently Asked Questions about hub-builder

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

FAQPage Schema
How do I enforce Azure Builder Hub coding standards for UI components?

You can enforce Azure Builder Hub coding standards by applying this skill to guide component selection, design token application, consistency checks, file structure, and pre-commit self-audits, preventing hardcoded values and inconsistent token usage.

How do I prevent hardcoded values and ensure design token usage in my UI development?

To prevent hardcoded values and ensure design token usage in UI development, this skill mandates the application of pre-defined tokens for colors, typography, spacing, and borders, ensuring strict consistency with the Azure Builder Hub design system.

What is the best way to standardize custom UI implementations using Storybook?

The best way to standardize custom UI implementations using Storybook is to enforce the use of pre-defined Storybook components over custom builds, which improves consistency and maintainability across the Azure Builder Hub design system.

Can I use this skill to check accessibility attributes for interactive UI elements?

Yes, you can use this skill to check accessibility guardrails, as it actively promotes the inclusion of necessary accessibility attributes for interactive elements during the UI development process.

Does this skill guide file structure and naming conventions for pages and components?

Yes, this skill guides file structure enforcement by directing developers on the correct placement and naming conventions for pages and components within the Azure Builder Hub coding standards.

What are the limitations of relying on design tokens for UI component standardization?

The limitation of relying on design tokens for UI component standardization is that it requires strict adherence to pre-defined token structures for colors and typography, preventing custom hardcoded values that might be needed for edge cases outside the Azure Builder Hub design system.