uiux-context

Applies project-specific design overrides to UI/UX skill recommendations for Astro and Tailwind projects.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/po4yka/blog --skill uiux-context-po4yka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uiux-context
Source: https://github.com/po4yka/blog/tree/main/.agents/skills/uiux-context
Command: npx skills add https://github.com/po4yka/blog --skill uiux-context-po4yka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Generic UI/UX skill recommendations often conflict with an established project design system, suggesting wrong fonts, colors, or component patterns. This Skill defines project-specific overrides so design guidance stays consistent with the existing Astro + React + Tailwind codebase. ## Core Features & Use Cases - Stack Constraint Enforcement: Forces design searches to use the Astro stack instead of mobile or generic stacks. - Palette and Typography Locking: Preserves the neutral greyscale palette and the Geist Sans, Geist Mono, and Piazzolla font set against conflicting recommendations. - Component Adaptation: Redirects component suggestions toward the project's terminal workstation primitives like MacWindow, PanelShell, and Cmd. - Use Case: When a design skill suggests a colorful accent palette or SaaS-style cards, this override ensures the output respects the greyscale palette and terminal aesthetic defined in DESIGN.md. ## Quick Start Read this Skill before applying any ui-ux-pro-max, brand-system, slides, banner-design, or design-tokens recommendations to the project.

Frequently Asked Questions about uiux-context

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

FAQPage Schema
How do I apply project design overrides to UI/UX skill recommendations?

Read this Skill's SKILL.md before running any ui-ux-pro-max, brand-system, slides, banner-design, or design-tokens skill. Its override rules take precedence over conflicting skill output, keeping results aligned with the project design system.

What stack should I use for design searches in an Astro project?

Always use the --stack astro flag when running design search queries in this project. Do not use react-native or other mobile stacks, since the project is built with Astro, React 19, and Tailwind CSS 4.

Can I generate a new design system for a project that already has one?

No. When a project already defines its design system in files like DESIGN.md and theme.css, do not use --design-system generation. Use --domain searches only for supplementary guidance that respects the existing system.

Should skill color palette suggestions override an existing project palette?

No. Palette recommendations from design search tools are reference material only. The project's defined palette, such as a neutral greyscale scheme with emphasis tokens, always takes precedence over generated suggestions.

When do generic component recommendations not fit a project?

Generic cards, SaaS panels, or mobile components do not fit when a project uses custom primitives like MacWindow, PanelShell, or Cmd. Adapt any component recommendation to match the project's established aesthetic instead of applying it verbatim.