Show HN: Use After Effects with Claude Code, Cursor and Antigravity

Description and use

**Brief Summary (2‑3 sentences)**
The “Show HN: Use After Effects with Claude Code, Cursor and Antigravity” project demonstrates how to integrate Adobe After Effects with AI‑powered coding assistants (Claude Code), the Cursor IDE, and the Antigravity UI framework. It provides a proof‑of‑concept workflow that lets users generate and edit After Effects scripts or expressions via natural‑language prompts, then run them directly in the After Effects environment.

**Value**

• **Rapid prototyping**: Designers and motion‑graphics artists can describe visual effects in plain English and get ready‑to‑run ExtendScript/JSX code instantly, cutting down iteration time.
• **Unified toolchain**: By bridging After Effects with modern AI coding assistants and a lightweight UI (Antigravity), the project creates a single, searchable interface for script generation, testing, and tweaking.
• **Collaboration**: Generated code can be version‑controlled and shared, making it easier for teams to review and refine AI‑suggested scripts.

**Practical Adoption Path**

1. **Clone & review** – Fork the repository, read the README, and verify the licensing (likely MIT/Apache).
2. **Set up dependencies** – Install Claude Code (or an API key for Anthropic), the Cursor IDE, and the Antigravity package; ensure After Effects is on the same machine and that the ExtendScript engine is accessible.
3. **Run the demo** – Execute the provided starter script to confirm that prompts from Claude are turned into valid JSX and that Antigravity’s UI can launch the generated code in After Effects.
4. **Integrate into workflow** – Replace the demo prompts with your own internal templates (e.g., “Create a lower‑third animation with a bounce”), and embed the CLI/GUI into your existing pipeline (e.g., as a pre‑render step).
5. **Validate & iterate** – Add unit tests for generated scripts, monitor API usage limits, and set up CI to lint both the AI‑generated code and the surrounding glue code.

**Production Readiness**

• **Maturity**: Medium. The project is recently updated (2026‑07‑13) and shows a functional prototype, but integration signals are sparse and documentation is minimal.
• **Risks**: Limited test coverage, potential breaking changes in Claude’s API, and reliance on proprietary After Effects scripting. Verify the license, check issue tracker activity, and consider fallback mechanisms (e.g., manual script edits).
• **Recommendation**: Suitable for internal tools, proof‑of‑concepts, or early‑stage pipelines after a short validation sprint. For production‑critical workloads, perform a thorough security and maintenance audit, lock down API versions, and add monitoring around script execution.

Use in a workflow

Show HN: Use After Effects with Claude Code, Cursor and Antigravity may be useful when its README and activity match a concrete workflow.

Limitations and review notes

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.