Results for “proof”

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher quality software.

Prepare GPT-pro-ready proof planning or diagnosis bundles from a user's idea, packaging claims, sources, givens, and open questions for review without solving gaps locally.

Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher code quality.

Guides incremental code improvements, error-proofing through types and validation, and standardization to raise code quality and prevent defects.

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher quality and fewer defects.

Guide for continuous improvement, error proofing, and standardization in code and processes. Use when improving code quality, refactoring, or discussing process improvements.

Define a lightweight, disposable Proof of Life probe to test a risky hypothesis cheaply and surface harsh truths before building real product.

Select the right Proof of Life (PoL) probe type based on hypothesis, risk, and resources to match validation method to the real learning goal.

Bind content to live product proof and an accountable author voice.

Plan and execute rapid game prototypes to validate mechanics, test assumptions, and find the fun before committing to full production. Use when building playable proofs-of-concept. Also trigger for "prototype", "game jam", "proof of concept", "find the fun", "playable demo", or "rapid prototype".

Use only for developer-facing products; plan adoption loops, examples, templates, community, and proof artifacts

Perform an exhaustive, multi-pass proofread and copy-edit of an applied-microeconomics manuscript to top-economics-journal standards (AER, QJE, Econometrica, ReStud), checking prose, equations, table notes, footnotes, and citations for avoidable errors. Use before submitting or circulating an empirical economics paper.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness

Verify code changes work by running them. Proves through execution, not just inspection.

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Runs a hypothesis-driven debugging workflow that reproduces failures, forms discriminating tests, proves root cause via toggle, and delivers a fix, regression test, and postmortem.

Unified math capabilities - computation, solving, and explanation. I route to the right tool.

Runs throwaway experiments to validate feasibility before building, producing a verdict with evidence.

Verify that a change really works before you claim completion

Screenshot-obsessed, fantasy-allergic QA specialist - Default to finding 3-5 issues, requires visual proof for everything

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use to prove that a support process, policy or script change actually took effect — when, for whom, and whether behaviour followed — rather than that it was approved. Trigger for "prove we made that change", "when did this policy actually change", "did the team adopt the new process", evidencing remediation, "we told everyone" claims, or a change that was signed off and never landed.

Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verification command and read its output before making any success claim.

Prove a feature works by delegating verification to an independent sub-agent that drives the real app, then open a pull request with the proof.

基于证据优先的仓库执行工作流，适用于ECC。当用户需要运行命令、检查仓库、调试CI失败或推送带有精确执行和验证证明的窄修复时使用。