mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 4.8
43d23ef696
Move the operator cheatsheet's copy-paste prompts into per-workflow i8- skills that each route to their authoritative procedure doc, and reduce the cheatsheet to a table index plus a usage paragraph, enforced by a new lint. Add skills for develop, test, quality, refactor, the debug and requirement flows, and commit / pull-request / push-trigger-pull; rename the iteration skills to i8-iterate-* and rename the index to i8-help. Wire the active-listening, dialectic, and robot skills into the flows for clarification, uncertain root causes, and autonomous execution. Drop the Infinito-specific agent aliases (alias.md, INFINITO_ALIAS_MD, the make alias agent section, and the two alias tests); terminal aliases stay. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
915 B
915 B
name, description
| name | description |
|---|---|
| i8-iterate-playwright | Inner-loop iteration on an Infinito.Nexus role-local playwright.spec.js against an already-running stack without redeploying (make compose-playwright / swarm-playwright). Use when writing, debugging, or fixing a Playwright spec for a web-* role. Infinito.Nexus specific. |
Follow the instructions from AGENTS.md, then follow the procedure in docs/agents/action/iteration/playwright.md (relative to the Infinito.Nexus repository root) exactly. That document is the source of truth; this skill only routes you there.
Begin by clarifying every open requirement with the active-listening skill (escalating any root-cause or design question you are not ~99% sure of to the dialectic skill), then work under the robot skill. Ask upfront whether to scope changes to the Playwright spec files only, or also to any other files that cause the tests to fail.