eip

What problem does it solve?

This Skill prevents inconsistent or non-compliant implementation of Ethereum Improvement Proposals by giving a strict, repeatable blueprint for where each helper, schema, and JSON-RPC method must live.

Core Features & Use Cases

• Enforces the ownership rule: anything that exists because of an EIP belongs under packages/eip/src/<n>/.
• Standardizes folder shape: one operation per file, predictable naming (kebab-case / snake_case / camelCase), and co-located tests.
• Keeps public APIs curated: index.ts defines the exported surface, so consumers only import what is meant to be public.
• Guides method and schema patterns: supports correct choice among Readable, Writable, Signable, and validation via Valibot schemas at boundaries.
• Ensures spec traceability: every implementation file starts with the canonical EIP link comment(s).

Quick Start

Add a new EIP folder at packages/eip/src/<n>/ following the prescribed file layout, then implement each operation with the required schema-first, parse-first pattern and co-located tests.