Execute multi-level exploratory testing that goes beyond smoke testing to actively find bugs through escalating test scenarios.

Post-implementation QA workflow: tests, code polishing, commit, and self-improvement.

Identify dead code in a codebase. **Core rule: code only used in tests is still dead code.** Only production usage counts.

Execute an implementation plan file.

Systematic methodology for finding the root cause of bugs, failures, and unexpected behavior. Cycle through characterize-isolate-hypothesize-test steps, with oracle escalation for hard problems. Diagn

Deep architecture report. Fans out parallel inspections across different aspects of the codebase, synthesizes their findings, and writes `.turbo/codebase-map.md` and `.turbo/codebase-map.html`. Analys

Current layout: unexpanded shells live in `.turbo/shells/` with `spec:` and `depends_on:` frontmatter. Plans live in `.turbo/plans/` with `status:` (required) and optional `spec:` for provenance. This

Launch the app and hands-on verify that it works by interacting with it. Every smoke test is a concrete interaction with the running app: navigating a screen, clicking a control, filling a form, runni

Ship an approved split plan as separate branches, commits, and PRs.

Read the latest update instructions from the local repo and follow them.

Searches, replaces, and reads text in Word documents. Use when the user asks to edit, search, or extract text from .docx files.

Rédaction de requêtes devant le Conseil de prud'hommes pour contester un licenciement pour faute grave. Utiliser ce skill quand l'utilisateur demande de rédiger une requête CPH, contester un licenciement pour faute grave, préparer une saisine du CPH pour un litige lié à un licenciement, ou créer un document de contestation de licenciement en droit du travail français.

Guide for creating effective skills. Use when users want to create a new skill (or update an existing skill) that extends the model's capabilities with specialized knowledge, workflows, or tool integrations.

Guide to analyze a current work session and propose improvements to skills. Use (1) automatically after working with a skill to capture learnings, (2) when the user suggests improvements, corrections, or additions during a skill-related session, or (3) when the user manually invokes `self-improve`.

Guide for reading, interpreting, and applying statutes, regulations, and rules in legal and compliance contexts. Use when the user asks about (1) how to read and interpret statutes, regulations, or rules, (2) statutory interpretation methods and canons of construction, (3) understanding legislative intent, (4) applying statutes to specific legal situations, (5) extracting requirements from legal text, (6) distinguishing between different types of legal requirements, or (7) cross-jurisdictional compliance analysis.

Write Go integration/unit tests following existing patterns in the codebase. Use when the user asks to write, add, or create tests for Go code.

Generates optimized descriptions for video platforms from transcripts and supplementary material. Use when the user asks for a video description or provides a transcript for video preparation.

Open the Claude Code Organizer dashboard — view and manage all memories, skills, MCP servers, hooks, and configs across scopes

Architecture map, layer responsibilities, key files, auth types, and debug runbook by symptom.

>

Generate research questions from economic phenomena

>-

>-

Divergent research ideation — generate many candidate directions, then adversarially filter to the strongest

Perform adversarial visual audit of Quarto or Beamer slides checking for overflow, font consistency, box fatigue, and layout issues.

Defamiliarization audit for empirical output. Systematically interrogates every feature of a figure, table, or set of results — not just the main finding. Named for Jason Fletcher, who asked about the spike at t=1 when everyone else was looking at t=2. Use when you have output and are about to interpret or report it.

You are **Referee 2** — a health inspector for academic work. You have a checklist, you perform specific tests, you file a formal report.

Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.

Challenge research design decisions, assumptions, and methodology choices with specific critical questions. Helps strengthen the paper before submission.

Interactive interview to formalize a research idea into a structured specification with hypotheses and empirical strategy.

Generate structured research questions, testable hypotheses, and empirical strategies from a topic or dataset.

Find and assess datasets for your research question. Two Explorer agents search in parallel across data source categories; an Explorer-Critic then stress-tests each candidate against the research desi

Formalize a research idea into a concrete project specification with testable hypotheses and empirical strategies.

Draft an academic manuscript from existing analysis outputs. Follows propose-first — the outline is always shown for approval before writing begins.

Design identification strategy or pre-analysis plan. Dispatches Strategist (proposer) and strategist-critic (validator). Replaces /identify and /pre-analysis-plan.

Draft academic paper sections with notation protocol, anti-hedging, and humanizer pass. Replaces /draft-paper and /humanizer.

>-

>-

>-

>-

'Converts LaTeX article-class .tex documents to Quarto .qmd format for multi-format publishing (HTML, PDF, Word). Use when asked to convert, port, migrate, or translate a .tex LaTeX file to Quarto; when porting an academic paper or manuscript from LaTeX to Quarto; when a .tex document needs to render to HTML, Word, or Typst PDF. Covers preamble → YAML front matter, section headings, text formatting, math, citations (natbib/biblatex), cross-references, figures, tables, lists, footnotes, hyperlinks, and special characters.'

>

Design and document statistical algorithms with pseudocode and complexity analysis

Numerical algorithms and computational techniques for statistics

Quality assurance and testing protocols for statistical software

Sensitivity analysis frameworks and assumption-testing methods

JASA/Biometrika manuscript structure with VanderWeele notation standards

Activate when the user is drafting any academic economics content from scratch (e.g., outlines, abstracts, introductions, data/methods/identification sections, results narratives, conclusions, referee responses, table/figure captions) and needs economics-specific structure, phrasing options, and quality checks to produce publication-ready prose.

Reads the manuscript and notebooks to generate a structured abstract. Use when writing or updating the abstract.

Scaffolds a method-specific analysis notebook (DiD, IV, RDD, LASSO, Panel FE) with boilerplate. Use when starting a new econometric analysis.