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 天内回复