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

Abierto
#64 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
next.js, react, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
8 h 58 min
PR fusionados (30 d)
37

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de procoderji-com/procoderji

Todos los issues de procoderji-com/procoderji

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.