codememo-expert

To add a new feature to a Next.js and Expo monorepo, determine the correct app, package, data model, and authentication pattern by applying project-specific conventions for feature development, UI changes, and domain logic.

The best way to structure Convex mutations in a TypeScript monorepo is to follow project-specific conventions for domain logic and backend changes, ensuring data flows align with the overall repository architecture and design system rules.

Reviewing code across web, mobile, and backend layers in a monorepo involves applying comprehensive repository context to verify that implementation patterns, Convex mutations, and TypeScript packages adhere to project-specific engineering guidelines.

Yes, the CodeMemo architecture supports Payload CMS and Convex backend integration, providing a complete project context that spans web, mobile, backend, and CMS layers including data flows and technology stack conventions.

You need full repository context for modifying a monorepo codebase when performing feature development, debugging, UI updates, backend changes, code reviews, and system design decisions to avoid repeatedly rediscovering the architecture.

Modifying a monorepo without project-specific conventions leads to misaligned feature development, incorrect package usage, and inconsistent testing workflows across Next.js, Expo, and Convex layers due to a lack of architectural context.