The snippets, ordered obscure → unmistakable

  1. Snippet 1(Generic helper)
  2. Snippet 2(Doc IR builder)
  3. Snippet 3(Printer dispatch)
  4. Snippet 4(Options resolution)
  5. Snippet 5(Wadler printer)
  6. Snippet 6(prettier — entry)

Why this project gives itself away

The give-away. Snippet 1 is generic. Snippet 2 is the Doc IR — group/indent/line/softline/hardline are Prettier's intermediate representation, derived from Wadler's "A Prettier Printer". Snippet 3's genericPrint(path, options, print) is Prettier's plugin contract. Snippet 4's `arrowParens` / `printWidth` / `singleQuote` are the iconic config keys. Snippet 5 explicitly references Wadler's paper. Snippet 6 names James Long and the "opinionated code formatter" tagline.

How a Framed puzzle is built

Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.