dimitar/fitaiProto
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

agents.md update

Browse Source
This commit is contained in:
echo 2025-11-09 15:15:42 +01:00
parent df668927f5
commit 771fcdf23b
1 changed files with 17 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
AGENTS.md
View File

@ -1,22 +1,24 @@
# AGENTS.md
## Project Overview
FitAI is a fitness management solution with admin web app and React Native mobile app for client management, payments, attendance tracking, and notifications.
FitAI fitness management solution: Next.js admin web app + Expo React Native mobile app for client management, payments, attendance tracking, and notifications. Monorepo with shared packages.
## Build/Test Commands
This project is in early prototype stage - no build system configured yet.
- When implementing: expect standard npm/yarn commands (npm run dev, npm run build, npm test)
- For single tests: use npm test -- --testNamePattern="test name" or npm test path/to/test.test.js
- Admin: npm run dev/build/lint/typecheck/test (from apps/admin)
- Mobile: npm run start/build/lint/typecheck/test (from apps/mobile)
- Database: npm run build/dev/typecheck/db:push/db:studio (from packages/database)
- Single test: npm test -- --testNamePattern="test name" or npm test path/to/test.test.js
## Code Style Guidelines
- Use TypeScript for type safety
- Follow React/React Native conventions
- Use camelCase for variables and functions
- Use PascalCase for components
- Import order: external libraries → internal modules → relative imports
- Implement proper error handling with try/catch blocks
- Use semantic HTML and accessible components
- Follow mobile-first responsive design principles
- Implement proper state management (Context API or Redux)
- Use environment variables for configuration
- Write comprehensive tests for critical functionality
- TypeScript strict mode, avoid `any` (warned by ESLint)
- React/React Native conventions with functional components
- camelCase for variables/functions, PascalCase for components
- Import order: external → internal (@fitai/\*) → relative imports
- Error handling with try/catch, use React Query for API errors
- ESLint enforced: no-unused-vars, prefer-const, no-var
- Use Zod for validation, React Hook Form for forms
- Database: Drizzle ORM with SQLite, use shared schemas
- Testing: Jest + Testing Library, write tests for critical functionality