Uses failing test results as signals to guide bug search and narrow down candidate fault locations. Use when one or more tests are failing and the user wants to understand what's broken, when CI reports failures, or when triaging a batch of test failures after a change.

Automatically synthesizes code patches to fix identified bugs, leveraging the bug location and surrounding context. Use when a bug has been localized and the user wants an automated fix, when generating candidate patches for review, or when the user asks to fix a specific bug.

Z.AI CLI providing: - Vision: image/video analysis, OCR, UI-to-code, error diagnosis (GLM-4.6V) - Search: real-time web search with domain/recency filtering - Reader: web page to markdown extraction - Repo: GitHub code search and reading via ZRead - Tools: MCP tool discovery and raw calls - Code: TypeScript tool chaining Use for visual content analysis, web search, page reading, or GitHub exploration. Requires Z_AI_API_KEY.

Triage router for all Luzmo problems. Use first whenever anything is broken, not working, or behaving unexpectedly. Triggers on: "not working", "broken", "why is X failing", "debug", chart "0 height", "chart not loading", "wrong data showing", API errors. Diagnoses root cause by symptom and routes to the right implementation skill. Does NOT implement fixes. Use this skill first - even if you think you know the fix - for any Luzmo error, rendering failure, data anomaly, or unexpected behavior.

Visual customization and branding for Luzmo surfaces. Use for custom colors, white-labeling, dark/light modes, and per-tenant themes. Triggers on: "change colors", "brand styling", "dark mode", "white-label", "custom theme", "IQ Chat styling", "ACK theming". Routes to the correct mechanism per surface: Theme API for dashboards, CSS variables for IQ Answer, IQChatOptions for IQ Chat, Flex runtime theme. Not for chart data or slots (use data-visualization) or data security (use multitenancy).

Server-side Luzmo resource operations - CRUD, automation, and bulk API scripts. Use for listing, searching, creating, or deleting dashboards, datasets, themes, users, groups. Triggers on: "list all dashboards", "delete dataset", "bulk update", "automate", "script", "find resources". Critical: all deletes are irreversible and require explicit user confirmation before execution. Not for embedding saved dashboards/charts (use core), auth setup (use core), or data ingestion (use data-integration).

Getting data into Luzmo from any source. Use whenever connecting a database, pushing files, or modeling data. Triggers on: "connect data source", "upload CSV", "import data", "sync from database", "push data via API", "data not loading", createDataprovider. Provides ready-to-use scripts. Covers data modeling, Warp acceleration, and custom connectors. Use eagerly for any data-source or schema question. Essential before charts can display anything. Not for chart rendering (use data-visualization) or per-tenant access control (use multitenancy).

Build a brand-new Luzmo chart component when no built-in chart type (and Flex) is sufficient. Triggers on: "custom chart", "build a custom chart", "no built-in chart type fits", "chart plugin", "manifest", "render/resize/buildQuery", "custom chart not in picker", "upload custom chart", "org release". Rare advanced path (~95% of users never need this). Not for Flex charts with built-in types (use data-visualization), embedding saved dashboards (use core), self-service chart editors (use analytics-studio), or auth setup (use core).

Core Luzmo setup - use whenever starting a new integration or hitting auth/API errors. Triggers on: API credentials (LUZMO_API_KEY, LUZMO_API_TOKEN), embed token generation (createAuthorization), SDK selection, 401/403 errors, REST-verb confusion, "how do I authenticate", "embed dashboard", "dashboardId", "dashboard not rendering". Essential starting point before any feature skill. Use eagerly for any auth or saved-dashboard/chart embedding question. Pair with domain skills for feature-specific work. Not for building charts in code (use data-visualization), data loading (use data-integration), or tenant isolation (use multitenancy).

Build a self-service analytics environment inside your application. Two approaches - out-of-the-box Embedded Dashboard Editor (editMode) or custom Analytics Components Kit (ACK). Use for letting end-users create/edit dashboards, white-label studios, editMode, designer/owner token roles, and ACK configuration. Triggers on: "self-service analytics", "let users edit dashboards", "embedded studio", "analytics components kit", "ACK", "designer role", "dashboard editor". Critical pattern: ACK configures -> your app stores state -> separate renderer displays. Not for view-only embedding of saved dashboards (use core), building charts in code (use data-visualization), data connection (use data-integration), or AI queries (use ai-analytics).

AI-powered analytics with Luzmo - /aiprompt API and IQ embed components. Use for natural language data queries, chart generation, agentic workflows (agent analyst|item, tasks), IQ Chat/Answer embedding (luzmo-iq-embed-chat, LuzmoIQChatComponent), "AI not working", wrong answers, quality optimization. Requires AI/IQ addon license. Use eagerly for any natural-language analytics feature. Not for standard chart embedding (use core for saved dashboards, data-visualization for Flex) or React Native (IQ embed components are web-only).

Analyze recent code changes via git history and extract software engineering lessons. Use when the user asks 'what is the lesson here?', 'what can I learn from this?', 'engineering takeaway', 'what did I just learn?', 'reflect on this code', or wants to extract principles from recent work.

This skill should be used when the user says "visual sketch", "arn visual sketch", "sketch directions", "explore visuals", "visual proposals", "try different looks", "design directions", "sketch the UI", "visual exploration", "compare styles", "show me options", "what could this look like", or wants to generate multiple visual direction proposals as real HTML/CSS running on the scaffolded project's dev server, iteratively selecting and refining until a final visual direction is chosen.

This skill should be used when the user says "use cases", "arn use cases", "write use cases", "define use cases", "Cockburn use cases", "actor goals", "behavioral requirements", "system behavior", "what does the app do", "describe the behavior", "use case document", "document the behavior", "define system behavior", or wants to create structured use case documents that describe the application's behavior from actor perspectives, producing a use-cases/ directory with individual Cockburn fully-dressed use case files and a README index.

This skill should be used when the user says "prfaq", "pr faq", "pr/faq", "press release stress test", "stress prfaq", "amazon pr faq method", "test the pitch with a pr/faq", "validate concept through pr/faq", "critique press release", "pr faq stress test", "will this marketing story hold up", or wants to stress-test a product concept by drafting a compelling press release and FAQ, then adversarially critiquing it to find where the concept cracks under scrutiny. Produces a PR/FAQ report with the full draft, adversarial questions, crack point analysis, and recommended concept updates.

This skill should be used when the user says "pre-mortem", "premortem", "risk analysis", "stress premortem", "failure analysis", "what could go wrong", "pre mortem", "investigate failure", "failure modes", or wants to stress-test a product concept by applying Gary Klein's pre-mortem methodology to identify hypothetical failure root causes, early warning signals, and mitigation strategies. Produces a pre-mortem report with 3 root causes across distinct failure dimensions and recommended concept updates.

This skill should be used when the user says "stress interview", "synthetic interview", "user interview stress test", "interview my personas", "test with synthetic users", "persona interview", "simulate user interviews", "run user interviews", or wants to stress-test a product concept by conducting structured interviews with synthetic personas through three adversarial lenses (Pragmatist, Skeptic, Power User). Produces an interview report with per-persona findings, synthesized themes, and recommended concept updates.

This skill should be used when the user says "competitive analysis", "gap analysis", "competitive gap", "stress competitive", "compare competitors", "feature comparison", "competitive stress test", "market comparison", "competitor analysis", or wants to stress-test a product concept by conducting deep competitive gap analysis with feature comparison, gap identification, and positioning assessment. Produces a competitive report with a feature matrix, per-competitor analysis, and recommended concept updates.

This skill should be used when the user says "static prototype", "arn static prototype", "visual validation", "pixel perfect", "component showcase", "static screens", "build a static prototype", "create a component showcase", "visual review", "validate the visuals", "check the design", "validate components", "review the design visuals", or wants to create a static component showcase and validate it through iterative expert review cycles with per-criterion scoring, an independent judge verdict, and versioned output.

This skill should be used when the user says "scaffold", "arn scaffold", "set up the project", "create project", "initialize project", "bootstrap project", "create the skeleton", "install dependencies", "configure the project", or wants to create a working project skeleton from architecture decisions with installed dependencies, configured build tools, and a UI toolkit ready for development.