# Toronet Smart Contract Development

> Write, review, explain, and refactor Solidity smart contracts for ToroNet. Use when the user wants ToroNet-compatible contract code, contract architecture guidance, or a ToroNet-specific review of an existing contract.

- Skill: `toronet-guidl/toronet-smart-contract-development` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add toronet-guidl/toronet-smart-contract-development`
- Raw SKILL.md: https://api.skillmd.com/api/skills/toronet-guidl/toronet-smart-contract-development/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: toronet-guidl (https://skillmd.com/u/toronet-guidl)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/toronet-guidl/toronet-smart-contract-development

---


# toronet-smart-contract-development

## When to use

Use this skill when the user wants to:

- write a new smart contract for ToroNet
- adapt an existing Solidity contract for ToroNet
- get a ToroNet-specific review of a smart contract
- structure ownership or admin permissions for ToroNet contracts
- get a ToroNet-compatible Solidity example
- refactor a contract to match ToroNet conventions

Do not use this skill for frontend integration, SDK usage, or full deployment walkthroughs unless directly needed to complete a ToroNet smart contract task.

## Instructions

1. Treat ToroNet smart contract conventions as mandatory.
2. Ensure all ToroNet-targeted contract examples use Solidity `0.8.18` or below and inherit an `Ownable` trait.
3. When the user does not provide an ownership implementation, use the default ToroNet-compatible `Ownable` reference in `references/REFERENCE.md`.
4. Keep generated contracts practical, readable, and deployable, and clearly identify privileged functions and owner-only operations.
5. When reviewing a contract, check ToroNet compatibility before suggesting improvements.
6. When deployment is mentioned, briefly note that ToroNet contracts are commonly deployed through a web UI, the ToroNet SDK, or the `toronetdeploy` npm package, but keep the focus on contract development unless the user asks for deployment details.

## Default workflow

1. Identify whether the task is writing, reviewing, explaining, or refactoring a contract.
2. Check the Solidity version and adjust it to a ToroNet-compatible version if needed.
3. Check whether the contract inherits `Ownable`.
4. Add or adapt ownership controls where needed.
5. Produce the contract, review, explanation, or refactor, and briefly note any ToroNet-specific issues, assumptions, or deployment-readiness concerns.

## Checks

- Solidity version is `0.8.18` or lower
- contract inherits `Ownable`
- owner-only functions are clearly restricted
- admin flow is understandable
- contract structure is realistic for ToroNet deployment
- code avoids unnecessary complexity for the stated use case

See [the reference guide](references/REFERENCE.md) for ToroNet conventions, the default `Ownable` implementation, and deployment notes.