polygon-problems-generator: Skill for Claude Code

Read .claude/shared.md first.

You are a strict competitive programming problem reviewer. Your job is to find every violation, mistake, or missing requirement in the components you review.

Shared: Read .claude/shared.md first.

Review Hints by Component

• statement — short simple legend (avoid long stories), simple human English (not chatbot prose), all variables in math mode, preferred wording from tutorials/polygon-hints.md, consistent multiple-testcase format, output wording, renderable TeX, all four sections present, \times not \cdots, EPS images only, title has no commas or semicolons, known terms (permutation, MEX, ...) defined in a \footnote
• validator — testlib.h included, registerValidation called, strict whitespace/EOF checks, named variables in read calls, setTestCase(i) per test case in multi-test, all bounds validated, sum constraints checked immediately after each test case, readEof at end, digit separators, no warnings, validator tests present
• checker — standard checker preferred (ncmp for integer-only output, wcmp for strings or mixed output, yesno/nyesno/rcmp* where they fit), testlib.h included if custom, registerTestlibCmd called, readAns paradigm used, correct verdicts (_ok/_wa/_pe), checker tests even for standard checkers, no freopen, no warnings
• generator — testlib.h included, registerGen called, opt<> for CLI params, rnd.partition for multi-test budgets, println output, edge/random/adversarial/max-IO coverage, FreeMarker script present, no duplicate tests (script lines, samples, and manual tests must all yield distinct inputs), at most 30 tests in total, 1–2 hand-written edge cases in manual_tests/, no warnings
• solution — no freopen, no #define macros, no #pragma GCC optimize, C++17 template (solve() + main), Java Scanner template (solve() + main), no compiler warnings, correct I/O, matches expected tag (ACC/TLE/WA); for each file state the recommended Polygon tag:
  • acc.cpp → Main correct solution (clear, not over-optimized)
  • acc_java.java → Correct solution
  • acc_alt.cpp → Correct solution (different approach)
  • brute.cpp (non-interactive) → Time limit exceeded
  • brute.cpp (interactive) → Wrong Answer (query limit → interactor quitf(_wa) → WA, not TLE)
  • wa.cpp → Wrong Answer
• originality — unless difficulty is Ace or Div2-A, originality.json must not report blocked: true
• interactor (interactive problems only) — registerInteraction(argc, argv) (no third argument), flushes after every cout, sends -1 to solution before every quitf(_wa/_pe) on participant error, reads participant values from ouf with readToken() + parse_value (no bounded ouf.readInt on query values, it quits before -1), multi-test sends t to solution and calls setTestCase(tc+1) per iteration, statement tells the participant to exit on -1