This document maps features in this repository to their source specifications in the specs repository.
Spec Version: v1.1-specs
Last Updated: 2025-12-06
- When implementing a feature, find it in the table below
- Click the spec link to view the authoritative specification
- Use line number references to load only relevant sections
- Follow the spec exactly for API contracts, schemas, and behaviors
-
- Complete app architecture (entire file - ~2500 lines)
- Project structure (lines 100-300)
- Feature specifications (lines 300-1800)
- UI/UX guidelines (lines 1800-2200)
- Performance optimization (lines 2200-2400)
-
- REST endpoints for mobile (lines 80-1200)
- Authentication (lines 120-280)
- Dashboard metrics (lines 500-750)
-
- Queries for dashboard (lines 400-600)
- Real-time subscriptions (lines 800-900)
- Wireframes & UX Flow
- Mobile owner dashboard (lines 400-800)
- Onboarding flow (lines 50-150)
- Sprint 1 Plan
- Mobile app tasks (Week 4-6)
- Communication Language Guidelines
- Glossary
- Vietnamese/English term translations
- Standard terminology
- Vietnam Market Strategy
- Mobile-first requirements
- Payment integrations (MoMo, ZaloPay, VNPay)
- Social platform integrations (Zalo, Facebook)
When the specs repository releases a new version:
- Review SPEC_CHANGELOG.md
- Identify breaking changes affecting this repository
- Update this file to reference new spec version
- Implement required changes
- Update repository version and tag release
AI assistants should:
- Load specs on-demand using the links above
- Use line number ranges to minimize context
- Reference this spec version consistently
- Follow AI Context Guide
Example:
semantic_search(
repo: "https://github.com/localstore-platform/specs",
query: "OTP authentication endpoint"
)
Then read specific sections:
read_file(
"architecture/api-specification.md",
lines: 150-280
)