add-exploration

Design and implement interactive Ethereum protocol explorations with canonical data, widgets, and tests.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/feelyourprotocol/website --skill add-exploration-feelyourprotocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-exploration
Source: https://github.com/feelyourprotocol/website/tree/main/.cursor/skills/add-exploration
Command: npx skills add https://github.com/feelyourprotocol/website --skill add-exploration-feelyourprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a new interactive exploration for an Ethereum protocol change (EIP) involves many coordinated steps — UX design, canonical metadata, widget implementation, tests, registry wiring, cover art, and home-page placement — that are easy to get wrong or ship inconsistently. This Skill turns that into a single executable playbook with explicit gates and invariants. ## Core Features & Use Cases - End-to-end exploration build: Creates canonical.ts, info.ts, examples.ts, MyC.vue, and config files under src/explorations/<id>/, following the signed-off briefing from the brief-protocol-change phase. - Design discipline: Enforces a capture statement, first action, play loop, form-factor pass (mobile/tablet/desktop), and cross-exploration UI reuse checks before any files are created. - Test-first workflow: Requires Vitest logic and Vue mount tests, a Cypress e2eCatalog row, and finish gates (npm run lf:ci, npm run type-check, targeted vitest runs). - Use Case: After a human approves a briefing for EIP-8024, run this Skill to design the widget, copy the closest reference exploration, implement and test it, register it in REGISTRY.ts, prepend it to the home Latest list, and generate cover art — all in one phase. ## Quick Start Ask the agent to run the add-exploration phase for the signed-off EIP briefing, implementing the exploration widget, tests, registry entry, and cover art.

Frequently Asked Questions about add-exploration

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

FAQPage Schema
How do I add a new EIP exploration to the Feel Your Protocol website?▼

Create a folder under src/explorations/<id>/ with canonical.ts, info.ts, examples.ts, and MyC.vue, copying the closest reference exploration by change nature. Then register it in REGISTRY.ts, add an e2eCatalog row, prepend the id to FEATURED_EXPLORATION_IDS, and generate cover art.

What tests are required when adding an exploration?▼

Write Vitest specs covering metadata, CANONICAL, examples, execution helpers including beyond-edge inputs, and Vue mounts of the widget. Add one row to e2eCatalog.ts so the Cypress visit-all loop picks up the route, and run lf:ci, type-check, and targeted vitest as finish gates.

When should I create a new shared E-Component versus reusing one?▼

Prefer existing E-Components with config, slots, or local companions first. Only create a new shared E-Component when briefing or design identifies a reusable logic and UX structure, via a focused sub-round with typed config, tests, and a catalogue row.

Can I add a new runtime dependency while building an exploration?▼

No. A new runtime dependency is an exception gate that requires an explicit human request. The playbook instructs you to stop and ask rather than improvise past it, and to prefer existing package.json entries.

What is the difference between a UIC extraction and a new E-Component?▼

A UIC extraction moves a duplicated chrome control, like a toggle or run button, into src/eComponents/ui/ with tests, and is required in-scope work. A new E-Component is a reusable logic-plus-UX structure that needs a dedicated sub-round or human approval.