Skip to content

Commit f712f25

Browse files
committed
harden storage getStore for browser runtimes and filter null keys
1 parent 0e2460d commit f712f25

5 files changed

Lines changed: 1063 additions & 3 deletions

File tree

CLAUDE.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
1. Think Before Coding
2+
Don't assume. Don't hide confusion. Surface tradeoffs.
3+
4+
Before implementing:
5+
6+
State your assumptions explicitly. If uncertain, ask.
7+
If multiple interpretations exist, present them - don't pick silently.
8+
If a simpler approach exists, say so. Push back when warranted.
9+
If something is unclear, stop. Name what's confusing. Ask.
10+
2. Simplicity First
11+
Minimum code that solves the problem. Nothing speculative.
12+
13+
No features beyond what was asked.
14+
No abstractions for single-use code.
15+
No "flexibility" or "configurability" that wasn't requested.
16+
No error handling for impossible scenarios.
17+
If you write 200 lines and it could be 50, rewrite it.
18+
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
19+
20+
3. Surgical Changes
21+
Touch only what you must. Clean up only your own mess.
22+
23+
When editing existing code:
24+
25+
Don't "improve" adjacent code, comments, or formatting.
26+
Don't refactor things that aren't broken.
27+
Match existing style, even if you'd do it differently.
28+
If you notice unrelated dead code, mention it - don't delete it.
29+
When your changes create orphans:
30+
31+
Remove imports/variables/functions that YOUR changes made unused.
32+
Don't remove pre-existing dead code unless asked.
33+
The test: Every changed line should trace directly to the user's request.
34+
35+
4. Goal-Driven Execution
36+
Define success criteria. Loop until verified.
37+
38+
Transform tasks into verifiable goals:
39+
40+
"Add validation" → "Write tests for invalid inputs, then make them pass"
41+
"Fix the bug" → "Write a test that reproduces it, then make it pass"
42+
"Refactor X" → "Ensure tests pass before and after"
43+
For multi-step tasks, state a brief plan:
44+
45+
1. [Step] → verify: [check]
46+
2. [Step] → verify: [check]
47+
3. [Step] → verify: [check]
48+
Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
49+
50+
# env variables
51+
export EDV_AUTH_KEY=DOCKWALLET-TEST
52+
export EDV_URL=https://edv.truvera.io
53+
export PROOF_TEMPLATE_FOR_ANY_CREDENTIAL=61146961-e1b2-4c08-bbc9-2bc9fd815575
54+
export CERTS_API_KEY=eyJzY29wZXMiOlsidGVzdCIsImFsbCJdLCJzdWIiOiI3Iiwic2VsZWN0ZWRUZWFtSWQiOiI4IiwiY3JlYXRvcklkIjoiNyIsImlhdCI6MTY5ODg1MzI0MiwiZXhwIjo0Nzc4MTQ5MjQyfQ.njdeY1QzgBP9alG2wWjr_8tpEGnMpa2baEPVhtjKYiZTHYe_FnBKVu7jksk-eoIOYqD41MtOP9mjn9cG9Ure2A
55+
export TESTING_API_URL=https://api-staging.truvera.io
56+
57+
# nodejs version
58+
nvm use 24
59+
60+
# running integration tests
61+
npm run test:integration integration-tests/verification-flow/range-proofs.test.ts
62+
63+
# runing unit tests
64+
npm run test

0 commit comments

Comments
 (0)