playtest-edge-hunt

Runs iterative six-area conversation playtests against tmct to find, fix, and ship edge-case fixes.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/polycode-public/the-mechanical-code-talker --skill playtest-edge-hunt-polycode-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playtest-edge-hunt
Source: https://github.com/polycode-public/the-mechanical-code-talker/tree/main/.claude/skills/playtest-edge-hunt
Command: npx skills add https://github.com/polycode-public/the-mechanical-code-talker --skill playtest-edge-hunt-polycode-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually probing a conversational engine for parsing and inference failures is slow and inconsistent. This Skill automates a repeatable playtest loop that walks realistic six-area conversations against a local tmct build, finds edges (unparseable requests or wrong answers), minimizes them, fixes them, and ships each iteration with a version bump. ## Core Features & Use Cases - Structured six-area playtest loop: Walks personal introductions, capability orientation, codebase exploration, teach-and-infer, code-task planning, and research digests in one continuous session per iteration. - Edge minimization and regression testing: Reduces each failing probe to a minimal passing/failing pair, diagnoses the responsible interpretation layer, and ships a named regression test with every fix. - Logged, versioned iterations: Writes a numbered playtests/PLAYTEST_LOG_*.md per run, commits the fix plus log, bumps the patch version, and pushes every iteration. - Use Case: A maintainer says "run 5 playtests" and the Skill serially probes the local tmct CLI against a scratch copy of an example repo, fixes discovered grammar or construction-bank gaps, and ships five versioned commits. ## Quick Start Tell the session to follow the playtest-edge-hunt skill and run a chosen number of playtest iterations against the local tmct build.

Frequently Asked Questions about playtest-edge-hunt

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

FAQPage Schema
How do I run automated playtests against the tmct CLI?▼

Invoke the skill by telling the session to follow playtest-edge-hunt, optionally with an iteration budget like "run 5 playtests". Each iteration pipes a scripted conversation through node bin/tmct.mjs chat against a scratch copy of an example repo, never the committed fixture.

What conversation areas does each playtest iteration cover?▼

Every iteration walks six areas in one session: personal introductions and remembered facts, capability orientation, indexed codebase exploration, teach-and-infer including codebase-grounded facts, code-task planning, and research digests. Specific probe content is varied between runs based on prior logs.

How are discovered edge cases turned into fixes?▼

Each failing probe is minimized word by word into a closest passing and minimal failing pair, which becomes the regression test. The --narrate flag identifies which interpretation layer owns the fix, such as normalize.mjs, grammar.mjs, or the constructions template bank.

Why must playtest sessions use a scratch directory instead of the example repo?▼

A live chat session writes session and provenance state back into the repo's .tmct graph store, which would dirty checked-in fixture files. The skill copies examples like mini-webapp into a mktemp scratch directory and cleans up only that exact path.

When does the playtest loop stop running?▼

The loop stops when the iteration budget is reached (default 10), when two consecutive iterations ship no code change, or when three consecutive iterations end unfixable. On stop it reports edges found, fixed, and unfixable per area plus versions shipped.