senior-ui-systems-designer

Generates visual direction proposals for SaaS interfaces aligned with Tailwind v4 and design tokens.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill senior-ui-systems-designer-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-ui-systems-designer
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/senior-ui-systems-designer
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill senior-ui-systems-designer-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing new SaaS screens often results in generic, flat interfaces that lack hierarchy, density control, and systemic consistency. This Skill provides structured visual direction for operational B2B interfaces, producing comparable design proposals and verifiable acceptance criteria instead of ad-hoc styling decisions. ## Core Features & Use Cases - Visual Direction Proposals: Generates 2-3 distinct visual directions per interface, each with an aesthetic thesis, differentiating anchor, and execution risk, then recommends one with justification. - Screen-Type Heuristics: Applies specific composition and density rules for dashboards, tables, forms, detail views, settings, and empty/error states. - Systemic Specification: Translates the chosen direction into hierarchy, layout, typography, mandatory states (hover, focus, loading, empty, error), responsive behavior, and visual acceptance criteria. - Use Case: When building a new operations dashboard in a Next.js app, use this Skill to compare layout directions, define first-viewport hierarchy, and produce reviewable visual criteria before any implementation begins. ## Quick Start Ask the assistant to propose two or three visual directions for a new dashboard screen in apps/web, including hierarchy, density, states, and a justified recommendation.

Frequently Asked Questions about senior-ui-systems-designer

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

FAQPage Schema
How do I get visual design proposals for a new SaaS dashboard?

Describe the screen type and its operational context, and the Skill classifies the interface, reviews existing patterns, then proposes 2-3 visual directions with a justified recommendation. Each direction includes an aesthetic thesis, differentiating anchor, and execution risk.

What types of screens does this design skill cover?

It covers operational dashboards, tables and listings with filters, long forms and wizards, detail views, settings pages, operational onboarding, and empty, error, or permission states. Composition and density rules adapt to each category rather than using a fixed template.

Does this skill implement React or Next.js components?

No, it focuses on visual direction and specification, not implementation. For actual Next.js App Router implementation it defers to complementary skills like frontend-dev-guidelines and nextjs-app-router-patterns.

When should I not use a visual direction skill?

Avoid it for pure implementation tasks, Tailwind class cleanup, WCAG-only audits, or backend and API architecture decisions. It is meant for defining or reviewing the visual proposal of an interface, not for technical remediation.

How does the skill handle accessibility in UI design?

Accessibility is treated as a baseline, requiring WCAG 2.2 AA compliance from the start of every proposal rather than as a later remediation step. Mandatory states like focus, disabled, and error are specified for each interface.