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

Aberta
#64 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
next.js, react, typescript
Domínio
frontend, game-dev

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
1
Forks
1
Merge médio
8h 58min
PRs com merge (30d)
37

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de procoderji-com/procoderji

Todas as issues de procoderji-com/procoderji

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.