house-conventions

To enforce studio development conventions, load the applicable House Knowledge Base packs for iOS, Android, and stack choices before implementation or specification work begins. This ensures mobile development outputs align with established studio patterns.

Align monetization and analytics implementation by loading the relevant house conventions alongside project team rosters before coding. This applies studio patterns to mobile paywalls or tracking events while respecting project-specific overrides.

You need to load house conventions for your mobile release workflow before writing any code change, specification, or store asset. This prevents inconsistent release practices by applying established standards to git workflows and store operations upfront.

Yes, you can override house conventions by checking the project team roster and project documentation. The system respects project-specific capabilities and roles, recording any intentional deviations from studio standards in daily fragments for later review.

Track divergences from mobile architecture standards by recording conflicts and reusable discoveries in daily fragments. This monitors intentional project-specific deviations from the house knowledge base for later review and continuous improvement.

Yes, the house conventions system works with both iOS and Android monetization features by identifying the relevant knowledge packs for each platform. It ensures paywall implementations match studio patterns while applying project-aware guidance.