analyzing-ethereum-sma…
Perform static and symbolic analysis of Solidity smart contracts using
Use when laying out the proof strategy of a pure-mathematics manuscript for Annals of Mathematics — the architecture of the argument, the key lemmas and propositions, the novel technique, and where the difficulty lies. Designs and exposes the proof plan; does not check final
$ npx -y skills add tradecatlabs/vibe-coding-cn --skill anmath-methods --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/anmath-methodsContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when laying out the proof strategy of a pure-mathematics manuscript for Annals of Mathematics — the architecture of the argument, the key lemmas and propositions, the novel technique, and where the difficulty lies. Designs and exposes the proof plan; does not check final
name: anmath-methods description: Use when laying out the proof strategy of a pure-mathematics manuscript for Annals of Mathematics — the architecture of the argument, the key lemmas and propositions, the novel technique, and where the difficulty lies. Designs and exposes the proof plan; does not check final correctness line-by-line (see anmath-referee-strategy).
For an Annals paper, an expert non-specialist should be able to read a **proof overview** and understand *how* the theorem is proved before verifying *that* it is. The architecture is part of the contribution.
1. **Proof outline up front.** After stating the Main Theorem, give a paragraph or short section sketching the strategy: the main steps, the key lemma(s), and the crux. 2. **Decompose into named results.** Break the argument into Lemmas, Propositions, and intermediate Theorems, each stated precisely and proved before it is used. 3. **Isolate the new idea.** Name explicitly which step is the genuinely new technique and why prior approaches failed there. This is what makes the paper publishable. 4. **Locate the difficulty.** Tell the reader where the hard part is and why it is hard; do not let the crux pass disguised as routine.
| Symptom | Action | |---------|--------| | A 10-page proof with no internal structure | Extract Lemmas/Propositions with clear statements | | The same estimate reused three times | State it once as a Lemma and cite it | | A self-contained technical computation interrupting the flow | Push to an appendix (anmath-supplementary) | | Reliance on a deep external theorem | State it precisely with citation; do not paraphrase loosely | | The crux step stated as "a calculation shows" | Expand fully — this is exactly what referees check |
Proposition), so others can cite and reuse it — methods with reach justify Annals.
does not work and how the new idea circumvents the obstruction.
in your adaptation.
exact statement you use, not a vague version.
unavoidable, isolate the dependence and flag it explicitly.
【Proof strategy, one paragraph】... 【Key lemmas/propositions】L1: ...; P1: ...; ... 【The new idea (crux)】... 【Why the standard approach fails】... 【External results relied on】author (year), Thm X — exact statement used 【Steps to push to appendix】... → anmath-supplementary 【Next step】anmath-figures (exposition & structure)
从想法到产品的 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…