skills.rest
niconiahi
niconiahiCOMMUNITY
Explore all skills by this author →
GitHub

eip

Create Ethereum Improvement Proposal implementations under packages/eip/src with Valibot schemas.

1|Updated Jul 22, 2025
Search Tags:#typescript#ethereum#valibot#wallet integration#eip implementation#json-rpc methods
One-click install
npx skills add https://github.com/niconiahi/ethernauta --skill eip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eip
Source: https://github.com/niconiahi/ethernauta/tree/main/skills/eip
Command: npx skills add https://github.com/niconiahi/ethernauta --skill eip

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about eip

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a new Ethereum EIP implementation in a TypeScript monorepo?▼

EIP implementations must live under packages/eip/src/<n>/ with one operation per file, co-located tests, and an index.ts defining the public API surface.

What is the correct way to validate JSON-RPC method parameters for an EIP?▼

Validate JSON-RPC method parameters at boundaries using Valibot schemas, applying a schema-first, parse-first pattern to ensure type safety before executing operations.

How do I organize EIP helper functions for dapp and wallet interoperability?▼

Organize EIP helpers as curried operation functions categorized by Readable, Writable, or Signable types to standardize dapp and wallet interoperability workflows.

Does an EIP implementation require links to the original specification?▼

Yes, every implementation file must start with canonical EIP link comments to ensure strict spec traceability back to the original Ethereum Improvement Proposal document.

Can I export multiple operations from a single file when adding EIP-specific wrappers?▼

No, you must maintain one-operation-per-file granularity with predictable kebab-case or camelCase naming, curating the public surface exclusively through index.ts.

What are the limitations of using a strict folder structure for EIP implementations?▼

This strict folder structure does not accommodate ad-hoc file placement; all EIP-specific helpers, schemas, and wrappers are mandatorily owned under packages/eip/src/<n>/.

Related Skills

Explore More Software Engineering Skills→
niconiahiniconiahi
1

no-violations

Enforce TypeScript and Valibot boundary validation rules in the ethernauta monorepo.

Community
Advanced
hairyfhairyf
4

starknet

Access Starknet JSON-RPC and Wallet API specifications for node interaction.

Community
Intermediate
niconiahiniconiahi
1

core

Standardize Valibot schemas for Ethereum base primitive values.

Community
Basic
hamzashakoor119hamzashakoor119

spec-driven-development

Enforce spec-driven development workflows from requirements through code generation and review.

Community
Advanced