Skill UI

Sends a board memo or strategy brief to multiple AI models (Claude, Codex, Gemini) for independent review, then reconciles consensus and divergences. Used for high-stakes, irreversible decisions like fundraises, pivots, layoffs, or regulatory commitments, offering an objective sanity check before moving forward.

Before You Build acts as a crucial checkpoint in the AI coding workflow. It prevents premature implementation by rigorously assessing product risk—analyzing market demand, existing user workflows, switching costs, and distribution channels. Instead of writing code, it guides the user to define core assumptions and propose the smallest, most effective validation test (e.g., landing page test, user interview) before committing resources.

A comprehensive guide for structuring Human-Robot Interaction (HRI) conference submissions. It outlines the critical distinction between core, decision-making content (which must remain in the 8-page body) and supplementary materials (e.g., extended tables, instruments, codebooks). Special emphasis is placed on treating the video figure as a primary artifact, ensuring it is short, legible, and properly anonymized for double-blind review.

This comprehensive guide provides authors with a step-by-step workflow for submitting manuscripts to the Journal of Accounting and Economics (JAE) via Elsevier's Editorial Manager. It details crucial requirements, including executing double anonymization, formatting specific metadata (Highlights, JEL codes, Keywords), managing submission fees, and ensuring all files are correctly sequenced for the final review PDF.

A comprehensive final checklist for authors submitting manuscripts to top academic journals (e.g., JAP) via Editorial Manager. It ensures compliance with APA 7th edition style, full author anonymization for masked review, adherence to open science (TOP) standards (data/code availability), and statistical rigor. This guide helps prevent common submission failures before final upload.

This command acts as a crucial product gate, forcing a deep, strategic review before any code is written. Instead of simply fulfilling the request, it guides users through three structured roles: Scope Expansion (finding the 10x vision), Hold Scope (stress-testing assumptions and failure modes), or Scope Reduction (defining the true MVP). It ensures that the developed solution solves the user's real job-to-be-done, not just the explicit feature request.