Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.

Express Spec-Driven Development for setting up project-aware change workflows, documenting domains, planning and applying changes in stages, verifying outcomes, and archiving completed work. Use only when the user explicitly asks for ESDD, references an ESDD command or artifact, or wants to continue an existing ESDD change.

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).

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

Review real software repositories for likely security issues using the local OWASP Top 10:2025 category set, official OWASP-mapped CWE lists, and canonical MITRE CWE records. Use when auditing source code, configuration, IaC, pipelines, dependencies, auth flows, crypto, logging, or error handling, and when the goal is evidence-based findings mapped to both CWE and OWASP 2025 with confidence levels and coverage gaps.

This skill should be used when the user says "arch vision", "architecture vision", "arn arch vision", "define the architecture", "tech stack", "what technology should I use", "design the system", "system architecture", "how should I build this", "technology choices", "choose technologies", "pick a tech stack", or wants to explore technology options and define the high-level architecture for a greenfield project. Takes a product concept as input and produces an architecture-vision.md document capturing the technology stack, system design, protocols, packaging strategy, and known risks.

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.

Content strategist and creator for multi-platform marketing campaigns. Writes blog posts, drafts social media captions, creates email newsletters, plans editorial calendars, develops SEO-optimized articles, and produces marketing copy for landing pages, ads, and video scripts. Use when the user needs to write a blog post, build a content calendar, draft social media content, create marketing copy, develop a brand voice guide, adapt long-form content for multiple platforms, produce a video or podcast script, or plan a full content campaign across channels. Best suited for general-purpose or cross-channel content creation; defer to a more specialized skill when the task is narrowly scoped to a single domain such as technical SEO auditing, advanced email-automation workflows, or paid media campaign management.

Reads a site feature specification file and converts it into a structured, actionable development task list saved to the project memory bank. Use when you need to break down requirements into developer tasks, plan project work from a PRD or spec, convert feature specifications into tickets with acceptance criteria, or create a task breakdown from site-setup documentation. Produces per-task acceptance criteria, file references, and technical stack notes drawn exclusively from the specification — no scope creep or unspecified features added.

Analyzes, redesigns, and automates business workflows to eliminate bottlenecks and improve efficiency. Creates process flow diagrams, identifies root-cause inefficiencies, writes standard operating procedures (SOPs), designs automation sequences, and produces implementation roadmaps with ROI estimates. Use when the user asks to map a business process, audit a workflow for inefficiencies, identify bottlenecks or handoff failures, create SOPs or checklists, design automation for repetitive tasks, apply Lean or Six Sigma techniques, or build a phased process improvement plan.

Develops brand guidelines, audits content for brand consistency, creates brand voice documentation, defines visual identity standards (colors, typography, logo usage), and produces brand strategy deliverables including positioning statements and messaging frameworks. Use when the user asks about brand guidelines, brand voice, logo usage, style guides, brand audits, naming, maintaining brand consistency across materials, or building a brand identity system from scratch.

Reviews web application UI using Playwright screenshot captures to identify visual bugs, broken interactive elements, layout regressions, and specification mismatches. Produces structured evidence-based QA reports with screenshot references, pass/fail verdicts, and prioritised fix lists. Use when asked to QA a web page, find UI bugs, run visual testing, check screenshot evidence, validate an implementation against a spec, review responsive layout, or verify interactive elements like accordions, forms, and navigation menus.

Sends HTTP requests to REST and GraphQL API endpoints, validates response codes, headers, and payloads, measures response times against SLA thresholds, generates structured test suites, and produces test reports covering functional, security, and performance scenarios. Use when the user asks about testing APIs, validating endpoints, checking HTTP status codes or response bodies, load testing, stress testing, debugging REST or GraphQL services, testing authentication flows, checking rate limiting, detecting SQL injection or OWASP API vulnerabilities, or integrating API tests into CI/CD pipelines.

Sends HTTP requests to REST and GraphQL API endpoints, validates response codes, headers, and payloads, measures response times against SLA thresholds, generates structured test suites, and produces test reports covering functional, security, and performance scenarios. Use when the user asks about testing APIs, validating endpoints, checking HTTP status codes or response bodies, load testing, stress testing, debugging REST or GraphQL services, testing authentication flows, checking rate limiting, detecting SQL injection or OWASP API vulnerabilities, or integrating API tests into CI/CD pipelines.

Expert user experience researcher that creates usability test plans, designs surveys, conducts user interview analysis, builds data-backed personas, maps user journeys, and synthesizes research findings into prioritized, actionable design recommendations. Use when the user asks about usability testing, user interviews, UX audits, survey design, persona creation, user journey mapping, A/B testing analysis, heatmap interpretation, accessibility research, or translating research data (interview notes, survey results, behavioral analytics) into design decisions. Distinct from general product management or analytics skills by focusing specifically on user behavior research methodology, participant recruitment, study design, and insight communication.

Designs and tracks scientific experiments, A/B tests, and feature rollouts for product and engineering teams. Defines experiment hypotheses, calculates required sample sizes, tracks variant performance metrics, analyzes statistical significance, and delivers ship/no-ship recommendations. Use when the user asks about designing A/B tests or split tests, setting up control vs. treatment groups, tracking experiment results, calculating statistical significance or confidence intervals, managing feature flag rollouts, or deciding whether to ship a feature based on experiment data.