classey-screens

Create a centralized blueprint for consistent Classey screen layouts and navigation.

Updated Apr 9, 2026

Search Tags:#frontend #scaffolding #navigation #design-system #screens #ui-patterns #classey

Ready to run

npx skills add https://github.com/melvinv007/classey_personal_tracker --skill classey-screens

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: classey-screens
Source: https://github.com/melvinv007/classey_personal_tracker/tree/main/.github/skills/classey-screens
Command: npx skills add https://github.com/melvinv007/classey_personal_tracker --skill classey-screens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classey screens and pages are scattered across projects, causing inconsistency and slow delivery. This skill standardizes the design, layout rules, and component usage for all 17 screens, enabling teams to implement pages quickly with a cohesive experience.

Core Features & Use Cases

Detailed layout rules, component lists, wireframe behavior, and page-specific rules for all 17 screens.
Centralized frontmatter-driven discovery and a single source of truth for page scaffolding, routing, and navigation.
Real-world use: rapidly scaffold new pages or routes for any screen while maintaining global consistency.

Quick Start

Start by referencing this skill before building any page, route, or layout in Classey and implement each screen strictly according to the defined patterns.

Frequently Asked Questions about classey-screens

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

FAQPage Schema

How do I maintain consistent UI patterns across multiple frontend 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.

What is frontmatter-driven discovery for page scaffolding?▼

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.

How do I scaffold new application screens without breaking the design system?▼

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.

Do I need any external dependencies to standardize my frontend navigation rules?▼

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.

How does this approach handle unsafe scripts during page implementation?▼

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.

What's the best way to manage layouts for educational screens like attendance and CGPA calculators?▼

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.