executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
account-abstractionComprehensive expertise in ERC-4337 account abstraction, smart contract wallets, paymasters, bundlers, and user operation handling. Covers social recovery, session keys, gas sponsorship, and wallet SDKs. Use when "account abstraction, ERC-4337, smart wallet, paymaster, bundler, user operation, gasless transaction, session keys, social recovery, smart accoun…
Independent GitHub snapshot · Automated classification · Original documentation governs
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.