Loading...
Loading...
Found 874 Skills
Spec Status - displays pipeline progress dashboard for a single specification showing document statuses, blockers, and next action.
Executes the Antagonistic-Review process from the Elephant-Goldfish Model (EGM) via an automated multi-agent review loop to audit documents against qualitative standards and structural templates, and automatically apply approved fixes. Use when reviewing design docs, READMEs, feature specifications, implementation plans, or verifying document completeness and tone.
United Arab Emirates architectural code and regulatory reference. Covers the federal regulatory framework (UAE Fire and Life Safety Code of Practice 2018 by General Civil Defence, Federal Law 29/2006 + 2/2014 + 1/2020 for People of Determination, ESMA standards) plus the seven Emirates' independent codes: Dubai Building Code 2021 (DBC), Dubai Civil Defence regulations, Trakhees regulations for free zones, Dubai Green Building Regulations & Specifications 2011 + Al Sa'fat 2016, Dubai Universal Design Code 2017; Abu Dhabi International Building Code 2013 (ADIBC, IBC-derived), Estidama Pearl Building Rating System 2010, DMA Accessibility Code; Sharjah Department of Planning and Survey rules; northern emirates' deferral patterns to Abu Dhabi or Dubai codes. Includes climate zone hot-arid design overlays, sandstorm/ thermal expansion loads, ADM/DM approval workflows, RERA Dubai project registration, developer-master-developer-end-customer hierarchies (Emaar, Aldar, Nakheel masterplan compliance), DEWA/ADDC utility coordination, and the cross-walk between IBC, ASCE 7, NFPA, and UAE national amendments. Practitioner-grade clause-level reference for design teams working in any of the seven Emirates.
Use this skill to shape product or engineering work before committing time to it: set appetites instead of estimates, narrow raw ideas into bounded problems, sketch solutions at the right level of abstraction, de-risk rabbit holes, write pitches, bet with capped downside (circuit breaker), and govern builds with discovered scopes and scope hammering. Adapted from Basecamp's Shape Up and extended for human+AI-agent teams. Use when a raw idea, feature request, or "redesign X" grab-bag needs to become a bounded project before anyone builds; when planning how much work an idea is worth; or when delegated agent builds need budgets, kill criteria, and non-convergence rules. Do not use for discovering whether a problem is real (use product-discovery), for portfolio-level sequencing across quarters (product-roadmapping-and-portfolio), for formal specification after the bet is placed (spec-driven-development), or for task-level prioritization frameworks like RICE (product-methodology).
Decode a reference image or brief description into an editable halftone paper-collage specification. By default, use the Codex built-in `image_gen` to create brand-consistent stills and transparent layers, then use local FFmpeg or HyperFrames to produce a deterministic motion video that assembles piece by piece from an empty background. Use this when the user mentions halftone collage, paper collage, paper-cut collage, editorial collage, magazine collage, retro print collage, collage motion, collage animation, paper-cut animation, paper-piece assembly, layer-by-layer assembly, from nothing to something, elements flying in and assembling, stop-motion collage, stop-motion animation, Arcads style, reference-image breakdown, style breakdown, reverse-engineering a visual, “make it in this style,” “make something similar,” “generate collage stills,” “animate this image,” “make these elements assemble,” or “create a collage ad or collage explainer video.” English trigger semantics include editorial collage, halftone collage, paper collage, paper-cut motion, stop-motion graphic, assemble from empty, build-on motion, analyze this, break this down, reverse-engineer this look, generate the stills, animate this, and make these move. By default, do not invoke Arcads, Nano Banana, Seedance, or Kling. Enter an external generation path only when the user explicitly requests it and the corresponding connector is available.
Grill me about specs for the workflows I want to build, within this workspace.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
Turn ambiguous coding requests into verified Cursor Agent implementation specs. Use when the user wants requirements, an implementation plan, or a spec before coding; include source checks, needed ADRs, and agreed delivery. Do not use for already specified direct implementation or memory cleanup.
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Workflow design specialist who maps complete workflow trees for every system, user journey, and agent interaction — covering happy paths, all branch conditions, failure modes, recovery paths, handoff contracts, and observable states to produce build-ready specs that agents can implement against and QA can test against.