Play your first case
This page is the spine. Six steps take you from nothing to a case open on your machine, with a tutor scoped to it and a score you can run as often as you like. Each step is short here and has a page of its own when you want the detail.
Nothing on this page pushes, opens a pull request, or records anything against your profile. Handing the case in is one command past the end, and it has its own page too.
Before you begin
Section titled “Before you begin”- Fito installed on your machine, per Install and prerequisites.
- A Fito server you can reach, with its web app running.
- An LLM provider configured in pi. The tutor and the scoring run on your subscription.
Allow a sitting for the case itself. The two sample cases are estimated at 35 and 40 minutes.
1. Create an account
Section titled “1. Create an account”Open the web app and sign up at /auth/signup, or sign in if you already have
an account.
While you are there, link GitHub with Continue with GitHub. You do not need it for this page, and you will need it the moment you submit.
→ Create an account and sign in
2. Pick a case and copy its id
Section titled “2. Pick a case and copy its id”Open /cases and choose one. Its cover carries the
learning objectives,
the prerequisites, the
rubric criteria and —
once you are signed in — which prerequisites you already hold.
Copy the id out of the URL, the <id> in /cases/<id>. Cases have no short
name, so you paste this id into every command below.
3. Log in from the terminal
Section titled “3. Log in from the terminal”Start a pi session in any folder, then:
/fito-loginYour browser opens, you sign in with the same account, and your tokens land in
~/.fito/credentials. The browser tells you to return to the terminal.
4. Open the case
Section titled “4. Open the case”/fito-case-open <case-id>This forks the case to your GitHub, clones it to ~/.fito/cases/<case-id>/,
checks out the published version, creates your working branch, and then briefs
you: the situation, the task, the constraints, the deliverables and the
knowledge components it develops. It never shows you the solution.
5. Work, and ask when you are stuck
Section titled “5. Work, and ask when you are stuck”Open ~/.fito/cases/<case-id>/ in your editor and solve it. Commit on the
working branch.
When you get stuck, ask the tutor:
/fito-tutor how should I approach this?It can read this case and the knowledge behind it, and nothing else.
6. Preview your score
Section titled “6. Preview your score”/fito-evaluate <case-id>A dry run against your local checkout. No pull request, no submission, nothing recorded. It runs the rubric’s automated checks, scores each criterion 0 to 3 with its reasoning, and shows the proficiency each score would record. If the case carries a quiz you answer it here as practice.
Iterate until you are happy with it.
You are at the finish line for setup
Section titled “You are at the finish line for setup”You now have a real case with a working checkout, a tutor and a local scoring loop. Everything from here is the case itself.
When you are ready to hand it in, that is /fito-submit <case-id> — and it
needs the GitHub link from step 1.
What’s next
Section titled “What’s next”- Submit and read your result — hand the case in and see what lands on your profile.
- Bloom levels and proficiency — what a recorded score means.
- Browse the knowledge area — the vocabulary a case is scored against.