docs

Find the LOVE20 contracts, functions, viewers, and cast call/send templates needed for a concrete operation. Use when asked how to launch a token, contribute, claim, stake, request unlock, withdraw staked assets, submit actions, vote, join, verify, mint rewards, burn for parent token, manage default group identity, activate or post to group chats, inspect state with viewer contracts, or reuse the existing LOVE20 cast scripts.

Explain LOVE20 core protocol mechanics and map them to the core contracts and whitepaper. Use when asked about fair launch, parent and child token rules, SL and ST staking, SL 解锁期 or unlock period, 申请解锁, 取回质押资产, governance rounds, action submission, voting, joining, random verification, reward minting, or how LOVE20 rules are implemented on-chain.

Implement LOVE20 extension or derivative protocol contracts, factories, tests, and integration wiring. Use when asked to build a new extension, scaffold a derivative protocol, add or modify a factory, write extension tests, wire ExtensionCenter registration, or carry an extension change through contract, script, and frontend handoff.

Explain and design LOVE20 extensions, extension factories, and whitelist-based reward flows. Use when asked how the extension framework works, how to build a new extension, how ExtensionCenter should be used, how LP or chain-group extensions behave, or how extension actions map back into LOVE20 rewards.

Trace LOVE20 frontend behavior to pages, components, hooks, ABIs, viewer contracts, and environment configuration. Use when asked how a LOVE20 UI action works, which contract a page calls, where data is aggregated in the frontend, how extension pages are registered, how default group identity is shown, or how wagmi hooks map to LOVE20 contracts.

Implement or modify LOVE20 frontend pages, components, hooks, ABIs, extension registration, and transaction flows. Use when asked to build a new LOVE20 UI feature, wire a new extension or derivative protocol into the dApp, add routes or hooks, update env-configured addresses, or carry a frontend change through read and write verification.

Wire LOVE20 changes across contract repos, periphery viewers, cast or log scripts, network address files, and frontend env or hook layers. Use when asked to carry a feature across multiple LOVE20 repos, align ABIs and addresses, integrate a new contract into viewers or scripts, reconcile end-to-end read and write paths, or make a local or public-test integration actually work.

Navigate LOVE20 documentation and related repositories across docs, core, periphery, script, extension, extension-lp, extension-group, group, group-chat, and interface. Use when asked what a LOVE20 concept means, how phase and round concepts should be interpreted, which repo or file is authoritative, how protocol terms map to code, where to start reading, or how to find the correct LOVE20 source quickly.

Frame LOVE20 requests into precise prompts and response contracts for protocol explanation, contract interaction, state inspection, troubleshooting, selector decoding, code review, and docs or skill updates. Use when a LOVE20 ask is underspecified, when you want a reusable prompt for another AI agent, or when a broad task should be split into smaller prompts with the right evidence requirements and companion skills.

Troubleshoot LOVE20 protocol, contract, extension, group, group-chat, and frontend failures by mapping a symptom to the fastest evidence sources and next checks. Use when a LOVE20 launch, contribute, claim, stake, submit, vote, join, verify, mint, extension registration, group mint, default group identity, group chat activation or posting, event sync, or frontend transaction flow does not behave as expected.

Decode LOVE20 function selectors, custom error selectors, event topics, and frontend error mappings across interface, script, core, periphery, extension, group, and group-chat repos. Use when asked what a 4-byte selector or topic means, which contract emitted an event, which custom error a revert corresponds to, how the frontend turns raw errors into Chinese messages, or how to trace ABI signatures back to LOVE20 code.

Inspect LOVE20 chain state, viewer reads, frontend query hooks, and indexed event history across core, periphery, interface, script, and group-chat repos. Use when asked where a token, round, action, account, default group identity, chat message, reward, or event timeline is read from, which contract or hook powers a page, how to query historical events, whether an address participated in an action, or why current state and indexed history disagree.

Plan and execute the minimum LOVE20 test, regression, deployment, and post-release verification matrix for core, extension, periphery, script, and frontend changes. Use when asked what to run before merging or deploying, how to validate a LOVE20 change end to end, how to prepare a release checklist, or how to sign off regressions after contract, frontend, or integration work.