Cyptopimpinainteazy
Cyptopimpinainteazy / 00-x3-core-rules
Establishes the foundational operating law for all coding sessions. Every agent must follow these rules before, during, and after producing code. - Inspect actual source files, not just markdown docs, before making claims.
Cyptopimpinainteazy / 01-proof-before-claim
No completion claim is valid without proof from actual source, tests, wiring, and command output. - Before saying anything is "done", run the strongest proof command available.
Cyptopimpinainteazy / 02-no-fake-completion
Prevent agents from using stubs, mocks, no-ops, or placeholder logic and calling them "implemented." - When you write a function body, it must contain real logic, not a stub.
Cyptopimpinainteazy / 03-production-code-only
All code merged into main must be production-quality. No demo paths, mock backends, hardcoded test addresses, or in-memory-only persistence should be shipped to production. - Prefer production-quality implementations over demo/mock versions.
Cyptopimpinainteazy / 07-cross-vm-atomic-rules
Cross-VM operations (EVM, SVM, BTC, CosmWasm, X3VM) must be atomic or have proven rollback. Partial execution across chains is an invariant violation. - Every cross-chain transfer must have a timeout and refund path.
Cyptopimpinainteazy / 08-status-report-required
Every response must communicate actual completion status with an honest status bar. No hiding behind vague language. - Include a status bar with 10-block visual bars for Overall, Code, Tests, Wiring, Docs, and Proof.
Cyptopimpinainteazy / 09-next-10-tasks-required
Every completion report must include exactly 10 concrete next tasks. This prevents agents from abandoning work with no clear path forward. - List exactly 10 tasks, numbered 1 through 10.
Cyptopimpinainteazy / 04-runtime-wiring-required
A file existing in the repo does not mean it is wired into the runtime. Code must be reachable from the actual execution path. - Before claiming a module/feature is "wired", trace it from the entry point (main.rs, lib.rs, CLI, API handler, pallet construct_runtime!).
Cyptopimpinainteazy / 06-security-rollback-required
Every production feature must consider security, rollback, replay, and failure paths before being called complete. - Auth checks must be real, not `return Ok(())` pass-throughs.
Cyptopimpinainteazy / 05-tests-are-sacred
Tests are the proof mechanism. Modifying tests to hide code failures is sabotage. Failing tests signal real problems. - Run the full test suite for the changed area, not just the file you touched.