games: add Inductive Challenge for visual odd-one-out reasoning

Ouverte
#64 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
next.js, react, typescript
Domaine
frontend, game-dev

Piste de recherche

Start by reading the parent issue #24 and dependency #58, then locate the game's existing exercise entry points and tests. Define and test the rule families, unique outlier evaluation, deterministic generation, difficulty bounds, accessibility, and shared scoring behavior. Done when the specified rule and browser tests pass and puzzle fixtures receive a visual clarity review.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement games help wanted

Part of #24. Depends on #58.

Student problem

Students need practice identifying a consistent visual rule and explaining which item breaks it.

Scope

  • Present a set of original figures where exactly one breaks a documented rule.
  • Start with rule families such as line count, line continuity, filled-cell count, shape count and fill pattern.
  • Increase difficulty through controlled figure complexity and distractors, rather than unexplained random changes.
  • Store the governing rule with each puzzle and explain the outlier after answering in learning mode.
  • Validate that the intended rule identifies exactly one outlier. Avoid accidental alternative interpretations where practical.
  • Describe this exercise as odd-one-out; do not advertise sequence completion unless that mechanic is implemented.
  • Support keyboard/touch selection, meaningful figure labels/non-color cues, shared timing/results and free guest access.

Done when

  • Tests cover each rule family, unique outlier evaluation, deterministic generation and difficulty bounds.
  • Puzzle fixtures receive a visual clarity review.
  • A browser test selects an answer, reads its explanation and starts another round without duplicate scoring.
Langage dominant
TypeScript
Étoiles
1
Forks
1
Merge moyen
8 h 58 min
PR mergées (30 j)
37

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de procoderji-com/procoderji

Toutes les issues de procoderji-com/procoderji

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.