vois-loop

Solid

Iterative design build loop for the Vois design system. Wraps design-ask, vois-router, and the full skill chain (vois-patterns, vois-components, vois-tokens, righter, design-rationale) in a loop that detects conflicts between skills and routes back upstream when something doesn't resolve cleanly. Includes an inline validation pass (no external skill required) that checks implementation correctness before design-rationale closes the loop. Use this as the single entry point for any feature build that starts from a ticket, brief, or raw description. Trigger when someone says "build this", pastes a ticket, or asks to run the full design loop.

Web & Frontend 20 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
44
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Vois Loop A loop orchestrator that runs the full Vois skill chain iteratively. Unlike vois-router which executes a linear chain, this skill enables skills to push back on each other and route upstream when conflicts arise. The loop encodes design iteration as a process, not a one-shot answer. ----- ## The loop at a glance ``` design-ask ↓ vois-router (classifies + sequences) ↓ vois-patterns → vois-components → vois-tokens ↑___________________loop back_________________| ↓ righter (inline throughout) ↓ validate (inline — see Step 4) ↓ design-rationale ``` **Where righter lives:** righter is not a sequential step. It runs inline throughout vois-tokens — whenever labels, errors, button copy, helper text, or any UI string is encountered. It does not run after vois-tokens. It runs during it. **Where validate lives:** validate is not an external skill. It is a structured pass defined in this skill (Step 4) that runs after vois-tokens completes. No external skill is needed or called. Max iterations: 3. If unresolved after 3 passes, surface the conflict to the designer rather than continuing to spin. ----- ## Loop state The loop maintains a state block that persists across all it...

Details

Author
ommakes
Repository
ommakes/Skills
Created
6 months ago
Last Updated
2 days ago
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

vois-router

Orchestrates the Vois design system skill chain. Use this skill as the single entry point whenever you're doing any UI work against the Vois design system — building a screen, picking a component, writing copy, or defending a design decision. The router reads your input, identifies the right starting point and skill sequence, and packages context forward so you don't have to re-explain the problem at each step. Works with vois-patterns, vois-components, vois-tokens, righter, and design-rationale. Each of those skills can still be used standalone — this router is additive, not a replacement. Trigger when someone says "build this screen", "what component should I use", "help me write this copy", "route me through the design system", or pastes any feature brief, ticket, or design question without specifying which skill to use.

20 Updated 2 days ago
ommakes
Web & Frontend Listed

design-loop

Use this skill when Tyler asks to run the design loop, fix compliance issues autonomously, iterate on the kitchen design, or when the user says 'run design:loop'. Orchestrates design:review → design:modify → design:qa in a capped cycle (max 3 iterations). DO NOT invoke for a one-shot review (use design:review) or a single spec edit (use design:modify).

8 Updated today
tstapler
AI & Automation Listed

vloop

Three-layer closed-loop engineering for AI coding agents — L1 plan-execute loop, L2 product-acceptance/redesign loop, L3 human review/requirement-update loop, with 12 backends (claude/codex/opencode/gemini/aider/copilot/cursor-agent/droid/amp/qwen/goose/kiro-cli). Use when the user wants to set up, run, resume, or cancel an autonomous coding loop, mentions "vloop", "loop engineering", "ralph", overnight agent runs, or wants an agent to work through a PRD/plan with acceptance gates. Also use PROACTIVELY — to propose, never to auto-start — when a request spans 3+ independent stories/features, asks to fully implement a PRD/spec/issue list, or signals unattended intent ("keep going until done", "overnight", "don't ask me at each step").

0 Updated 1 months ago
wikieden