You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
- Implemented 6 microservices following Domain Driven Design principles - Game Session Service: session management, scoring, state transitions - Question Bank Service: CRUD operations, fuzzy answer matching - User Service: player profiles, statistics, role management - Leaderboard Service: rankings, competitions, tie handling - Admin Service: role-based access control, audit logging - Gateway Service: authentication, rate limiting, proxying - Created shared packages for common types, errors, events, valueobjects - Added comprehensive business rules (30-min sessions, 3 attempts per question) - Implemented clean architecture with aggregates, value objects, domain services - Built sophisticated scoring system (2 points no hint, 1 with hint) - Added fuzzy answer matching with 85% similarity threshold using Levenshtein distance - Created event-driven patterns for inter-service communication - Implemented circuit breaker patterns and health checking in gateway - Added comprehensive validation and error handling across all services 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
4 months ago | |
|---|---|---|
| backend | 4 months ago | |
| docs | 4 months ago | |
| CLAUDE.md | 4 months ago | |
| README.md | 4 months ago | |
README.md
Know Foolery
Overview
Know Foolery is a quiz game inspired by the French game "Déconnaissance" (https://escaleajeux.fr/jeu/decon.0.1). It's a web-based quiz platform with plans for cross-platform expansion to mobile and desktop applications.
Game Concept
Core Gameplay
- Objective: Players answer randomly selected questions to score points
- Question Format: Each question belongs to a theme, displayed above the question
- Scoring System:
- 2 points for correct answer without hint
- 1 point for correct answer with hint
- 0 points for incorrect answer or timeout
- Attempts: Players have exactly 3 attempts per question
- Time Limit: Each game session is limited to 30 minutes maximum
- Hints: Players can request one hint per question, but this reduces their score
Player Experience
- Registration: Players must enter their name before starting a game
- Session Management: Game tracks progress, attempts, and time remaining
- Leaderboard: Display top 10 scores accessible to all players
- Themes: Questions are categorized by themes (Geography, History, Science, etc.)
Documentation
Detailed requirements
Architecture
Guidelines
Future Enhancements
Planned Features
- Question Categories: Filter questions by subject
- Difficulty Progression: Adaptive difficulty based on performance
- Multiplayer Mode: Real-time competition between players
- Daily Challenges: Special themed question sets
- Achievement System: Badges and milestones
- Question Contributions: Player-submitted questions
Scoring Enhancements
- Time Bonus: Extra points for quick correct answers
- Streak Bonus: Consecutive correct answers bonus
- Difficulty Multiplier: Higher points for harder questions
- Perfect Game Bonus: Bonus for 100% correct rate
Success Metrics
User Engagement
- Daily Active Users: Track player engagement
- Session Duration: Average time spent playing
- Question Accuracy: Player success rates by theme
- Hint Usage: Frequency and effectiveness of hints
Technical Performance
- Response Times: API and database performance metrics
- Error Rates: Application stability and reliability
- Uptime: System availability and reliability
- Security Events: Monitoring for security incidents
Business Metrics
- Player Retention: User return rates and engagement
- Content Quality: Question difficulty and engagement
- Platform Usage: Cross-platform adoption rates
- Admin Efficiency: Content management effectiveness
Project Roadmap
Phase 1: Core Platform (Weeks 1-6)
- Basic web application with core game mechanics
- Essential microservices and database setup
- Admin panel for question management
Phase 2: Enhanced Features (Weeks 7-12)
- Complete security implementation
- Comprehensive observability and monitoring
- Production-ready deployment
Phase 3: Mobile Expansion (Weeks 13-18)
- React Native mobile applications
- Cross-platform component optimization
- Mobile app store deployment
Phase 4: Advanced Features (Weeks 19-24)
- Desktop applications
- Advanced analytics and reporting
- Enhanced security and compliance features