Lead-Studios/DeWordle

AI Summary: Implement a modal that appears after a DeWordle game concludes, displaying the definition, usage example, part of speech, and pronunciation of the guessed word. This will involve triggering the modal on game end, fetching word data from an external API, and potentially adding audio playback functionality. Stretch goals include animating the modal and adding a 'Did you know?' section with related words.

AI Summary: Develop a game replay viewer for the DeWordle game, allowing users to review past game attempts. This involves creating a UI to display guess history, including tiles and evaluations, with navigation controls. Stretch goals include adding auto-play and shareable replay links.

AI Summary: Implement a real-time countdown timer (hh:mm:ss) showing the time remaining until the next daily Wordle puzzle is available. The timer should disable daily play after completion and synchronize with server time to prevent manipulation. A stretch goal includes adding a tooltip or modal explaining daily challenge rules.

AI Summary: Develop a personal stats dashboard for the DeWordle game, displaying metrics like win rate, streaks, average attempts, and total games played. This involves creating a user interface, fetching player statistics via a backend API, and potentially animating the data presentation. Stretch goals include showing personal bests and integrating a global ranking.

AI Summary: Implement a user interface allowing players to select a difficulty level (e.g., Hard Mode with stricter rules) for the DeWordle game, persisting their choice, and adjusting game logic accordingly. Stretch goals include difficulty-based scoring and warnings for rule violations.

AI Summary: Implement an offline mode for the DeWordle game, allowing users to play with cached words and locally stored results. This involves detecting offline status, storing a small number of words locally, enabling offline guessing and result evaluation, and optionally syncing the session upon reconnection and warning users about offline limitations.

AI Summary: Implement a visually appealing animation system for a decentralized Wordle game built on StarkNet. This involves animating tile flips, applying color reveals with a delay, shaking rows for invalid guesses, and ensuring smooth performance across devices. Optional improvements include using a dedicated animation library and making animations customizable.

AI Summary: Develop a custom on-screen keyboard for a decentralized Wordle game built on StarkNet. The keyboard should visually represent user guesses by changing key colors based on the guess result and include animation for key presses. Stretch goals include haptic feedback and theming options.

AI Summary: Implement a multiplayer mode for the DeWordle game, allowing players to invite friends to play the same word simultaneously. This initial phase focuses on creating an invite screen, generating unique room codes/links, and enabling players to join existing rooms and synchronize the word to be guessed. Later phases will add real-time updates and player identification.

AI Summary: Implement accessibility features in the DeWordle game, including screen reader compatibility for buttons and tiles, font scaling for low vision users, ARIA tags (or accessibilityLabels for React Native), and optionally, a high-contrast mode toggle. This ensures the game is playable by users with visual impairments.

AI Summary: Implement global state management in a React application using Context API for authentication and Zustand/Jotai for game session data. This involves creating context providers, state management logic, and integrating with backend APIs for authentication and game interactions (login, signup, session management, guess submission).

AI Summary: Build a landing page for the DeWordle game that greets users (showing their username if logged in) and provides options to sign in or browse as a guest. This involves creating a React component (`LandingScreen.tsx`), integrating with an existing authentication context (`AuthContext`), and conditionally rendering content based on user login status.

AI Summary: Implement backend validation to prevent further guesses on a Wordle game session after it's completed (won or lost). This involves checking the game's status before processing a guess request and returning a 403 Forbidden error if the game is already over.

AI Summary: Implement user authentication for a decentralized Wordle game built on StarkNet. This involves creating sign-in and sign-up screens, integrating with backend API endpoints for user registration and login, and managing authentication state using a React context API. The solution should persist session data using AsyncStorage or SecureStore.

AI Summary: Implement backend validation to prevent duplicate word guesses in a Wordle-like game. The `/wordle-sessions/:id/guess` endpoint needs modification to check if a submitted guess already exists in the session's `previousGuesses` array. A 409 Conflict error should be returned if a duplicate is found.

AI Summary: Create a POST API endpoint (/wordle-sessions/:id/guess) to handle player guesses in a decentralized Wordle game. The endpoint should receive a guess, retrieve the game session, evaluate the guess using the `evaluateGuess` function, save the guess and result to the session history, and return appropriate responses (including 404 if the session isn't found).

AI Summary: Implement a pure function in TypeScript that evaluates a Wordle guess against the solution word, returning the status (correct, present, absent) for each letter, handling duplicate letters correctly. The function will be used as the core word evaluation logic for a decentralized Wordle game built on StarkNet.

AI Summary: Implement backend validation for the DeWordle game to reject guesses that are not valid words from a pre-existing dictionary. The validation should occur before game logic processing, returning a 400 Bad Request error if the word is invalid. The invalid guess should not count as an attempt.

AI Summary: Implement logic to update the game session status (WON, LOST, or IN_PROGRESS) after each guess in a decentralized Wordle game built on StarkNet. This involves checking the guess evaluation result and updating the database accordingly within the transaction.

AI Summary: Implement a `SessionCompletedEvent` in the StarkNet smart contract to decouple game logic. The event should be emitted when a game session ends (win or loss) and include session ID, user ID (if applicable), final status, guess count, and solution word.