Final Challenge — Solution

Task: A different recurring instruction shows up: "whenever generating
a comparison table between two frameworks, always order columns so the
framework the user already knows comes first." Walk this through the
same six-question checklist this capstone used, and decide: new rules
file, addition to an existing one, or memory instead? Justify each
step.

Question 1 — Durable/universal, or conversational/specific? (Ch. 1/8)
This is durable and universal in shape - it should apply identically
to EVERY future comparison table, for any pair of frameworks, forever
- but it isn't a fully standalone topic the way video scripts are.
It's a small formatting detail that only matters within a context that
already exists elsewhere (comparison tables inside course chapters).
This is a meaningful difference from the capstone's own video-script
example.

Question 2 — Does it only make sense inside this one project? (Ch. 2)
Yes - it depends entirely on this project's own established practice
of generating comparison tables inside course chapters (seen
throughout this course's own compare-tables, and across many numbered
courses). It belongs in a project rules file, not the global CLAUDE.md.

Question 3 — Does an existing rules file's own format genuinely fit,
or does forcing it in lose something real? (Ch. 5)
Here the answer diverges from the capstone's own example: this
instruction fits naturally as ONE MORE detail inside P12 (Chapter 3),
which already governs code-block and table formatting conventions
across every numbered course. Nothing is lost by adding it there -
unlike video scripts, there's no genuinely new file shape or storage
convention this instruction needs of its own.

Question 4 — What letter prefix is free?
Not applicable - since this belongs inside an EXISTING rule (P12)
rather than a new file, no new letter prefix is needed at all.

Question 5 — Write the rule
A short addition to P12's own existing text: "When a comparison table
contrasts two frameworks and the user is already known to know one of
them, order columns so the familiar framework comes first."

Question 6 — Add the @rules/ line / update tracking files (Ch. 7/9)
Neither applies here either - since permanent_rules.md is already in
the @rules/ list, editing P12's own existing text needs no new wiring
step at all, and there's no separate course/tracking-file entry this
kind of formatting-convention change would need to touch.

Decision: this belongs as a small ADDITION to an existing rule (P12
in permanent_rules.md), not a new standalone rules file, and not
memory either - it's exactly durable and universal enough to earn a
place in a rules file, it just doesn't need a whole new file of its
own the way a genuinely new content type (video scripts) did.

Notes:
- This is precisely the point of walking through the checklist
  explicitly rather than defaulting to "recurring instruction always
  means a brand-new file" - the capstone's own video-script example
  and this exercise's own comparison-table example reach different,
  correct answers to the exact same six questions, because the two
  scenarios are genuinely different in scope.
- The real skill this final challenge is testing is knowing when
  Chapter 5's own "does an existing format genuinely fit" question
  answers YES instead of NO - recognizing a small addition doesn't need
  Chapter 10's own full new-category machinery at all.