Writing

Guides drafting of AAMAS author responses to preliminary reviews, focusing on double-blind compliance, no new results, and multi-reviewer pushback patterns.

Guides authors through AAMAS camera-ready preparation after acceptance, including de-anonymization, proceedings metadata, page reflow, rebuttal promise cleanup, and release of code and environments.

Audit the novelty and eligibility of an AAMAS submission by mapping related work across multiagent, game theory, and reinforcement learning venues, ensuring cross-community citation coverage that AAMAS reviewers expect.

Guides authors in preparing supplementary material for AAMAS conference submissions, including appendices with proofs, extended definitions, experiments, and anonymized code artifacts while ensuring compliance with page limits, anonymity, and size caps.

Assesses whether a research project is a strong fit for the AAMAS conference versus alternatives like AAAI, NeurIPS, or ICML. Helps identify the core interaction primitive and sharpen multiagent framing before writing begins.

A project-management workflow for AAMAS conference submissions, covering milestones from venue fit to camera-ready, with backward-planning offsets and common failure mode alerts.

Revise an AAMAS paper to highlight interaction contributions, name solution concepts, ensure game legibility, pair claims with proofs or experiments, fit the 8-page limit, and maintain double-blind wording.

Guides the preparation of anonymized supplement packages for ACL submissions, ensuring compliance with the Responsible NLP checklist and proper documentation of code, data, prompts, and annotation materials. Use when packaging artifacts for peer review in NLP conferences.

Automates component documentation by analyzing source code, demos, and existing docs to generate MDX files with live demos, API tables, and type definitions.

Guides users through a structured workflow for co-authoring documentation, proposals, technical specs, and decision docs. Helps transfer context, refine content, and verify reader understanding.

Automatically locates component source, demos, and existing docs to generate MDX documentation according to project conventions. Triggered when a user mentions a component name like Button or Accordion.

Guides users through a structured workflow for co-authoring documentation, proposals, technical specs, and similar content. Use when writing docs, creating proposals, or drafting specs.