ワンクリックでManusで任意のスキルを実行

wc-building-block-crossover

The recombination operator for the FIFA World Cup Fantasy evolution engine. Crosses elite candidate squads/plans at BUILDING-BLOCK boundaries (Captain Core, Clean-Sheet Spine, Mid-Engine, Differential Pod, Enabler Bench; or for matchday plans the XI/captain-ladder/bench/sub/chip blocks) — harvesting the strongest module from each parent rather than swapping individual players — then runs a feasibility REPAIR operator (budget, nation cap, formation, 15-man shape) that restores legality from the cheapest block first and never guts a value-bearing block. Records block lineage (which parent each block came from). Implements the Evolution document's central lesson that naive crossover destroys good building blocks. Use in the recombine stage after fitness selection.

Manusで実行

スター120

フォーク16

更新日2026年6月11日 14:38

ソース

lyndonkl

lyndonkl/claude

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

SKILL.md

readonly

name

wc-building-block-crossover

description

wc-building-block-crossover — recombine modules, then repair

Implements the recombination step of evolution-protocol.md against the module map in building-blocks.md. The discipline that defines this skill, straight from the Evolution document: a squad is not a flat list of independent slots; it is modules with internal linkage, and crossover must operate at module boundaries or it destroys the very things that make the parents good. "Excellent planning + Excellent memory without rediscovering both independently" — here: the best captain core and the best clean-sheet stack, fused.

Inputs

The elite candidate set (from fitness selection), each with its block tags and per-block quality.
Live constraints from tournament-state.md: budget (group $100m / KO $105m), nation cap (3 group, current-phase cap KO), phase.

Workflow

- [ ] 1. For each block slot, rank the elites by that block's quality (per-block fitness contribution)
- [ ] 2. Compose offspring by harvesting the top block from different parents (try a few combinations)
- [ ] 3. REPAIR each offspring to feasibility — cheapest block first, never gut a value block
- [ ] 4. Drop any offspring whose parents' blocks are fundamentally incompatible (repair would break a block)
- [ ] 5. Record block lineage per offspring; emit the feasible offspring

Step 1–2: Cross at block boundaries

For a squad, the blocks are BB1 Captain Core, BB2 Clean-Sheet Spine, BB3 Mid-Engine, BB4 Differential Pod, BB5 Enabler Bench (BB6 Fixture/Timing is the constraint layer, enforced in repair). For each block, identify which elite has the best version (highest contribution to fitness for that module — best captain core, best stack, sharpest pod). Compose 2–4 candidate offspring by mixing: e.g.

offspring_1 = BB1(A1) + BB2(A4) + BB3(A5) + BB4(A2) + BB5(cheapest-feasible)
offspring_2 = BB1(A6) + BB2(A3) + BB3(A5) + BB4(A4) + BB5(...)

Harvest whole blocks, not players. Do not pluck one defender out of a stack — the stack's value is its correlation; take it or leave it. For a matchday plan, cross MB2 captain-ladder from one parent, MB3 bench-order from another, MB1 XI / MB4 sub-triggers / MB5 chip likewise — keeping each block internally intact.

Step 3: Repair to feasibility (priority order)

Recombined blocks will usually break BB6 constraints. Repair in this order, preserving value-bearing blocks:

Formation. If no valid XI (1 GK; 3–5 DEF; 2–5 MID; 1–3 FWD) can be fielded from the 15, the recombination is structurally broken → re-pick the offending block from the next-best parent rather than patching individual players.
Nation cap. If a nation exceeds the cap, swap the lowest-xEV offender, preferring to move a BB5 enabler or BB4 differential over a BB1/BB2 value piece.
Budget. If over budget, release funds from BB5 first (downgrade the cheapest enabler), then BB4 (cheaper differential), and only touch BB1/BB2/BB3 if unavoidable — and if so, prefer downgrading one BB1 premium over breaking the BB2 stack (correlation is harder to rebuild than a single captain option).
Matchday spread / dead-minutes bench. Fix last; it's the cheapest lever.

Step 4: Drop incompatible offspring

Repair invariant: never satisfy a constraint by destroying a block. If, say, the only way to afford BB1(A1)'s captain core is to break BB2(A4)'s stack, the two parents are incompatible — drop that offspring and report it rather than emit a mangled squad. An incompatible pairing is information (those two genotypes don't fuse this round), not something to force.

Step 5: Lineage + emit

For each surviving offspring record:

offspring_id: <id>
blocks:
  BB1_captain_core:   { from: A1, players: [...] }
  BB2_clean_sheet:    { from: A4, players: [...] }
  BB3_mid_engine:     { from: A5, players: [...] }
  BB4_differential:   { from: A2, players: [...] }
  BB5_enabler_bench:  { from: repair, players: [...] }
repair_log: [ "downgraded enabler X→Y for $1.5m", "swapped nation-clash bench Z" ]
feasible: true

Lineage feeds the board ("A1 core + A4 stack + A2 pod") and the archetype scoreboard (which genotypes' blocks keep getting chosen). Hand the offspring to mutation, then diversity.

Guardrails

Whole blocks only. No individual-player crossover — that's the failure mode this skill exists to prevent.
Repair never guts a block. Cheapest-block-first; drop incompatible offspring rather than mangle.
Always emit lineage + repair log. Unexplained offspring can't be presented or learned from.
Produce a variance-diverse offspring set where the parents allow it (a safe fusion and a brave fusion) — the diversity skill checks this next, but don't pre-collapse it here.

このリポジトリの他の Skills

同じリポジトリ

wc-archetype-mutation

lyndonkl/claude

The mutation operator for the FIFA World Cup Fantasy evolution engine. Applies small, bounded, feasibility-preserving perturbations to a recombined offspring squad/plan — swap one differential for an adjacent-price alternative, reorder the bench by kickoff, shift one captain-ladder step, try one fixture-swing transfer, nudge one enabler. Mutation rate is low by default and raised on demand by the diversity governor when the population has collapsed. Each mutation stays inside budget/nation/formation feasibility. Use in the mutate stage after recombination, or when wc-population-diversity calls for more exploration.

2026-06-11120

wc-captain-ladder

lyndonkl/claude

Computes the optimal rolling-captaincy LADDER across a matchday's staggered kickoff sequence — the ordered captain candidates, the explicit bank-or-switch rules at each kickoff, and the captaincy_uplift that wc-fitness-eval folds into raw_xEV. Because the armband doubles the round's points AND can be MOVED during the round to a player who has not yet kicked off, captaincy EV is the expected value of the best outcome reachable by switching across the sequence — not a naive 2x of the top xEV player. Call from wc-matchday-tactician (to write MB2 of the matchday plan), from the strategists (to value a candidate's captaincy when building a matchday plan), and from wc-fitness-eval (which consumes captaincy_uplift). Returns the ladder, the switch thresholds, and the uplift against a stated baseline; the ladder is moot under the Maximum Captain chip (value = max of candidates).

2026-06-11120

wc-chip-timing

lyndonkl/claude

Scores the deployment leverage of all five FIFA World Cup Fantasy boosters (Wildcard, 12th Man, Maximum Captain, Clean Sheet Shield, Qualification Booster) across the remaining tournament horizon — computing, for each chip and each candidate round, the EXTRA expected points the chip yields in that round versus an average round, then turning the leverage surface into a fire/hold call per chip this round plus a maintained earmark table (chip -> earmarked round -> trigger -> fallback). This is the math engine behind wc-chip-strategist. Reads the round's player-ev, clean-sheet, fixture/progression, ownership and captain-ladder signals plus tournament-state (chips remaining, phase, surviving nations); never re-derives them. Enforces the golden rule — never reach the semis with chips unused. Use whenever a chip decision is live (the chip-check prompt, the group->KO transition, or any round where a chip is earmarked or leverage spikes). Emits a chip-plan signal.

2026-06-11120

wc-clean-sheet-model

lyndonkl/claude

Computes clean-sheet probability and defensive-returns EV for a team in a specific fixture from team defensive strength (xGA) against opponent attacking strength (xG), then models the STACK CORRELATION that turns a Clean-Sheet Spine (BB2) — GK + k same-team defenders — into a single correlated bet rather than k independent draws. Returns p_cs(team,fixture), a stack_corr_bonus capturing the amplified joint ceiling and shared downside (sign interacts with the rank objective θ: amplify when chasing, discount when protecting), and expected_ga with its conceding-points downside. Use when sizing a defensive stack, valuing a GK/DEF pick, scoring a candidate's BB2, or weighing the Clean Sheet Shield chip — called by wc-squad-architect, wc-matchday-tactician, wc-fitness-eval, and the strategists.

2026-06-11120

wc-decision-board

lyndonkl/claude

Renders the FIFA World Cup Fantasy decision board — the advisory output that surfaces 2-4 genuinely distinct, weighted options for the expert manager and ends on "your call." Takes the evolution engine's verified offspring (with fitness decomposition, genotype lineage, and specialist dissent) and formats each as an option with its concrete picks, EV/ownership-leverage/variance/progression decomposition, football reasoning, what it's betting on, the dissent, and an ownership read — then a trade-off axis, a recommended-but-overridable default tied to the rank objective, and a "what I need from you." Enforces options-not-commands, shows the working, surfaces dissent, never auto-commits. Use to present any squad/matchday/transfer/chip decision.

2026-06-11120

wc-decision-logger

lyndonkl/claude

Appends FIFA World Cup Fantasy decisions to tracker/decisions-log.md — logging not just what the manager chose but the full OPTION SET they chose from, which option the board recommended, whether the manager overrode it, and the manager's stated reasoning. Also archives the full generation (population → offspring → board → pick) to generations/, and updates the archetype scoreboard (which genotypes' blocks were chosen/won) and the manager's revealed preferences. Append-only; never overwrites. The override rows are the system's most valuable learning signal. Use after the manager picks an option off a board.

2026-06-11120

name

wc-building-block-crossover

description

wc-building-block-crossover — recombine modules, then repair

Inputs

The elite candidate set (from fitness selection), each with its block tags and per-block quality.
Live constraints from tournament-state.md: budget (group $100m / KO $105m), nation cap (3 group, current-phase cap KO), phase.

Workflow

- [ ] 1. For each block slot, rank the elites by that block's quality (per-block fitness contribution)
- [ ] 2. Compose offspring by harvesting the top block from different parents (try a few combinations)
- [ ] 3. REPAIR each offspring to feasibility — cheapest block first, never gut a value block
- [ ] 4. Drop any offspring whose parents' blocks are fundamentally incompatible (repair would break a block)
- [ ] 5. Record block lineage per offspring; emit the feasible offspring

Step 1–2: Cross at block boundaries

offspring_1 = BB1(A1) + BB2(A4) + BB3(A5) + BB4(A2) + BB5(cheapest-feasible)
offspring_2 = BB1(A6) + BB2(A3) + BB3(A5) + BB4(A4) + BB5(...)

Step 3: Repair to feasibility (priority order)

Recombined blocks will usually break BB6 constraints. Repair in this order, preserving value-bearing blocks:

Formation. If no valid XI (1 GK; 3–5 DEF; 2–5 MID; 1–3 FWD) can be fielded from the 15, the recombination is structurally broken → re-pick the offending block from the next-best parent rather than patching individual players.
Nation cap. If a nation exceeds the cap, swap the lowest-xEV offender, preferring to move a BB5 enabler or BB4 differential over a BB1/BB2 value piece.
Budget. If over budget, release funds from BB5 first (downgrade the cheapest enabler), then BB4 (cheaper differential), and only touch BB1/BB2/BB3 if unavoidable — and if so, prefer downgrading one BB1 premium over breaking the BB2 stack (correlation is harder to rebuild than a single captain option).
Matchday spread / dead-minutes bench. Fix last; it's the cheapest lever.

Step 4: Drop incompatible offspring

Step 5: Lineage + emit

For each surviving offspring record:

offspring_id: <id>
blocks:
  BB1_captain_core:   { from: A1, players: [...] }
  BB2_clean_sheet:    { from: A4, players: [...] }
  BB3_mid_engine:     { from: A5, players: [...] }
  BB4_differential:   { from: A2, players: [...] }
  BB5_enabler_bench:  { from: repair, players: [...] }
repair_log: [ "downgraded enabler X→Y for $1.5m", "swapped nation-clash bench Z" ]
feasible: true

Lineage feeds the board ("A1 core + A4 stack + A2 pod") and the archetype scoreboard (which genotypes' blocks keep getting chosen). Hand the offspring to mutation, then diversity.

Guardrails

Whole blocks only. No individual-player crossover — that's the failure mode this skill exists to prevent.
Repair never guts a block. Cheapest-block-first; drop incompatible offspring rather than mangle.
Always emit lineage + repair log. Unexplained offspring can't be presented or learned from.
Produce a variance-diverse offspring set where the parents allow it (a safe fusion and a brave fusion) — the diversity skill checks this next, but don't pre-collapse it here.