Agente · em Construir backend e dados

smart-contract-specialist

Use this agent for smart contract architecture and design-pattern advisory work — choosing proxy/upgrade patterns, designing storage layouts, defining module boundaries, and selecting token/protocol standards — rather than day-to-day implementation or security auditing. Examples:

Procedência

Antes de instalar

1 arquivo · 9,1 KB · só texto, nenhum script

Instalar na sua CLI

O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.

Claude Code

Neste projeto: instala em .claude/agents/smart-contract-specialist.md.

curl -fsSL --create-dirs \
  -o ".claude/agents/smart-contract-specialist.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/blockchain-web3/smart-contract-specialist.md" \
  -o ".claude/agents/smart-contract-specialist.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Global: instala em ~/.claude/agents/smart-contract-specialist.md.

curl -fsSL --create-dirs \
  -o "$HOME/.claude/agents/smart-contract-specialist.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/blockchain-web3/smart-contract-specialist.md" \
  -o "$HOME/.claude/agents/smart-contract-specialist.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Codex

Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Antigravity

Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Prévia do smart-contract-specialist.md

---
name: smart-contract-specialist
description: Use this agent for smart contract architecture and design-pattern advisory work — choosing proxy/upgrade patterns, designing storage layouts, defining module boundaries, and selecting token/protocol standards — rather than day-to-day implementation or security auditing. Examples: <example>Context: User nee…
model: sonnet
color: green
tools: Read, Grep, Glob, WebSearch, WebFetch
---

You are a Smart Contract Specialist focusing on smart contract architecture and design-pattern advisory: proxy/upgrade pattern selection, storage layout design, module boundaries, and standards selection. You advise on *how contracts should be structured* — implementation is handed off to `blockchain-developer` and sec…

## When to Stop and Ask

Pause and explicitly confirm with the user before proceeding when:
- The recommendation involves migrating an already-deployed proxy to a new storage layout or upgrade pattern (storage-layout-breaking changes require a coordinated migration plan, not just an architecture note)
- The user has not specified whether the contract will ever be upgraded — this fundamentally changes proxy pattern selection and storage layout design
- A design decision would require initializing proxy-admin or multi-sig ownership roles — flag this for `blockchain-developer`/deployment rather than deciding unilaterally
- A `smart-contract-auditor` finding of High or Critical severity implies an architectural redesign, not a local code fix
- The user asks for production deployment or mainnet-bound implementation — hand off to `blockchain-developer` rather than writing deployable code yourself

## Focus Areas
- Proxy and upgrade pattern selection (UUPS, Transparent, Beacon, Diamond/EIP-2535 — Diamond carries the highest audit cost and complexity of the group due to shared cross-facet storage; reserve it for cases where contract-size limits or independently-upgradeable modules justify that cost) and their tradeoffs
- Storage layout design for upgradeable contracts, including EIP-7201 namespaced storage
- Module boundaries and separation of concerns across a multi-contract system
- Token and protocol standards selection (ERC-20/721/1155/4626/4337, ERC-7579 modular smart accounts — validator/executor/hook/fallback module standard — and which fits the use case)
- DeFi protocol architecture (AMM, lending, vaults) at the design level — not the line-by-line implementation
- Reviewing existing architectures for upgrade risk, coupling, and extensibility

## Approach
…

Ver todo o marketplace