Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

build

Estrelas17

Forks2

Atualizado22 de julho de 2026 às 16:01

Build the mtg-pure Haskell project with cabal/GHC. Use whenever you need to compile the project, verify a change type-checks, do a clean build, or diagnose a build failure. Covers the PowerShell/Windows setup and the ToObjectN code-generation prestep (which you should NOT run proactively — it forces a long recompile).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

thomaseding

thomaseding/mtg-pure

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	build
description	Build the mtg-pure Haskell project with cabal/GHC. Use whenever you need to compile the project, verify a change type-checks, do a clean build, or diagnose a build failure. Covers the PowerShell/Windows setup and the ToObjectN code-generation prestep (which you should NOT run proactively — it forces a long recompile).

Build mtg-pure

Toolchain is installed: GHC 9.10.3 + cabal 3.16 in C:\ghcup\bin.

Use PowerShell (not Git Bash)

Run build commands with the PowerShell tool. Not for caching reasons — both shells reuse the compiled .hi/.o cache equally (see below). PowerShell wins on everything around the build: Git Bash mangles Windows paths (/c/...), sets HOME, and reorders PATH, which bites the sh.exe/configure steps, runghc codegen, and log encoding.

Build

cabal build

First build compiles the whole dep tree + generated ToObjectN modules — many minutes. Run it in the background and check the log.
Incremental rebuilds are very fast. cabal reuses cached .hi/.o object code. A message like mtg-pure ... (configuration changed) is not a recompile — it's just a seconds-long reconfigure (rewrites setup-config / plan.json); your compiled objects are reused untouched. Editing a file ("touch") only recompiles the modules that actually changed.
The configuration changed fingerprint is per-environment, so it ping-pongs between a tool shell and an interactive cmd.exe. Harmless — each side just pays one reconfigure, never a recompile.

Presteps (only if they fail)

ToObjectN code — assume it is already up to date; do NOT regenerate proactively. Files under src/MtgPure/Model/Object/ToObjectN/Instances* are git-ignored + generated. Their content changes only when the ObjectN/OT machinery changes (rare), but regenerating rewrites ~130 files' timestamps, which forces cabal to recompile every one of them — many minutes — even though nothing actually changed. So leave them alone by default.

Only regenerate when an independent build error clearly requires it: the generated files are missing entirely (Instances.hs absent → build fails), or a build error points at a stale/missing ToObject instance after you changed the ObjectN/OT types (see regen-object-code). Then:
```
New-Item -ItemType Directory -Force src\MtgPure\Model\Object\ToObjectN\Instances | Out-Null
Set-Location src; runghc MtgPure/Model/Object/ToObjectN/CodeGen.hs; Set-Location ..
```
cabal update once if the solver says unknown package: ... (empty Hackage index).
If ./configure fails with [Cabal-8011] (needs Unix toolchain), put sh.exe on PATH: prepend C:\Program Files\Git\usr\bin to $env:Path.

Diagnose failures

cabal build 2>&1 | Out-File -Encoding utf8 "$env:TEMP\mtg-build.log" (utf8, or the log reads as garbage), then grep error:|Failed to build|Cabal-[0-9].
Dependency-version / new-warning failures → see update-cabal-toolchain.

Run after building

REPL: cabal repl. Tests/demo are main<Name> entry points — see run-tests.

Mais deste repositório

mesmo repositório

add-card

thomaseding/mtg-pure

Add a new Magic card (or token) definition to mtg-pure. Use whenever the user asks to add, implement, model, or encode an MTG card/token — anything that ends up as a new binding in src/MtgPure/Cards.hs. Handles the DSL body plus the three-place wiring (export, AllCards, cSpell) that is easy to miss by hand.

2026-07-2217

add-combinator

thomaseding/mtg-pure

Add a card-authoring combinator to MtgPure.Model.Combinators in mtg-pure. Use when a card definition needs DSL vocabulary that doesn't exist yet (a new effect/cost/requirement/ability helper), or when card code is reaching for a raw Recursive constructor because no combinator wraps it. Explains the thin-wrapper + As* coercion pattern and how combinators relate to the Recursive DSL.

2026-07-2217

add-engine-fwd

thomaseding/mtg-pure

Add or wire a cross-module engine operation through the Fwd indirection in mtg-pure (the Fwd/Type, Fwd/Impl, Fwd/Api trio). Use when an engine function in one MtgPure.Engine.* module needs to call a function defined in another engine module, when you hit an import cycle between engine modules, or when adding a new primitive the engine exposes. Also covers the Magic visibility/read-write capability types those signatures use.

2026-07-2217

add-game-test

thomaseding/mtg-pure

Add a scripted gameplay test under src/Test/Game/ in mtg-pure (a replayed terminal game that exercises specific cards/interactions). Use when the user wants a test for a card or rules interaction, a regression test for an engine change, or a reproducible game scenario. Covers the test skeleton, the replay-input mini-language, and registering the module.

2026-07-2217

i-am-a-code-chameleon

thomaseding/mtg-pure

Rewrite a specified file so it reads as if Thomas Eding (the project maintainer and sole original author of mtg-pure) wrote it himself. Use whenever the user asks to make a file "look like I wrote it", "match my style", "sound like me", "de-AI-ify", "blend in", "chameleon" a file, or clean up AI-authored or contributed code so it matches the house voice — even if they only say "fix the style of X.hs". Also use as a final pass after generating any substantial new module, when asked to make it indistinguishable from hand-written code.

2026-07-2217

model-round-trip

thomaseding/mtg-pure

Add or change a constructor in the recursive card DSL (MtgPure.Model.Recursive types like Effect, Elect, Cost, Requirement, Condition, abilities) in mtg-pure, keeping the hand-written ConsIndex / Show / Ord instances in lockstep. Use whenever you add, remove, or rename a constructor of a Recursive.* GADT — the project's "a card reproduces its own source" invariant depends on these instances being updated together.

2026-07-2217

name	build
description	Build the mtg-pure Haskell project with cabal/GHC. Use whenever you need to compile the project, verify a change type-checks, do a clean build, or diagnose a build failure. Covers the PowerShell/Windows setup and the ToObjectN code-generation prestep (which you should NOT run proactively — it forces a long recompile).

Build mtg-pure

Toolchain is installed: GHC 9.10.3 + cabal 3.16 in C:\ghcup\bin.

Use PowerShell (not Git Bash)

Build

cabal build

First build compiles the whole dep tree + generated ToObjectN modules — many minutes. Run it in the background and check the log.
Incremental rebuilds are very fast. cabal reuses cached .hi/.o object code. A message like mtg-pure ... (configuration changed) is not a recompile — it's just a seconds-long reconfigure (rewrites setup-config / plan.json); your compiled objects are reused untouched. Editing a file ("touch") only recompiles the modules that actually changed.
The configuration changed fingerprint is per-environment, so it ping-pongs between a tool shell and an interactive cmd.exe. Harmless — each side just pays one reconfigure, never a recompile.

Presteps (only if they fail)

ToObjectN code — assume it is already up to date; do NOT regenerate proactively. Files under src/MtgPure/Model/Object/ToObjectN/Instances* are git-ignored + generated. Their content changes only when the ObjectN/OT machinery changes (rare), but regenerating rewrites ~130 files' timestamps, which forces cabal to recompile every one of them — many minutes — even though nothing actually changed. So leave them alone by default.

Only regenerate when an independent build error clearly requires it: the generated files are missing entirely (Instances.hs absent → build fails), or a build error points at a stale/missing ToObject instance after you changed the ObjectN/OT types (see regen-object-code). Then:
```
New-Item -ItemType Directory -Force src\MtgPure\Model\Object\ToObjectN\Instances | Out-Null
Set-Location src; runghc MtgPure/Model/Object/ToObjectN/CodeGen.hs; Set-Location ..
```
cabal update once if the solver says unknown package: ... (empty Hackage index).
If ./configure fails with [Cabal-8011] (needs Unix toolchain), put sh.exe on PATH: prepend C:\Program Files\Git\usr\bin to $env:Path.

Diagnose failures

cabal build 2>&1 | Out-File -Encoding utf8 "$env:TEMP\mtg-build.log" (utf8, or the log reads as garbage), then grep error:|Failed to build|Cabal-[0-9].
Dependency-version / new-warning failures → see update-cabal-toolchain.

Run after building

REPL: cabal repl. Tests/demo are main<Name> entry points — see run-tests.