ss-build

Build UI screens using StyleSeed rules with a lock-build-score-fix workflow.

22|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/izzoa/polyrouter --skill ss-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-build
Source: https://github.com/izzoa/polyrouter/tree/main/.agents/skills/ss-build
Command: npx skills add https://github.com/izzoa/polyrouter --skill ss-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents generic, first-draft UI work by forcing a complete StyleSeed workflow: lock the visual direction first, build against the full rules, then score and fix issues before presenting the result.

Core Features & Use Cases

  • Design lock first: Creates or reuses a STYLESEED.md file so the surface, mood, accent, font, and motion are decided before any UI code is written.
  • Rule-driven build: Instructs the model to read the full design rules and apply focal point, type scale, accent consistency, and visual craft constraints while building.
  • Quality gate loop: Runs a score-and-fix cycle until the result reaches the minimum acceptable threshold, reducing drift, polish gaps, and default-looking outputs.
  • Use case: A designer or engineer asks for a marketing page, dashboard, or app screen and wants the output to feel intentionally art-directed instead of machine-generated.

Quick Start

Use the ss-build skill to build a polished inventory dashboard and follow the full lock-build-score-fix loop before showing the result.

Frequently Asked Questions about ss-build

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

FAQPage Schema
How do I prevent generic, machine-generated UI design when building app screens?

To prevent generic UI design, enforce a controlled workflow that locks visual direction first, applies rule-based constraints during the build, and runs a quality gate before delivery. This ensures intentional art direction and visual consistency across product surfaces.

What is a design lock and why is it needed before building a dashboard?

A design lock establishes surface, mood, accent, font, and motion decisions in a configuration file before any UI code is written. It is needed to prevent visual drift and ensure the final dashboard maintains consistent art direction.

How do I enforce visual consistency and a quality gate for landing page creation?

Enforce visual consistency by applying rule-driven constraints for focal points, type scale, and accent consistency during the build. A quality gate loop then scores the output and applies iterative fixes until the landing page reaches the minimum presentation threshold.

Can I build marketing pages and app screens without writing UI code from scratch?

Yes, you can generate marketing pages and app screens by instructing a model to read full design rules and apply composition constraints. The system builds the surface against these rules, ensuring the output feels intentionally art-directed rather than manually coded from scratch.

When should I use a score-and-fix loop for UI design?

Use a score-and-fix loop when a UI design has polish gaps, drift, or default-looking outputs that fail to meet visual craft constraints. The loop iteratively scores the result and applies fixes until it reaches the minimum acceptable presentation threshold.