AI Tooling
Purpose
Section titled “Purpose”AI tooling is part of the course method. Learners should use AI to accelerate reading, planning, debugging, testing, and review, while still making security and design decisions themselves.
Required AI Context
Section titled “Required AI Context”Before starting Ethereum-specific work, ask the AI assistant to read:
- ethskills SKILL.md
- Scaffold-ETH 2 llms-full.txt
- The current module page
- The current lab page
Recommended Prompt
Section titled “Recommended Prompt”You are helping me complete an Ethereum application developer lab.First read https://ethskills.com/SKILL.md and https://docs.scaffoldeth.io/llms-full.txt.Then use the current lab brief to produce:1. A step-by-step implementation plan2. Commands I need to run3. Files I need to edit4. Tests I should write5. Security risks I should check manuallyDo not ask for or store private keys, seed phrases, or real-wallet credentials.Module Mapping
Section titled “Module Mapping”| Module | AI Context to Prioritize |
|---|---|
| Module 0 | SKILL.md, Ship, Tools |
| Module 1 | Why Ethereum, Protocol, Gas, Wallets |
| Module 2 | Standards, Tools, Security |
| Module 3 | Ship, Tools, Orchestration, Scaffold-ETH 2 docs |
| Module 4 | L2s, Gas, Wallets, Security |
| Module 5 | Money Legos, Security, Ship |
What AI Should Help With
Section titled “What AI Should Help With”- Explaining unfamiliar Ethereum concepts
- Translating docs into actionable steps
- Drafting tests
- Debugging compiler and deployment errors
- Reviewing README structure
- Performing a first-pass security review
- Comparing implementation choices
What AI Must Not Handle Alone
Section titled “What AI Must Not Handle Alone”- Private keys, seed phrases, or production credentials
- Real asset movement
- Final contract permission design
- Final security sign-off
- Deployment to production networks
- Legal, regulatory, or financial claims
Required AI Development Note
Section titled “Required AI Development Note”Every learner should submit an AI-assisted development note with:
- Resources the AI was asked to read
- Prompts used
- Useful AI outputs
- Incorrect or unsafe AI outputs
- Human corrections
- Remaining risks that require manual judgment
Safety Checklist
Section titled “Safety Checklist”Before running AI-generated commands or code:
- Check that no private key or seed phrase is included.
- Check that the network is a testnet unless explicitly instructed otherwise.
- Read any contract that transfers tokens or ETH.
- Confirm who has owner or admin permissions.
- Run tests before deployment.
- Keep a record of what changed.