aims-global-ui

Define and enforce a unified UI design system for all A.I.M.S. screens.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BoomerAng9/Agent-ACHEEVY-009 --skill aims-global-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aims-global-ui
Source: https://github.com/BoomerAng9/Agent-ACHEEVY-009/tree/main/apps/AIMS/.claude/skills/aims-global-ui
Command: npx skills add https://github.com/BoomerAng9/Agent-ACHEEVY-009 --skill aims-global-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Global A.I.M.S. design system: layout, responsiveness, typography, and visual rules that all A.I.M.S. screens must follow, regardless of page type (landing, chat, CRM, command center, finance, workflows, tools).

Core Features & Use Cases

  • Establishes a cohesive visual language across all A.I.M.S. interfaces, ensuring consistency in layout, typography, and component behavior.
  • Enables faster frontend development by providing reusable design primitives and tokens that teams can adopt across pages like landing, chat, CRM, and analytics dashboards.
  • Use Case: When starting a new A.I.M.S. screen, apply the design system to match existing components, typography scales, and spacing rules for a unified user experience.

Quick Start

Apply the A.I.M.S. design system to the next frontend task by referencing aims-global-ui guidelines.

Frequently Asked Questions about aims-global-ui

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

FAQPage Schema
How do I enforce consistent typography and color tokens across multiple frontend interfaces?

You can enforce consistent typography and color tokens across frontend interfaces by applying a token-driven design system that defines reusable design primitives and governance rules for all page types. This ensures cohesive visual language and consistent component behavior.

What is a token-driven design system and when do I need it for CRM dashboards and chat interfaces?

A token-driven design system uses predefined variables for spacing, color, and typography to unify visual rules across interfaces. You need it when building CRM dashboards, chat interfaces, or command centers to maintain accessibility and layout consistency.

Can I use a single UI design system for both landing pages and complex command center workflows?

Yes, a unified global UI design system can be applied to both landing pages and complex command center workflows. It provides reusable design primitives and spacing rules that adapt across different page types while maintaining a cohesive user experience.

How do I apply design system guidelines to a new frontend screen to match existing accessibility rules?

To apply design system guidelines to a new frontend screen, reference the established UI guidelines for typography scales, color tokens, and accessible component usage. This ensures the new screen matches existing components and spacing rules perfectly.

Does a global UI design system support responsive layout requirements for analytics dashboards?

Yes, a global UI design system supports responsive layout requirements for analytics dashboards by defining responsiveness rules and reusable layout primitives. This enables faster frontend development while ensuring adaptive visual consistency across screen sizes.

Why does my frontend design system fail to maintain consistent spacing across different page types?

Your frontend design system likely fails to maintain consistent spacing due to lack of clear governance and token-driven rules. Establishing unified spacing tokens and visual rules ensures all page types, from chat to CRM, adhere to the same design primitives.