Hire an AI Solidity smart contract developer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A list of ways the contract could be attacked, ranked by what is at stake
• A rule list of what must always be true, such as balances adding up
• A contract layout with interfaces, access roles and the upgrade pattern
• Gas notes naming the changes worth making
• A test plan with unit, random-input and upgrade tests, and the static checks to run
• A deployment checklist and audit-prep notes

How it does the job well

• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.
• Treat input from users, files and networks as untrusted. Validate it at the boundary.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You are planning an ERC-20 token, an NFT, a vault or a staking contract and want the risks listed first.

• Threat list. Each way the contract could be attacked, what is at stake and the planned defence.
• Rules that must always hold. Plain statements that must stay true after every action, each with how to test it.
• Contract layout. The parts, their jobs, who can call them and the upgrade pattern.
• Gas notes. Storage and call changes that cut cost, with the trade-off for each.
• Test plan. Unit, random-input, rule and upgrade tests, plus the static checks to run.
• Deployment checklist. The steps, who does each and what to verify, from testnet to launch.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Kent Beck would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Model the threats. It lists who holds power, what you trust outside the contract, and how flash loans, price manipulation or key theft could hurt you.
• State the rules that must hold. It writes down the facts that must stay true after every action, which become tests later.
• Plan the layout. It sets interfaces, roles, events and the upgrade pattern, with a storage layout that survives upgrades.
• Plan the gas savings. It names storage, call and data choices that cut cost, and skips tricks the compiler already does.
• Plan the tests. It lists unit tests, random-input tests, rule tests, upgrade tests and static analysis.
• Prepare for audit. It lists the deployment steps and the notes an auditor needs, with trust assumptions and known risks.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-solidity-smart-contract-engineer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-solidity-smart-contract-engineer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• What the contract must do, in plain words
• Which chain or network it will run on, such as Ethereum or an L2
• The token standard, if any, such as ERC-20 or ERC-721
• Who holds admin power, and any outside contracts or price feeds you trust
• Your threat worries, such as theft, rug pulls or price manipulation (optional)
• Your existing contract code, if you have any (optional)

Helpful context (optional)

• The exact tokens and chains involved, so risks match your real setup.
• A short list of what each role, such as admin or user, may do.

Tools and access

• Claude, ChatGPT or Gemini: A chat can write the plan and outlines. Run Foundry, Slither and Mythril on your own computer to check them.

Functions and deliverables

• Solidity smart contract developer: Plan a safer Solidity smart contract, with a threat list, contract layout, gas notes, a test plan and a checklist to run before an audit.
  • A list of ways the contract could be attacked, ranked by what is at stake
  • A rule list of what must always be true, such as balances adding up
  • A contract layout with interfaces, access roles and the upgrade pattern
  • Gas notes naming the changes worth making
  • A test plan with unit, random-input and upgrade tests, and the static checks to run
  • A deployment checklist and audit-prep notes
  Source: Michael Sitarzewski and Agency Agents contributors.
• Software developer from specifications: Give it a spec and tickets. Get the work built in code, tested and reviewed.
  • One integration branch with the full spec built
  • Tests for each ticket
  • Tickets closed in your tracker
  • A code review of the result
  • A draft pull request (optional)
  Source: Matt Pocock.
• Test list writer: Write a test list before you change software, a form or a process. Get cases to check, smallest first, with the first one marked.
  • The change in one line
  • A list of cases, each describing behaviour and not how to build it
  • The order to work through them, smallest first
  • The one case to turn into a real test now
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.
• Kent Beck: Plan a software change using Kent Beck’s recorded approach. List the cases, take small steps and keep code tidying separate from new behaviour.
  • Your problem worked on the way Kent Beck would: their questions, their method, their push-back
  • The answer or the work, in Kent Beck's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You are planning an ERC-20 token, an NFT, a vault or a staking contract and want the risks listed first.
• You must choose between upgrade patterns, such as UUPS or transparent proxy.
• Your gas costs are high and you want to know which storage and call patterns to change.
• You are about to hire an auditor and want your tests and notes ready, so the audit is faster.

Limits to check before starting

• You have a deployed contract and need it reviewed for flaws. Use the Blockchain security reviewer.
• You want to know whether to buy, sell or launch a token as an investment. This agent plans code, not money decisions.
• You need a general web or backend design. Use the Backend Architect agent or the Software architect.
• You need a threat review of a non-blockchain app. Use the Application security reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then references/source-agent.md.
• Describe what the contract does, the chain, the token standard and who holds admin power. Paste any existing Solidity code.
• Say "Write the contract plan. Ask me once if anything is missing. Do not tell me it is safe."
• Read the threat list first. Add any risk it missed, then check the must-always-be-true rules against your own design.
• Run the compile, test and static checks it lists on your own computer, with tools such as Foundry, Slither and Mythril. The agent cannot run them.
• Test on a testnet first. Before real money, get a professional security audit.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-solidity-smart-contract-engineer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.