Conversation
Public API Changes✅ No public API changes detected. |
|
@enitrat I can already guess that this is bad. Am I correct in understanding the pnpm commands are basically worthless? Already plan to change/improve this. Do you have any specific tips, besides NOT putting in too much stuff? |
Coverage Report
File CoverageNo changed files found. |
This is Boris Cherny's claude.md, the aim is to provide guidelines on specific topics. For us a guideline would be the North star of the SDK so that claude sticks to it in documentation, naming conventions, etc... |
Replace reference manual (commands, directory listings, code style rules) with product vision, operation flow map, naming conventions, and design decisions that Claude cannot infer from config files. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
||
| Semantic-release automates versioning. Both packages are versioned in lockstep. `main` publishes to npm `latest`; `prerelease` branch publishes to npm `alpha`. CI gates: Vitest + Playwright must pass before publish. | ||
| - **TanStack `useQueries` wrapper is mandatory** in react-sdk. Never import `useQueries` directly from `@tanstack/react-query` — use the wrapper in `packages/react-sdk/src/utils/query.ts` which injects the custom `queryKeyHashFn`. An ast-grep rule enforces this. | ||
| - **Build order matters.** `@zama-fhe/sdk` must build before `@zama-fhe/react-sdk`. `pnpm build` handles this correctly. |
There was a problem hiding this comment.
I'd suspect that Claude could infer this information as @zama-fhe/sdk is a dependency of @zama-fhe/react-sdk
|
good reference to keep in mind: https://www.aihero.dev/a-complete-guide-to-agents-md |
3 participants
Summary
Initialise CLAUDE.md file
Scope
@zama-fhe/sdk@zama-fhe/react-sdk@zama-fhe/test-components@zama-fhe/test-nextjs@zama-fhe/test-viteValidation
N/A
Related
N/A
Demo (if possible)
N/A