juspay/xyne-spaces

ticket-specs

Create, regenerate, update, and review Xyne Spaces ticket Specifications by interviewing for requirement intent before drafting or writing the Specification.

browser-qa-delivery

Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.

dashboard-data

Build truthful self-contained dashboard snapshots from connected MCP/data tools or user-provided datasets. Use for /dashboard runs that query real metrics, render charts or operational summaries, and may be refreshed by scheduled jobs.

data-visualization

Design truthful, readable charts, diagrams, dashboards, and metric displays with appropriate encodings, hierarchy, annotation, and responsive behavior.

design-brief

Turn a product or visual request into a concrete interface brief, content hierarchy, user journey, and acceptance checklist before implementing a Design Studio artifact.

design-critique

Critique and polish an existing interface by finding hierarchy, consistency, usability, content, accessibility, and visual-quality defects before delivery.

design-system

Create or modify coherent visual tokens and reusable component rules for color, typography, spacing, radius, elevation, controls, and interaction states.

frontend-composition

Implement polished self-contained HTML interfaces with semantic structure, maintainable CSS, realistic content, and purposeful visual hierarchy.

motion-interaction

Add purposeful interaction and motion to HTML designs, including state transitions, feedback, navigation, disclosure, and reduced-motion behavior.

react-artifact

Author app-like designs in React/JSX and bundle them in-sandbox into the same single self-contained HTML artifact Design Studio delivers. Use when the design needs real state, complex interactivity, or component reuse beyond what vanilla JS comfortably…

responsive-accessibility

Make Design Studio artifacts responsive, keyboard operable, semantically correct, and readable across common viewport and input conditions.

architecture-diagrams

Author architecture, ER, and flow diagrams as hand-written inline SVG inside a self-contained HTML page — no mermaid, no scripts, no CDN.

evidence-citations

Anchor every claim in an explanation to file:line evidence you actually opened, and mark the difference between what you verified and what you inferred.

explanation-document

Structure a codebase/schema explanation as a self-contained HTML document ordered for a READER — mental model and flows first, deep per-component reference last — not in the order you explored it.