Make practice games useful for campus placement preparation

Aperta
  • Qualcosa non va?
#24 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
next.js, react, typescript
Ambito
backend, design, frontend

Direzione di ricerca

Start with related planning issue #22 and the games hub and landing page; the payload does not name their file paths. Define the intended skills and student journeys, then review how the existing Pattern Sprint and Digit Recall pages present rules, feedback, difficulty, accessibility, and practice guidance. Done means the hub explains playable games accurately, each exercise has clear learning feedback and guidance, and student feedback is gathered before expanding the catalog.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement games

Context

The current games are Pattern Sprint and Digit Recall. They are original short exercises, but the games page describes them as a quick break and does not explain how they help with campus-placement preparation.

Proposal

Make the games area a useful placement-practice space. First define the skills and student journeys it should support; then improve the exercises, feedback, and page copy to match. Begin with areas that fit short browser rounds, such as quantitative aptitude and logical reasoning, and evaluate coding or interview practice with students before expanding.

Acceptance criteria

  • Describe the intended placement-preparation skills for each exercise and avoid implying that the games predict or guarantee hiring outcomes.
  • Provide a clear explanation after each answer and useful difficulty progression or practice guidance.
  • Review questions and answers for correctness, clarity, and original authorship.
  • Keep the core practice flow free, mobile-friendly, keyboard-accessible, and usable without login.
  • State clearly that the content is independent practice, not an official assessment from an employer.
  • Gather student feedback before expanding the game catalog.

Related planning issue: #22.

Implementation plan

Build original placement-practice games in focused contributions. All core practice remains free and available without login. Start small, gather student feedback, then expand the catalogue.

Foundation and first release
  • #58 Shared catalogue, rules boundaries and session lifecycle
  • #59 Switch Challenge: symbols and shapes
  • #60 Digit Challenge: constrained arithmetic
  • #61 Grid Challenge: spatial memory and symmetry
  • #69 Browser history and per-game progress; can begin after the first game
Additional skill practice
  • #62 Motion Challenge: standard and axis-restricted boards
  • #63 Deductive Challenge: missing-symbol grids
  • #64 Inductive Challenge: visual odd-one-out
  • #65 Bubble Math: order expression values
  • #68 Colour-position recall
Planning games and mixed sessions
  • #66 Path Finder: rotatable arrow blocks
  • #67 Key and Door: directed maze planning
  • #70 Mixed timed practice; begins after at least three stable game families

This issue also owns the games hub and landing-page framing: show the skill, mode, difficulty and expected duration; link to instructions and relevant practice. Keep existing game links working. Do not advertise games or modes before they are playable.

Each game issue requires original puzzles/assets, explained rules/scoring, useful learning feedback, keyboard/touch controls and meaningful generator/evaluation tests. Quick-calculation and multiple-gap variants can follow the arithmetic/deductive foundations; no separate backend, public leaderboard or paid access is needed for this release.

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
8h 58m
PR unite (30g)
37

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di procoderji-com/procoderji

Tutte le issue di procoderji-com/procoderji

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.