ui-architecture

Enforce Material Design 3 and MVVM patterns for RotatingartLauncher UI changes.

186|11|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/FireworkSky/RotatingartLauncher --skill ui-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-architecture
Source: https://github.com/FireworkSky/RotatingartLauncher/tree/main/.agents/skills/ui-architecture
Command: npx skills add https://github.com/FireworkSky/RotatingartLauncher --skill ui-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all UI changes in the RotatingartLauncher project adhere to established architectural patterns, design guidelines, and platform constraints, preventing inconsistencies and technical debt.

Core Features & Use Cases

  • Architectural Alignment: Guides developers to follow the project's specific MVVM, routing, and landscape-first design principles.
  • Design System Consistency: Promotes the use of Material Design 3 tokens and custom glass components for a unified look and feel.
  • Use Case: When a new feature requires a settings screen, this Skill provides the blueprint for how to implement its UI, state management, and navigation within the existing project structure, ensuring it looks and behaves like other parts of the launcher.

Quick Start

Review the provided UI implementation notes and ensure any proposed changes align with the project's landscape-first design and MVVM patterns.

Frequently Asked Questions about ui-architecture

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

FAQPage Schema
How do I implement a settings screen using MVVM and Compose for an Android launcher?

When adding UI features, follow landscape-first design, custom NavState/Screen routing, and MVVM state-event-effect patterns using Material Design 3 and custom glass components to prevent technical debt and ensure architectural consistency.

How do I enforce Material Design 3 consistency across shared Android modules?

Enforce Material Design 3 consistency by utilizing Material Design 3 tokens and custom glass components across app and shared modules, ensuring all UI changes adhere to the established design guidelines and architectural patterns.

What is the best way to structure Android UI navigation with custom routing in Compose?

The best way to structure Compose UI navigation is using custom NavState/Screen routing combined with MVVM state-event-effect patterns, aligning UI with app conventions and landscape-first design principles.

Why does my Android UI architecture accumulate technical debt when adding new features?

UI architecture accumulates technical debt when new features fail to adhere to established MVVM patterns, landscape-first design constraints, and Material Design 3 token usage, causing structural inconsistencies across shared modules.

Do I need landscape-first design constraints for all UI changes in an Android launcher?

Yes, landscape-first design constraints are required for all UI changes, ensuring that new features like settings screens look and behave consistently within the existing RotatingartLauncher project structure and conventions.