vishwakarma

List every available Vishwakarma skill with its id, category, trigger description, and context cost. Call this to see what guidance exists before deciding what to load.

Find the skills relevant to what you are about to do. Describe the task in your own words — for example "building a pricing page with animated cards" — and this returns the skills that apply, ranked. Call this first, before writing any interface code.

Retrieve the full working knowledge of one skill: its body, its normative rules with the reasoning behind each, and the self-checks to run before reporting completion.

Retrieve deep reference material attached to a skill — edge cases, catalogues, worked examples. Only fetch one when its stated question is the question you actually have.

Compute the contrast between a foreground and background colour, and report whether it meets accessibility requirements. Use this instead of estimating — contrast is arithmetic, and estimates are unreliable in the mid-tones where most failures happen.

Generate a perceptually even colour ramp from a single seed colour, in OKLCh. Produces the 50–950 steps with lightness spaced by perception rather than by arithmetic, chroma shed toward the ends, and every step gamut-mapped without hue drift.

Turn a semantic motion intent into concrete duration, easing, and CSS. Choose the intent by what the motion means, not by how long you want it to take — the timing follows from the meaning.

Report whether a CSS property can be animated on the compositor or forces layout every frame, with a concrete alternative when it does.

Compute per-element delays for a group reveal, with automatic compression so a long list still reads as one gesture rather than a queue.

Resolve a deterministic set of design decisions — hero composition, section rhythm, emphasis strategy, accent discipline, motion character — from the brief. Call this BEFORE designing anything. It exists to stop the design collapsing onto the most predictable option, which is what makes generated wo…

Build a CSS clamp() that scales a value with viewport width. Retains a rem term so the result still respects the user’s browser font-size setting, which a pure vw value would ignore.

Return the viewport configurations to verify against, and exactly what to check at each. Use this instead of asking whether something "is responsive", which is not a checkable question.

Evaluate measurements taken from an interface against the project Design Contract, and return specific violations with fixes. Extract the actual values from your output and pass them here rather than judging by impression.

Generate a complete design token set in the requested format. Supply a brand colour to derive the whole system from it, including a dark theme that is a separate design rather than an inversion.