__Campaign

Full end-to-end project planning agent that takes a rough idea all the way through research, planning, organization, and validation before any code is written. Use this skill whenever a user has a new project idea and wants structured, phase-by-phase help turning it into a complete, research-backed, approved plan — even if they don't explicitly say "project planning". This is the right skill any time someone wants to think before they build. Always trigger this skill for phrases like: "I have a project idea", "help me plan my project", "let's plan this before we build", "what should I figure out before starting", "turn my idea into a project plan", "help me go from idea to plan", "project planning", "create a project brief", "I want to build a SaaS / app / tool / website — where do I start?", "I have an idea but don't know where to begin", "help me think through this idea", "should I build this?", "help me scope this project", "I need a PRD and roadmap before we code anything", "let's research this idea first

Designs and documents REST and GraphQL APIs, OpenAPI specifications, service boundaries, and integration contracts. Use this skill when a user asks to design an API, define endpoints, create a REST or GraphQL schema, write an OpenAPI or Swagger spec, establish a service contract, map integration points between services, or document an existing API. Common phrasings: "design an API for my app", "write an OpenAPI spec", "define REST endpoints", "create a GraphQL schema", "document this service's interface", "what endpoints do I need?", "help me plan my API surface". Do NOT use for implementing API server code, writing client SDK code, or running/testing live API requests — those require execution environments beyond this skill's scope.

Designs REST and GraphQL APIs including endpoint definitions, request/response schemas, authentication patterns, error-handling conventions, and OpenAPI documentation. Use this skill when a user asks to design an API, create API specs, define endpoints, document a service interface, plan an API surface, or establish request/response contracts. Common phrasings: "design an API for X", "create an OpenAPI spec", "what endpoints should I have?", "define my REST routes", "write a Swagger file", "document my service interface", "help me plan my API". Do NOT use when the user wants to implement handler code, test a live API, write client SDKs, or when the request is about database schema design (use database-schema-skill) or service orchestration architecture.

Reviews code for correctness, security vulnerabilities, performance issues, readability, and adherence to best practices and team conventions. Use this skill when a user asks for a code review, PR review, feedback on code quality, a security audit of code, style or pattern improvements, or a second opinion on an implementation. Common phrasings: "review this code", "check my PR", "look at this function", "is this secure?", "any issues with this?", "code feedback please", "audit this module", "does this follow best practices?". Do NOT use when the user wants code written from scratch (no existing code to review), or when the request is purely about running/executing code, deploying, or testing infrastructure — this skill reads and critiques existing code only.

Designs analytics and operational dashboards including layout, chart types, KPI cards, filters, drill-downs, and data visualizations. Use this skill when a user asks to design a dashboard, create data visualizations, build a metrics view, display charts or graphs, plan a reporting interface, or structure an analytics page. Common phrasings: "design a dashboard for X", "what charts should I use?", "help me visualize this data", "create a metrics view", "build a reporting page", "I need a KPI dashboard", "show me how to display this data visually". Do NOT use when the user wants to write the actual frontend code for a dashboard (use a code-generation skill), query the underlying data (use notebook-query-skill), or set up a BI tool like Tableau or Looker.

Cleans, normalizes, and validates datasets: fixes formatting inconsistencies, handles null/missing values, deduplicates records, standardizes field values, validates data types, and prepares data for downstream analysis or import. Use this skill when a user has messy data to fix, needs to normalize a CSV or table, wants data preparation before analysis or loading, or needs a cleaning plan for a dataset. Common phrasings: "clean this data", "fix my CSV", "normalize these fields", "deduplicate this table", "my data has inconsistencies", "prepare this for analysis", "standardize these values", "handle nulls in my dataset". Do NOT use when the user wants to analyze or visualize already-clean data (use notebook-query-skill), design a database schema (use database-schema-skill), or build an ETL pipeline (beyond cleaning rules, into full pipeline architecture).

Design and document the PostgreSQL database schema, migrations, seeds, and indexes. Use when the user asks to create tables, relationships, migrations, or seed data.

Designs relational and NoSQL database schemas: tables, fields, data types, relationships, foreign keys, constraints, indexes, and naming conventions. Use this skill when a user asks to design a database, create tables, define a schema, model entities and their relationships, map ERDs, or plan database structure. Common phrasings: "design a database for X", "create the tables for my app", "define a schema", "model these entities", "what tables do I need?", "design my data model", "create an ERD", "how should I structure my database?". Do NOT use when the user wants to write queries against an existing database (use notebook-query-skill), clean/transform data (use data-cleaning-skill), or design an API (use api-design-skill). Schema design is the focus — not query writing or data migration.

Scaffold, build, and extend the DZIRE design system. Use when the user asks to create tokens, components, layouts, or patterns.

Generate and maintain project documentation. Use when the user asks to write, update, or produce docs, a README, changelog entry, architecture guide, or setup guide.

Create and run agent evals to verify AI output quality. Use when the user asks to test agent outputs, create eval cases, or benchmark skill performance.

Generates and evaluates pre-launch readiness checklists covering security, performance, accessibility, SEO, monitoring, observability, and go-live operational steps. Use this skill when a user is preparing to launch a product, feature, or service; needs a release checklist; wants to verify launch readiness; or is conducting a pre-flight review. Common phrasings: "are we ready to launch?", "create a launch checklist", "pre-launch review", "what do I need before going live?", "release readiness check", "launch prep list", "pre-production checklist", "go-live checklist". Do NOT use when the user wants to write deployment scripts or CI/CD pipelines (that's infrastructure work), perform ongoing post-launch monitoring (use a monitoring/alerting skill), or conduct a security audit of code (use code-review-skill for code-level review).

Writes, structures, and improves Markdown documentation: READMEs, wikis, API docs, guides, tutorials, technical references, and changelogs. Use this skill when a user asks to write docs, create a README, document a project, improve existing documentation, write a guide or tutorial, create a wiki page, or structure technical reference material. Common phrasings: "write a README for this", "document this project", "improve my docs", "create a getting started guide", "write API documentation", "help me with my wiki", "turn this into a proper doc", "document this function/module", "write a changelog". Do NOT use when the user wants to write code (not docs), design a database or API (use dedicated skills), or create presentation slides — this skill produces Markdown text files only.

Define KPIs, events, and reporting views for a project or feature. Use for success metrics, tracking plans, measurement frameworks, or analytics dashboards.

Designs scoring models, weighted formulas, ranking systems, evaluation rubrics, and calculated metrics for business logic and data evaluation. Use this skill when a user needs a scoring formula, ranking algorithm, weighted grading system, evaluation rubric, priority score, lead scoring model, health score, risk score, or any calculated metric definition. Common phrasings: "design a scoring model for X", "create a ranking formula", "how should I weight these factors?", "build a lead score", "create an evaluation rubric", "design a risk score", "what's a good formula for scoring Y?", "help me rank these items". Do NOT use when the user wants to run or apply the formula to actual data (use notebook-query-skill), visualize scored results (use dashboard-design-skill), or train a machine learning model — this skill designs formulas and rubrics, not ML pipelines.

Writes SQL queries, data analysis notebooks (Jupyter/Python/R), and analytics workflows for data exploration, reporting, and insight generation. Use this skill when a user asks for SQL queries, data analysis scripts, notebook cells, analytics code, data exploration workflows, or wants to extract insights from a dataset. Common phrasings: "write a SQL query for X", "help me analyze this data", "create a Jupyter notebook", "how do I query this table?", "give me Python to explore this dataset", "write analytics code", "I need a report query", "summarize this data with code". Do NOT use when the user wants to clean messy data before analysis (use data-cleaning-skill), design a database schema (use database-schema-skill), visualize results with a dashboard UI (use dashboard-design-skill), or train/build a machine learning model.

Converts raw ideas into structured project plans, phases, MVP scope, risks, and outputs.

Gathers and structures project requirements: goals, scope, stakeholders, deliverables, constraints, timeline, and success criteria. Use this skill when starting a new project, onboarding a client, capturing requirements from a conversation or brief, structuring a project proposal, or creating a project charter. Common phrasings: "help me start a new project", "capture my requirements", "create a project brief", "I want to kick off a project", "define the scope of this project", "write up what we discussed", "structure my project plan", "help me onboard this client", "what do I need to define for this project?". Do NOT use when the project is already defined and underway — this skill is for the intake/discovery phase, not ongoing project management, status reporting, or sprint planning (those are execution-phase activities).

Convert product ideas into structured briefs with scope, audience, features, and revenue paths. Use for startup concepts, app ideas, or any project needing a clear, actionable brief.

Build and extend the search system. Use when adding search routes, indexing, ranking, filters, or search analytics.

Run SEO audits on CMS posts, generate SEO reports, score content quality, and provide keyword and tag recommendations.

Creates new AI skills, improves existing ones, and measures skill performance through eval-driven iteration. Use when a user wants to build a skill from scratch, rewrite or refine an existing SKILL.md, run test prompts to evaluate skill quality, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. Common phrasings: "create a skill for X", "improve this skill", "run evals on my skill", "why isn't my skill triggering?", "write a SKILL.md for Y", "help me test and iterate on this skill". Do NOT use for general coding tasks, answering questions, or creating non-skill documentation — this skill is specifically for authoring and iterating on SKILL.md files and their associated eval sets.

Define, document, and extend social media graphic templates and design rules for the DZIRE brand. Use when the user asks about social asset specs, post templates, or platform-specific design rules.

Verify the project environment and stack are correctly installed and configured. Use when the user asks to check the stack, confirm tools are installed, or set up the environment.

VIP subscription lifecycle management for DZIRE_v1. Handles plan display, Stripe Checkout redirect, webhook activation, and VIP access control.

Create and extend reusable UI components in the DZIRE design system. Use when the user asks to build components like inputs, selects, tooltips, drawers, tabs, or any other primitive UI element.

Test web apps with Playwright: verify UI, capture screenshots, debug browser issues, and automate interactions. Use for frontend testing, browser automation, or UI verification.

Ask Copilot what files it needs to see before answering a question