This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
These apply to every task, across both the Rust backend and this Next.js frontend.
Use sound design and engineering practice in both codebases. Prefer patterns already established here over inventing new ones.
Consider security before starting a task, not as a review afterwards. Octo is non-custodial and moves real money — treat the threat model as live, not theoretical.
Once a change is secure, make sure it scales and is easy to understand. Favour the version a new engineer can follow over the clever one.
On every task, look for gaps or vulnerabilities a malicious actor could exploit. If you find one, prevent it and report it — even when it falls outside the scope you were asked to work on.
One line of comment per block. No bloated code.