1k-architecture

The OneKey monorepo architecture organizes code into apps/ and packages/ directories, using platform-specific file suffixes to separate web, mobile, and desktop components while maintaining strict import hierarchy rules to prevent circular dependencies.

Cross-package references in a monorepo are governed by strict import hierarchy rules that enforce workspace conventions, prevent circular dependencies, and maintain modular code structure across multi-platform components and shared interfaces.

To navigate cross-cutting concerns across web, mobile, and desktop packages, review the monorepo architecture overview to identify package relationships, code ownership boundaries, and import rules before planning feature work.

Platform-specific file suffixes in monorepo development are needed when implementing multi-platform components, ensuring platform-specific code remains isolated and architecture consistency checks pass across web, mobile, and desktop environments.

This monorepo architecture overview suits new developer onboarding by clarifying project structure, package relationships, and import hierarchy rules, enabling faster orientation with the repo layout and major packages before contributing code.

Strict dependency management matters for scalable monorepo contributions because it enforces workspace conventions and import hierarchy rules that avoid circular dependencies, maintain modularity, and support architecture-consistency checks across cross-package interfaces.