vois-router

Solid

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.

Web & Frontend 21 stars 0 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 85/100

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

Skill Content

# Vois Router A single entry point for the Vois design system skill chain. You describe what you're working on. The router identifies which skills are needed, in what order, and carries context forward between them so each skill starts with what it needs. The skills this router coordinates: - `vois-patterns` — structural container decisions (SKILL.md + references/ per template) - `vois-components` — specific component selection (SKILL.md + references/ per job category) - `vois-tokens` — tokens, spacing, implementation (SKILL.md + references/ per topic) - `righter` — all UI copy, invoked inline throughout (SKILL.md + references/ already in place) - `design-rationale` — cognitive/behavioral audit, opt-in at two points in the chain (SKILL.md + references/ already in place) Each of these skills works standalone. The router adds orchestration on top — nothing more. The router never needs to know which reference file a skill reads internally — that's the skill's own routing logic. The router's job is just to tell each skill what task it's doing, and (for COMPONENT-ONLY runs) to flag when a scoped, partial read is appropriate instead of a full one. --- ## Step 0: Load project context Before routing anything, check for three files at the project root. These are the persistent memory layer. Without them, every session starts cold and the skill chain applies generic defaults instead of project-specific rules. ``` PRODUCT.md — strategic: why this exists, who it's for, what to a...

Details

Author
ommakes
Repository
ommakes/Skills
Created
4 months ago
Last Updated
4 days ago
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category