case-study 2026-10-12 x-casejavascriptclaude-slidescodexobfuscation

Almost-complete Claude Slides editor: REA Skill reverse with Codex

A widely bookmarked X walkthrough names REA explicitly: pull the Slides front-end artifacts, wire REA into Codex, and let a REA Skill chew through obfuscated editor code toward a working reconstruction.

Source meta

— GitHub stars (snapshot)

Language: —

License: —

Updated: —

GitHub source: —

rea.run rating

5/5 — REA Skill reverse of Claude Slides

Quality. High-engagement walkthrough with clear install → reverse steps and screenshots.

Evidence. Public X thread + four self-hosted screenshots; author names REA explicitly.

Limits. Author’s session on assets they chose to inspect — not a license to crack third-party SaaS DRM.

For. Builders studying obfuscated front-end editors they are authorized to analyze.

Step context from @dotey Claude Slides reverse thread (1/4)

Step context from @dotey Claude Slides reverse thread (2/4)

Step context from @dotey Claude Slides reverse thread (3/4)

Step context from @dotey Claude Slides reverse thread (4/4)

Public metrics (snapshot)

Metric	Figure	Note
Views	~71k	Author post at capture
Likes	676	Snapshot 2026-10-12
Bookmarks	999	Snapshot 2026-10-12
Reposts	103	Snapshot 2026-10-12
Source	@dotey	Four screenshots self-hosted

Four-step flow (as described by the author)

Step	Action
1	Download the editor’s scripts and styles
2	Install REA through Codex (`npx rea-agents… setup` pattern)
3	Run a REA Skill against the obfuscated code
4	Iterate until the reconstructed editor covers nearly full functionality

Operator checklist (authorized copies only)

Confirm you may keep and analyze the downloaded assets.
Pin a reproducible rea-agents version after setup.
Ask the agent for Evidence on module boundaries, not vibes alone.
Keep proprietary blobs out of public repos unless license allows.
Cross-link findings to your own rebuild tests.

Screenshots

The four images below are self-hosted copies from the public thread (for case archival). See the original post for full context and any updates from the author.

Why it is on rea.run

High-signal community proof that people already pair Codex + REA Skill on messy front-end packages — with steps others can audit, not a crack script dump.

Compliance

Lawful RE only on software and copies you are authorized to analyze. Reconstructing editor behavior for learning is not permission to pirate, bypass billing, or redistribute proprietary assets.

Takeaways

Author-named REA + Codex Skill path on obfuscated JS.
Steps: fetch assets → setup REA → Skill reverse → verify rebuild.
Authorization and redistribution limits still apply.

Related on rea.run