Dasemu
40631362b3
Establishes version control for the personal Logseq DB fork before starting the server-client architecture migration and domain features described in docs/agent-guide and the approved implementation plan. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
11 lines
1.1 KiB
Markdown
11 lines
1.1 KiB
Markdown
- Do not modify any files under `spec/` during development unless explicitly asked to modify the `.mli` files under `spec/`.
|
|
- Do not modify any dune file during development unless explicitly asked.
|
|
- If development is blocked because the `.mli` definitions under `spec/` are unclear or unreasonable, stop development immediately and report the specific spec issue, suggested changes, and rationale.
|
|
- This repository implements only the CLI portion. It does not include the db-worker-node server, and should use the existing cljs version of the db-worker-node server.
|
|
- MUST not use magic methods to cast types.
|
|
- Platform-specific code must only appear under `lib/platform/`.
|
|
- Only keep test cases related to business logic.
|
|
- Do not keep temporary tests added during refactoring, and do not keep test cases that assert internal implementation details.
|
|
- Before adding a new external JavaScript function, first check whether a corresponding implementation already exists in `melange.js` or `melange.node`. Avoid adding new externals whenever possible.
|
|
- MUST not disable compiler warnings
|