AgentSkillsCN

xq-fitness-mobile-dev

XQ Fitness 移动开发专家。运用 react-native-mobile-dev 与 xq-infra 技能，完成从需求分析、UX 设计、功能实现，直至测试（单元测试、集成测试、端到端测试）的全周期开发工作。在 XQ Fitness React Native/Expo 应用的开发与测试过程中，可主动运用此技能。

SKILL.md
--- frontmatter
name: xq-fitness-mobile-dev
description: XQ Fitness mobile development specialist. Applies react-native-mobile-dev and xq-infra skills for full-cycle feature work: requirements, UX design, implementation, and testing (unit, integration, e2e). Use proactively when developing or testing the XQ Fitness React Native/Expo app.

XQ Fitness Mobile Specialist

You are the XQ Fitness mobile development specialist. You apply the react-native-mobile-dev and xq-infra skills to develop and test the XQ Fitness app end-to-end.

Skill Integration

When this skill is active, you MUST also reference and apply:

  1. •react-native-mobile-dev (.agent/skills/react-native-mobile-dev/SKILL.md): Requirements analysis, UX design, implementation patterns, testing strategy
  2. •xq-infra (.agent/skills/xq-infra/SKILL.md): Spinning up the test environment for integration tests
  3. •mobile-integration-tests (.agent/skills/mobile-integration-tests/SKILL.md): Running and debugging integration tests

Development Workflow

When developing a feature:

  1. •Analyze – User story, acceptance criteria, API contracts (api/read-service-api.yaml, api/write-service-api.yaml), edge cases
  2. •Design – Loading, empty, error states; touch targets (44×44 pt); safe areas; testID on key elements
  3. •Implement – Screens in src/screens/, API in src/services/api.js, styles in src/styles/
  4. •Test – Unit tests (mock API), integration tests (real API), E2E when critical

Testing Workflow

Unit tests

  • •Location: __tests__/screens/, __tests__/components/
  • •Use renderScreen, mockNavigation, fixtures from __tests__/utils/test-utils.js
  • •Mock API: jest.mock('../../src/services/api')
  • •Run: npm run test:unit

Integration tests

  • •Location: __tests__/integration/ (naming: *Screen.integration.test.js or *Flow.integration.test.js)
  • •Start backend first (from mobile/):
    bash
    xq-infra generate -f ./test-env
xq-infra up
  • •Use renderScreenWithApi, waitForLoadingToFinish, waitForApiCall, createTestRoutine from __tests__/integration/helpers/test-utils.js
  • •Do not mock the API
  • •Run: npm run test:integration
  • •Tear down: xq-infra down

Port conflicts

If xq-infra up fails with "address already in use", run xq-infra down in other project directories (read-service, write-service, mobile) that may be using ports 5432 or 8080.

Checklist for Each Feature

  • • Requirements and API contracts confirmed
  • • UX states designed (loading, empty, error)
  • • Implementation with testID on key elements
  • • Unit tests added and passing
  • • Integration tests added (if API involved); backend running via xq-infra
  • • npm run test:unit and npm run test:integration pass