Menu
Work on the revert.wtf Next.js frontend as a distinctive error-forensics product surface, not a generic SaaS or stock brutalist page.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run evidence-locked enrichment passes over existing revert.wtf catalog errors, preserving good entries while improving generic explanations, actions, references, and helper metadata.
Use revert.wtf safely from agents, tools, browsers, or integrations through bounded HTTP APIs, MCP tools, and lightweight package subpaths without downloading the full catalog into client bundles.
Add or update precise revert.wtf catalog entries, fixtures, source metadata, and matcher tests for one or a small set of EVM/RPC/provider/wallet/protocol errors.
Perform broader source-backed catalog enrichment for new EVM ecosystems, protocols, providers, standards, or deprecated/renamed/sunsetting coverage.
Maintain or use the read-only revert.wtf MCP server that exposes bounded catalog search, parser, selector lookup, AA explanations, x402 entries, and Blockscout registry tools to agents.
Modify or debug revert.wtf normalization, revert-data extraction, trace extraction, ABI decoding, catalog matching, selector lookup, or ERC-4337 decoding behavior.
| name | revertwtf-frontend-product-ui |
| description | Work on the revert.wtf Next.js frontend as a distinctive error-forensics product surface, not a generic SaaS or stock brutalist page. |
| version | 0.1.0 |
Use this skill when changing apps/web, visual design, UX, docs pages, tools, catalog browsing, or frontend verification.
The site should feel like an error-forensics instrument:
The user specifically disliked generic styling. Push for a unique product identity tied to EVM errors and debugging evidence.
"use client" components. Client tools should call apps/web/app/api/* routes or use tiny package subpaths like @revertwtf/catalog/panic.//errors/errors/[id]/catalog/tools/*/docs/*/aboutnode node_modules/typescript/bin/tsc -p apps/web/tsconfig.json --noEmit
If possible, run the app and visually inspect core routes:
pnpm --filter @revertwtf/web dev
If Next dev/build fails with local Windows spawn EPERM, report the limitation and at least run direct tsc plus Tailwind compilation:
node node_modules/tailwindcss/lib/cli.js -c tailwind.config.ts -i app/globals.css --minify
Run that Tailwind command from apps/web.