Practice against the code patterns you actually ship

You connect GitHub from your account, pick one or more repositories you care about, and ask EraCode to generate challenges from that context.

The system reads enough of the repository to understand structure, technologies, and representative patterns—then produces coding and mixed-format work that references the same kinds of files, folders, and conventions you already use.

You solve challenges in the normal EraCode flow: editor, tests, feedback, and timed scoring where applicable. When something is unclear, you are practicing the same “figure it out in this codebase” muscle you use at work.

Generic puzzles and language-only drills keep syntax warm, but they rarely match how your team names things, splits modules, or handles edge cases in production.

When challenges are grounded in repositories you actually ship, refreshers line up with real APIs, config shapes, and patterns you will see in the next PR—not abstract “Foo” classes or toy domains.

That makes practice easier to stick with: you are reinforcing memory for code you will touch again soon, instead of filing yet another unrelated exercise under “maybe someday.”

Faster onboarding when you rotate into a service you did not write, fewer “I forgot we did it that way here” moments in review, and sharper debugging because you have recently exercised the same stack and layout.

It complements codebase literacy: you are not just reading—you are doing short, focused reps on the same surface area your team owns.