build-on-base

Base Development

Complete playbook for building on Base L2 — network setup, smart contracts, wallet auth, payments, developer tool attribution, and framework migrations.

Default Stack

Safety Guardrails

• Never commit private keys — use cast wallet import for Foundry keystores
• Never expose RPC API keys or CDP credentials client-side — proxy through backend
• Never skip server-side payment verification — always call getPaymentStatus() server-side and verify sender, amount, recipient; track processed tx IDs to prevent replay attacks
• Never send transactions without Builder Code attribution — silent data loss, no errors, no warnings
• Validate all user-provided shell inputs before constructing forge/cast commands (no spaces, semicolons, pipes)
• COOP headers for Base Account popups — use same-origin-allow-popups, not same-origin

Task Routing

Read the reference for your task:

Operating Procedure

1. Classify the task using the table above
2. Read the relevant reference before implementing
3. Confirm the framework with the user when multiple options exist (e.g., Privy vs wagmi for Builder Codes)
4. Implement with explicit chain ID, security requirements, and all required validations
5. Deliver diffs, install commands, and any manual steps (env vars, API key setup, wallet registration)

For Edge Cases and Latest API Changes

• AI-optimized docs: docs.base.org/llms.txt
• Base Account reference: docs.base.org/base-account
• Base chain docs: docs.base.org

Installation

npx skills add base/skills --skill build-on-base