olcayseygan
UserFour Claude Code skills that redo your work as a tournament: re-make rebuilds it, re-master sharpens it, re-design redesigns it, re-view puts it on trial - scored, fought head-to-head, round after round.
Categories
Indexed Skills (7)
audit
Analyses code from several independent perspectives, then makes those perspectives argue with each other until they converge on a shared verdict. Each lens reviews blind, every finding is cross-examined by a lens that wants to kill it, conflicts are resolved as explicit trade-offs rather than averaged away, and the result is a ranked findings table with recorded dissent plus a full analysis. Use when the user says "/audit", "audit this code", "red-team this", "review this code from every angle", "review this code", "critique this", "analyse this code", "what's wrong with this", "look at this from every angle", "is this any good". For rewriting use rewrite, for improving in place use refactor, for UI use reskin. This skill judges code — for measuring data and writing the result up as a report, use report instead.
diagram
Draws a diagram that explains how something works, in the library the user names — Mermaid by default, otherwise Graphviz, D2 or PlantUML. One question per diagram, at most ten nodes, every branch labelled, and anything bigger split into an overview plus linked detail diagrams instead of one unreadable wall. Use when the user says "/diagram", "draw this", "diagram this flow", "show me how this works", "flowchart", "sequence diagram", "state machine", "architecture diagram", "visualise this process", or the Turkish equivalents "diyagram ciz", "akis semasi", "sema ciz", "gorsellestir". For measuring data use report, for judging code use audit, for charts of numbers use dataviz.
refactor
Improves existing work in scored rounds instead of rewriting it. Each round attacks the champion's weakest criterion with a reviewable diff, scores the result, and fights it head-to-head (VS) against the current champion; the loop runs until a challenger fails to beat it on both score and VS, then reports a full analysis plus a round-by-round table. Use when the user says "/refactor", "refactor this and compare", "make this better", "polish this", "sharpen it", "refine it", "optimize it", "improve it until it can't be improved". For throwing the code away and starting over, use rewrite instead.
report
Runs a data, measurement, root-cause or comparison study and delivers it as a dated, self-contained single-file HTML report. Use when the user says "/report", "analyse this data", "write a report", "measure this", "compare A and B", "find the root cause", "characterise this", "which one is better", "summarise these logs", or the Turkish equivalents "analiz et", "rapor çıkar", "raporla", "ölç", "karşılaştır", "kök neden bul". Fits log/CSV/raw-data studies, A-B comparisons, tuning, performance measurement, regression investigation, survey and metric summaries. Do NOT use for reviewing source code — that is audit — or for plain reading and searching a codebase.
reskin
Redesigns an interface from scratch in scored rounds, obsessing over alignment, layout, sizing, spacing, hierarchy, contrast and states. Each round designs a fresh version, renders it, scores it against a frozen design rubric, and fights it head-to-head (VS) against the reigning design; the loop runs until a challenger fails to win on both score and VS, then reports a full analysis plus a round-by-round table. Use when the user says "/reskin", "redesign this screen", "restyle it", "make this UI better", "the layout looks off", "fix the spacing/alignment". For rewriting logic use rewrite; for improving existing code in place use refactor.
rewrite
Rebuilds a piece of work from scratch, scores it, and pits it head-to-head (VS) against the previous version. Runs in rounds; each round challenges the reigning champion, and the loop continues until a challenger fails to win on both score and VS. Ends with a full analysis plus a round-by-round summary table. Use when the user says "/rewrite", "rewrite this from scratch", "remake it", "redo this from scratch", "rewrite it and compare", "try a different approach and see which is better". For improving existing code in place use refactor; for redesigning an interface use reskin.
specify
Turns a raw need text into atomic, testable requirements — one sentence per requirement, EARS phrasing, an active "the system" subject, a single modality vocabulary, quantified thresholds, MoSCoW priority and one flowing verification sentence each — plus an explicit list of what the source text left ambiguous. Use when the user says "/specify", "write requirements", "turn this into requirements", "requirements analysis", "acceptance criteria", "EARS", "SRS", "BRD", "user story", "business analyst", "what exactly are we building". For judging code use audit, for measuring data use report, for building use rewrite or refactor.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.