icfpc-littleman

Solves ICFPC 2026 littleman problems by writing, testing, and optimizing .man programs with the lman simulator.

1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/d-experts/public-icfpc-2026 --skill icfpc-littleman-d-experts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: icfpc-littleman
Source: https://github.com/d-experts/public-icfpc-2026/tree/main/member-06/.agents/skills/icfpc-littleman
Command: npx skills add https://github.com/d-experts/public-icfpc-2026 --skill icfpc-littleman-d-experts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing and optimizing solutions for ICFPC 2026 littleman problems requires a verified local workflow: guessing instruction semantics or checking behavior in the production editor leads to wrong submissions. This Skill enforces a disciplined loop of reading problem specs, writing .man programs, validating them locally with the lman simulator, optimizing footprint and tick scores, and submitting through the team proxy. ## Core Features & Use Cases - Local verification with lman: Runs structural checks, per-tick traces, and full public test suites against the official littleman interpreter wrapper, with coordinate-annotated errors. - Score optimization guidance: Prioritizes footprint reduction over tick reduction for footprint-tick scoring, with BFS-based instruction sequence search and grid-size analysis. - Per-problem organization: Keeps each problem in problems/<slug>/ with named .man variants and a NOTES.md documenting the program, score breakdown, and register transition tables. - Use Case: Ask to solve the triangle problem; the Skill reads the spec via lman, writes problems/triangle/triangle-9x9.man, runs lman test until all public cases pass, checks rank against official standings, and submits via the team proxy. ## Quick Start Ask the assistant to solve the ICFPC littleman problem 'triangle' and verify it locally with lman before submitting through the team proxy.

Frequently Asked Questions about icfpc-littleman

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I solve an ICFPC littleman problem locally?▼

Read the problem with lman problems <slug>, write a .man file under problems/<slug>/, then run lman check, lman run with inputs, and lman test to verify all public cases pass. Submit only after the full test suite succeeds.

How do I optimize a littleman footprint-tick score?▼

Prioritize shrinking the grid footprint since score is max(width,height) squared times average ticks. Check whether the instruction sequence is minimal via BFS over the (A,B) state space, then find the smallest grid that fits it.

What registers and instructions does the littleman language have?▼

Little men have only A and B registers plus BP, and numeric literals overwrite A. Division puts the quotient in A and remainder in B, and pipes move values one cell per tick with arrows at both ends.

Can I verify littleman solutions in the official browser editor?▼

No, this workflow forbids opening the production editor. The lman CLI wraps the official littleman.wasm interpreter, so local verdicts match production exactly, and all verification happens through lman check, run, and test.

Why does my littleman program fail with a coordinate error?▼

Errors like stepping on a non-instruction cell are returned with exact coordinates, such as a little man walking onto a wall or invalid character. Fix the indicated cell, ensure paths are closed, and re-run lman check.