{
  "format": "promtly.pack/1",
  "name": "Code",
  "author": "promtly",
  "description": "Diff review, commit messages, tests and explanations — the four that use {{clipboard}}.",
  "decks": [
    {
      "id": "deck_code",
      "name": "Code",
      "tiles": [
        {
          "id": "tile_code_01",
          "label": "Review diff",
          "body": "Review this change for correctness bugs first, then for anything that could be simpler. Rank findings by how likely they are to actually bite in production. Skip style opinions, and say plainly if you find nothing.\n\n{{clipboard}}",
          "color": "amber",
          "uses": 0
        },
        {
          "id": "tile_code_02",
          "label": "Commit msg",
          "body": "Write a commit message for this diff. One subject line under 72 characters saying what changed and why. Add a body only for what a future reader could not infer from the diff itself — the reason, the trap, the thing you measured.\n\n{{clipboard}}",
          "color": "slate",
          "uses": 0
        },
        {
          "id": "tile_code_03",
          "label": "Write tests",
          "body": "Write tests for this. Cover the cases that would actually break it in production, not the happy path — boundaries, empty inputs, the concurrent case, the thing that silently returns the wrong answer. Use {{framework=vitest}}.\n\n{{clipboard}}",
          "color": "green",
          "uses": 0
        },
        {
          "id": "tile_code_04",
          "label": "Explain this",
          "body": "Explain what this does, assuming I know the language but not this codebase. Lead with the one sentence that makes the rest obvious. Call out anything surprising or load-bearing, and anything that would break silently if changed.\n\n{{clipboard}}",
          "color": "blue",
          "uses": 0
        }
      ]
    }
  ]
}