Authoritative architecture reference for the Blue Spec codebase. Use BEFORE writing or changing any source under src/, spec/, lib/, or test/, before adding an agent adapter, before touching the build path, and whenever a decision depends on repo layout, code conventions, the command/template split, the agent-agnostic core vs. adapter boundary, or what Blue Spec scaffolds into a target project. Covers the toolchain, directory layout, type rules, and the command formats each supported agent expects.
Loading catalogue content.
Skills in this kit
3 skills
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
How to simulate a Blue Spec command end to end so the user sees both the process and the results in chat. Use when the user asks to simulate, demo, preview, run, or see in action any bluespec command. Read this before attempting any such simulation.