Why: this guide is meant to enable the user to go from a raw AVS Idea to Design to Prototype (Code) in under 10 mins and learn more about how EigenLayer works along the way.
Who: this guide is written to serve a more technical developer audience that prefers Vibe Coding with popular AI / LLM tools such as Claude Code. Please note that EigenLayer is also working to release a web app experience to enable the same Idea to Prototype flow which will be released independently.
Pre-requisites:
- High level understanding of EigenLayer protocol, Autonomously Verifiable Services, and how building an AVS might add value to your Web3 project.
- Any high level idea you have for an AVS.
- Claude Code installed on your machine.
This stage is focused on taking your high level idea for building an AVS and turning it into a refined idea prompt. This will help reaffirm that your idea can be practically built as an AVS and result in a prompt that will be easy for the LLM to convert into a full AVS Design tech spec.
Steps to refine your idea:
-
Open a new terminal session.
-
`git clone` a local copy of the avs-prompt-library github repo and `cd` into the newly created folder.
-
Run the `claude` command to enter the Claude Code console. Run `init` command to initialize the repository for Claude Code.
-
Send the following prompt to Claude Code terminal to refine your idea and include any detail you wish to provide about your AVS.
Help me generate a refined idea prompt for my AVS idea using the attached prompts/stage1-idea-refinement-prompt.md file for guidance.
My idea for an AVS is: [insert your idea here].
Please note that you may also add any AVS design detail you may already have in mind, including the following context to your prompt:
- Project Overview: what is the name of your project and what value does it provide for its users?
- AVS Purpose: what benefit does the AVS provide to securing, validating or decentralizing your project.
- Name: what do you want to name your AVS? Or do you want the LLM to name it for you 😉?
- Operator Work: which core work or task will the Operators that comprise your AVS do?
- Validation: The work is validated through [todo - insert a description of your validation logic at a high level]
- Rewards: send Rewards distributions to Operators based on [todo]
- The LLM will respond with either feedback on how to improve your AVS idea or a “[avs-name]-refined-idea-prompt.md” for your review.
Steps to generate your Design Tech Spec:
-
Go to your open `claude` terminal session.
-
Send the following prompt to Claude Code terminal:
Help me generate a design tech spec for my using the attached [myavs-refined-idea-prompt.md] file and prompts/stage2-design-generation-prompt.md file for guidance.
-
The LLM will respond with a completed "[avs name]-design-tech-spec.md" file for your review.
Steps to generate your prototype AVS code:
-
Go to your open `claude` terminal session.
-
Send the following prompt to Claude Code terminal:
Help me generate a prototype implementation for my AVS using the attached [my-avs]-design-tech-spec.md file and prompts/stage3-prototype-code-generation-prompt.md file for guidance.
- Enhance our default prompts for each stage. The initial prompts are minimally viable and can easily be improved with more time and iteration.
- Design: add automated logo generation and architecture design to the design generation step.
- The Prototype code generation phase is focused on hello-world-avs as the target codebase. We will expand this to other examples and partner platforms in the future.
- Add a standard front end to the hello-world-avs repo to enable better demo’ing of the solution (pull from this example).