>_DevCheatsheetsRUN

LEARNING SYSTEM // HOW IT WORKS

From a command lookup to a decision you can recall.

DevCheatsheets turns Git, Linux, and Docker references into short scenario runs. You read the situation, make a command decision, inspect the explanation, and meet missed concepts again in a later run.

Try a Git runInspect the command library

A SINGLE ROOM

The prompt asks for judgment, not a definition.

A typical room gives you a constraint: unfinished work exists, a production fix is urgent, and the work needs an isolated branch. The task is to produce the command that fits those conditions.

Situation

Keep the current work intact and start a new hotfix branch immediately.

Decision$ git switch -c hotfix/login
Why it fits

switch -c creates the named branch and switches to it in one command. The explanation connects the syntax to the constraint.

THE FOUR-PART LOOP

Practice, explain, and revisit.

The loop is intentionally visible so learners know what the game records and why a concept can return.

  1. 01

    Read the context

    Rooms begin with a developer task, incident, or operational constraint instead of an isolated vocabulary question.

  2. 02

    Make the decision

    You choose, type, repair, or order commands. An incorrect answer reduces health and keeps you in the same room.

  3. 03

    Inspect the result

    Feedback identifies the command, explains the fit, and includes safety guidance and an HTTPS documentation source.

  4. 04

    Return to weak concepts

    A corrected retry remains in the run's weakness record. A later first-attempt success clears that concept from the weak list.

PROGRESS RULES

What a run actually records.

8 + 1standard rooms and one boss room per run
3 / 6room milestones where earned rewards are checked
LocalXP, mastery, streaks, and active runs stay in browser storage

A correct answer advances the room and can award XP, combo progress, and rewards. An incorrect answer records the attempt without moving the cursor. Reaching zero health ends the run and blocks further input.

PUBLIC EVIDENCE

You can inspect the material without playing.

The game routes depend on local progress and are excluded from search indexing. The underlying learning material remains public through command references and authored field guides.

Command referencesBrowse Git, Linux, and Docker commands with explanations and sources.Field guidesRead complete workflows, failure modes, verification steps, and safety boundaries.Lab notesSee how documentation links were audited, corrected, and regression-tested.

BOUNDARIES

A simulation is not a production shell.

DevCheatsheets evaluates submitted text against authored accepted answers. It does not execute commands against a repository, host, container engine, or registry. Platform details can differ, so verify targets, privileges, versions, and official documentation before using a command on a real system.