AlexandrAI AGENTS.md
agents-md

AB Framework Mobile Harness Agent Guide

Project-specific AGENTS.md guidance for the AB Framework mobile harness role, generated Expo app shell, typed API core, feature modules, and verification gates.

AGENTS.md

Guidance for coding agents working on the AB Framework mobile harness role.

Project Overview

The mobile harness owns generated Expo React Native app structure, App.tsx orchestration, navigation, API client, typed copy, feature modules, reusable components, and framework verification for generated <app>-mobile output.

Project Map

  • .claude/mobile/AGENT.md defines the mobile role.
  • .claude/mobile/README.md documents generated mobile expectations.
  • .claude/mobile/skeleton/App.tsx is the app shell seed.
  • .claude/agents/ab-mobile-framework-agent.md owns mobile generation.
  • docs/source-architecture.md explains generated repo boundaries.
  • .claude/scripts/verify-framework.mjs checks generated suite completeness.

Setup Commands

bashnode .claude/scripts/verify-framework.mjs
node .claude/scripts/lint-claude-harness.mjs

Change Rules For Agents

  • Keep App.tsx orchestration-only.
  • Keep network code centralized under src/api in generated mobile repos.
  • Keep feature logic under src/features/.
  • Do not import server, admin, or web runtime source.
  • Keep copy typed and localization-ready.
  • Preserve reusable component boundaries.
  • Verify with the framework gate before reporting complete.

Verification

bashnode .claude/scripts/verify-framework.mjs

Inspect generated <app>-mobile output after skeleton or agent prompt changes.

Security Notes

Mobile skeletons should not include real API secrets, tokens, private endpoints, or server-only credentials. Use environment placeholders and centralized client configuration.

PR Checklist

  • App.tsx remains small.
  • API calls stay centralized.
  • Feature modules stay isolated.
  • Framework verifier passes.