design-web3

Guide Web3 system design for blockchain architecture and smart contract patterns.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/kunallimaye/lib-agents --skill design-web3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-web3
Source: https://github.com/kunallimaye/lib-agents/tree/main/skills/design-web3
Command: npx skills add https://github.com/kunallimaye/lib-agents --skill design-web3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of designing blockchain-based systems, providing guidance on architectural decisions, smart contract patterns, and Web3-specific constraints.

Core Features & Use Cases

  • On-chain/Off-chain Decision Framework: Helps determine the optimal placement of data and logic.
  • Smart Contract Patterns: Documents common and efficient smart contract architectures.
  • Gas Optimization: Provides design-level strategies to minimize transaction costs.
  • Use Case: When architecting a new decentralized application (dApp), use this Skill to decide which components should live on-chain versus off-chain and select the most appropriate smart contract upgrade pattern.

Quick Start

Use the design-web3 skill to get a decision framework for on-chain vs off-chain data placement.

Frequently Asked Questions about design-web3

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between on-chain vs off-chain data placement for a Web3 architecture?

To decide on-chain vs off-chain data placement, use a Web3 decision framework that evaluates decentralization requirements, gas costs, and smart contract logic constraints to determine optimal component placement.

What are the best smart contract patterns for designing decentralized applications?

The best smart contract patterns for dApps include documented architectures and upgrade patterns that optimize gas efficiency and address blockchain constraints like finality models and cross-chain communication.

How do I optimize gas costs when translating traditional system design to blockchain architecture?

Gas optimization in blockchain architecture is achieved through design-level strategies that minimize transaction costs by carefully translating traditional system design concepts into efficient smart contract logic.

Can I use standard system design principles for Web3 decentralization and cross-chain communication?

Standard system design principles require adaptation for Web3 decentralization because blockchain constraints affect finality models and cross-chain communication, necessitating specialized architectural decisions for smart contracts.

When should I not put application logic on-chain in a blockchain system?

You should not put application logic on-chain when the Web3 decision framework indicates that gas costs, finality models, or cross-chain communication constraints outweigh the benefits of decentralization for that specific component.