analyzing-ethereum-sma…
Perform static and symbolic analysis of Solidity smart contracts using
Use when anticipating how an expert Annals of Mathematics referee will verify a proof — stress-testing the argument for gaps, checking external dependencies, and pre-empting the questions a careful reader will ask. Hardens the manuscript before submission; does not write the
$ npx -y skills add tradecatlabs/vibe-coding-cn --skill anmath-referee-strategy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/anmath-referee-strategyContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when anticipating how an expert Annals of Mathematics referee will verify a proof — stress-testing the argument for gaps, checking external dependencies, and pre-empting the questions a careful reader will ask. Hardens the manuscript before submission; does not write the
name: anmath-referee-strategy description: Use when anticipating how an expert Annals of Mathematics referee will verify a proof — stress-testing the argument for gaps, checking external dependencies, and pre-empting the questions a careful reader will ask. Hardens the manuscript before submission; does not write the rebuttal (anmath-revision).
Expect a referee who is an **expert and verifies proofs in detail**, often over a long period (a year or more is common). They do not skim; they reconstruct each step. Their implicit questions:
1. **Is it important enough?** Significance is judged again at the report stage. 2. **Is every step actually valid?** They will probe exactly the steps you find hardest. 3. **Do the external results say what you claim?** They will check the cited statement. 4. **Does the theorem match the proof?** Any over-claim is caught here. 5. **Is anything hidden behind "clearly"?** Softening words attract scrutiny, not less.
| Probe | What to do before they do | |-------|---------------------------| | Where is the crux? | Make sure it is fully spelled out and easy to locate | | Which step is weakest? | Strengthen or expand it; do not hope it is overlooked | | Every "clearly"/"standard" | Resolve or cite it (see anmath-writing-style) | | Every external theorem | Re-read the cited source; confirm hypotheses match your use | | Quantifiers / constants | Confirm order and dependence are stated and correct | | Special / boundary cases | Check the degenerate cases the main argument might miss | | Computer-assisted steps | Confirm code/data are archived and the claim is reproducible |
piece — this speeds a long review and reduces the chance of misreading.
and remove a common source of objections.
on it; reduce or remove such dependence where possible.
do not pack the list with close collaborators.
【Crux locatable & complete】yes / fix: ... 【Weakest step】... → strengthened / expanded 【External-citation re-check】hypotheses match use: yes / fix: ... 【Boundary cases】covered / add: ... 【Computer-assisted reproducible】n/a / yes 【Suggested referees】names (conflict-free); conflicts declared: ... 【Residual risks to flag to editor】... 【Next step】submit, then await report → anmath-revision
从想法到产品的 AI 结对编程工作流标准:Prompt + Skill + Context + Quality Gate + 工程闭环 <!-- 徽章区域 (BADGES) --> 本仓库的 AI 解读链接:zread.ai/tukuaiai/vibe-coding-cn 🧠 六条核心命题
Repo: tradecatlabs/vibe-coding-cn
Perform static and symbolic analysis of Solidity smart contracts using
Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines…
AI-powered tools for Web3 bug bounty automation. Use when you want to automate recon, run…
Complete reference for all 10 DeFi smart contract bug classes. Use this when hunting for…
Case study - role misconfiguration bug class applied to a yield aggregator protocol. Use as a…
Master grep command arsenal for Web3 smart contract auditing. Use when starting a new…