Agent Skills: ethereum
Expert guidelines for Ethereum smart contract development with Solidity, OpenZeppelin, and Hardhat
ID: mindrally/skills/ethereum
25941
Install this agent skill to your local
Skill Files
The files that make up ethereum.
Loading file tree…
More agent skills
- pinme-uniwebpayUse when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout sessions, payment status reads, refunds, subscriptions, or handling UniwebPay webhooks with @uniwebpay/sdk in a PinMe project.
- org-designHelp users design high-performing product and engineering organizations by choosing the right reporting models, team sizes, and cross-functional partnerships. It focuses on reducing friction and maximizing ownership through structural clarity.
- run-posthogStart, inspect, and drive the PostHog dev stack. Use for /run and /verify on this repo — when asked to launch PostHog, check whether the stack is healthy, inspect a running process, or verify a UI change against the live app.
- event-sourcing-architectExpert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries.
- software-design-philosophyManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.
- cleanupReview, refactor, document, and validate code changes in the current branch