classey-screens

To maintain consistent UI patterns across frontend screens, you need a centralized blueprint that enforces layout rules, component usage, and navigation. This skill provides that single source of truth for all 17 Classey screens, ensuring cohesive design and scalable scaffolding across your project.

Frontmatter-driven discovery uses metadata at the top of page files to automatically identify and route screens. This skill implements it as a centralized mechanism for page scaffolding, allowing teams to rapidly build new routes while maintaining strict navigation consistency.

You can scaffold new application screens safely by referencing a centralized blueprint before building any page. This skill defines strict layout rules, wireframe behavior, and component lists for 17 screens, ensuring all new pages adhere to the existing design system.

No external dependencies are required to standardize your frontend navigation rules. This skill operates independently, using frontmatter-driven discovery and built-in safety checks to prevent unsafe scripts while enforcing cross-screen consistency.

It handles unsafe scripts by applying basic safety checks during the scaffolding process. This prevents unsafe scripts or prompts from being executed, ensuring that your frontend design system remains secure while you implement pages quickly.

The best way to manage layouts for educational screens like attendance and CGPA calculators is to use a standardized blueprint. This skill provides detailed page-specific rules and wireframe behavior for these exact screens, ensuring consistent implementation.