games: add a colour-position recall mode for visual memory
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 45/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- next.js, react, typescript
研究方向
Start by reading issues #24 and #58 to understand the parent work and dependency, then locate the existing Digit Recall game and its shared memory/session controls. Trace how rounds, timing, feedback and restarts currently work before planning the new mode. Done means the specified layout, recall, progression, accessibility and browser checks are covered; the issue does not name files or tests, so finding the entry points will take project familiarity.
由索引模型根據 Issue 內容生成。
描述
Part of #24. Depends on #58.
Student problem
The existing Digit Recall game trains number memory. Students also need a short exercise that asks them to remember where visual items appeared.
Scope
- Show a small grid of distinct colors with accompanying symbols/text labels for a defined memorization window.
- Hide it, name one of those items and ask the student to choose its former position.
- Start with a 2×2 layout and introduce documented progression in exposure time or layout complexity.
- Keep the spatial-memory mechanic separate from typing a remembered number, while reusing common memory/session controls.
- Provide learning replay and feedback showing the original layout. Timed rounds use the shared timing policy.
- Do not make color the only way to distinguish items; test labeled and high-contrast presentations with keyboard/touch input.
- Keep both existing games available, free and usable without login.
Done when
- Tests cover layout generation, target/position evaluation, memorization-to-recall transitions and progression.
- Hidden items cannot remain selectable/readable as the answer during recall.
- Browser checks complete a round, view feedback and restart without retaining the previous target.
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 1
- 平均合併
- 8 小時 58 分鐘
- 30 天內合併 PR
- 37
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
難度 2/5 1-3 小時 新手友好度 62/100
procoderji-com/procoderji#104 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100
procoderji-com/procoderji#36 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 85/100
procoderji-com/procoderji#35 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 79/100
procoderji-com/procoderji#34 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 90/100
procoderji-com/procoderji#33 ·
維護者通常 1 天內回覆
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
bug platform-android
難度 2/5 1-3 小時 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 則留言 ·
維護者通常 2 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
難度 1/5 1 小時以內 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆