Explore … canonical themes, disable or override any standard theme with your own .thm version, and rate community themes (1–5 ★).
.thm
FIDE Album Telemetry · Key Paradox & Solver Plausibility · 3×3 King Field · Per-Mate Purity & Idle Officer Audit
Import any YACPDB entry by ID/URL or query YACPDB for #2 compositions by theme keyword or composer. Private local compositions are never uploaded.
#2
Manage all #2 compositions and .thm theme specifications you own, plus composer identity, appearance, and backups.
🛡️ Consent-First Privacy: You may use a pseudonym (@handle) or your real name. We never auto-fill your name or email from sign-in providers or browser autofill without your explicit consent. Terms of Service & Privacy Policy
@handle
/studio-api/auth/oauth/callback
Every theme modification records an incremental revision number and a mandatory reason comment ("Why"). When exiting beta, the administrator can wipe all intermediate trial histories and reset all theme specifications to a clean Revision 1 (1.0 Production Baseline).
Workbench Guide, #2 Multi-Phase Matrix Theory & Thema (.thm) Specification Reference
Thema Studio is currently an experimental beta and is not at production-level quality yet. Theme specifications, primitives, and scoring heuristics are still under active development and verification — you may encounter false-positive or missed theme detections, incomplete edge cases, or breaking changes. Please report any issues via the 🐛 Bugs button in the top bar!
Thema Studio is an interactive orthodox #2 composition, formal verification, and aesthetic telemetry workbench powered by the Thema Pattern DSL (Domain-Specific Language) compiled to WebAssembly.
All … canonical #2 theme specifications are expressed declaratively in the Thema DSL and tested against 1,930+ benchmark positions. Edge cases in multi-phase virtual try filters, subtle unguards/interferences, and theme subsumption are continuously refined against The Chess Problem Encyclopedia and FIDE Album criteria.
While orthodox #2 solving, cook/dual detection, and Pure/Model mate verification are exact, the FIDE Quality Score and 6-Axis Telemetry weights (Thematic Density, Key Paradox, Try Deception, Defensive Mechanism, Economy) are heuristics under active tuning.
If a theme definition over-matches or misses a nuance on your composition, you don't have to wait for an engine update: click Encyclopedia (⌘K) to disable or override any built-in theme, or edit and test .thm rules live in the Theme Editor tab.
Any change to a theme specification requires an explanation. Please explain why this revision was made:
Updates to published themes are published as incremental revisions. Previous revisions remain preserved in public revision history, ensuring historical problems and studies referencing earlier versions never break.
Analyze, explain and author themes in orthodox mate-in-two (#2) problems.
Thema Studio is a modern chess problem workbench dedicated to orthodox mate in two (#2) compositions, multi-phase virtual play matrices, and thematic aesthetic telemetry.
Theme detection is powered by Thema (.thm) — a small language for describing chess themes. Every detected theme comes with its readable .thm definition, so you can see exactly why it matched.
Write original theme rules in the built-in Theme Editor with live 5-stage diagnostics. Run them in one click against the built-in benchmark problems plus your saved and community problems, and share them with composers worldwide in the Community Hub.
A public name or pseudonym is only required when sharing, publishing, or commenting — and is never auto-filled without your consent.
🛡️ No Auto-Fill Without Consent: We never pull or auto-fill your name or email from your sign-in provider. Enter either a @handle pseudonym or your real name as you wish to be credited.
Thema Studio Consent-First Attribution & Data Protection Charter
Thema Studio never auto-fills or harvests your name or email from sign-in providers or browser autofill. When sharing #2 compositions, publishing community .thm theme specifications, or posting comments, you choose whether to credit yourself under a @handle pseudonym or your real name.
You may sign in using GitHub, Lichess, Google, or a WebAuthn Passkey. Sign-in stores only an opaque provider identifier and session token to synchronize your workspace — never auto-filling your email address or profile name from an identity provider.
You do not need to enter a name or handle to use the workbench, solve #2 positions, author .thm specifications, or sign in. Choosing your public name or @handle is requested only when you actively:
Unpublished board positions and local .thm drafts remain strictly private and are never exported to external catalogs (such as YACPDB). Public comments and theme descriptions must remain scholarly and free of external URLs or spam.
Logged-in users can report bugs (public or visible only to admin @jon) and post flat plain-text replies.
@jon
GitHub, Lichess, Google, or Passkey (zero email collected).
--