Skill Orchestration

Orbit doesn't just "write code"; it understands engineering domains. Our Skill Manager allows you to tap into specialized knowledge.

Slash Commands

You can explicitly trigger skills by typing a slash command in the chat:

• /audit: Perform a high-level audit of the current feature for accessibility, performance, and best practices.
• /critique: Get a detailed design review focusing on visual hierarchy and emotional resonance.
• /polish: Add the "final 10%" — refining spacing, alignment, and micro-interactions.
• /distill: Strip away unnecessary complexity to reach a clean, powerful essence.

Dynamic Awareness

Even without explicit commands, Orbit's planner is aware of these tools. If it detects you are building a design-heavy component, it will automatically leverage the Frontend Design skill to ensure the results are premium and non-generic. The same logic applies to research workflows: when a prompt asks for market analysis, the planner routes the task through the deep-research pipeline before a single line of code is generated.

Custom Skills

The skill catalog is not closed. Orbit supports custom skills that are shared with the execution runtime and loaded from the canonical skills directory. A skill is a packaged prompt-plus-toolset that describes when it applies, what it evaluates, and how it reports back. You can define a team-specific skill — for example, a brand voice checker that enforces your copy guidelines, or a compliance linter that scans generated code for regulated data patterns — and then invoke it exactly like a built-in skill.

Combining Skills

Skills compose. A typical publish flow runs /audit for engineering health, then /critique for visual quality, then /polish to apply the fixes, and finally /distill to remove dead code before sharing. Because every skill operates on the same sandbox state, each pass builds on the previous one without forcing you to re-explain your intent.