0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-07 19:32:17 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.7 1fa2a50c1b docs(agents/cheatsheet): tighten Web Development Iteration prompt; drop trailing Use mode /caveman ultra from every prompt

Web Development Iteration prompt now spells out the in-container loop
explicitly: for every failing Playwright test, follow the inner-loop
procedure in role.md together with playwright.md; before every
redeploy run `make exec` and `make run` against the live stack and
fully fix and inspect every failure in-container; the next deploy
iteration only starts once every error is resolved and the fix is
empirically verified. Adds explicit prohibitions on commit/push and
on `ask`-mode approvals, and forbids premature termination — the
iteration is finished only when every role is green end-to-end.

Strips the `Use mode /caveman ultra` postscript from every other
prompt: it was an experimental mode marker that no longer applies
and only added noise. The prompts now stop at the standard
`act autonomously …` sentence.

Reformatted to comply with documentation.md: complete sentences
instead of semicolon chains, no em-dash thought breaks, RFC 2119
keywords used consistently.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-17 19:29:36 +02:00

8.4 KiB

Raw Blame History

Cheatsheet 📋

Copy-paste prompt templates the operator can hand to an agent to kick off a workflow. Each prompt routes the agent to its authoritative procedure file; this page is a navigational aid only and MUST NOT be treated as source of truth.

Replace every <placeholder> before sending.

Every prompt below instructs the agent to first clarify all open requirements through active listening, then act autonomously through to completion with as few follow-up questions as possible.

Selection Matrix 🧭

Situation	Use
Building a new feature, app, or larger change	Development
Fixing or evolving a single web app role with the deploy/test loop	Web Development Iteration
Running or validating tests for a specific scope	Testing
Writing or updating a Playwright spec for a `web-*` role	Playwright Tests
Cleaning up code, docs, or roles after a change	Refactor and Optimize
A GitHub Actions / CI run failed and needs triage	Pipeline Debugging
A local deploy is failing on the host	Local Deploy Debugging
Operator placed a `.log` or `job-logs.txt` file in the workdir for ad-hoc inspection	Log File Inspection
Staged changes are ready to be committed	Commit
A branch is ready to be opened as a pull request	Pull Request Creation
A branch needs to be pushed, validated via manual CI, and transitioned through the draft → ready-for-review cycle	Push, Trigger, Pull
A new requirement needs to be written	Requirement Creation
An existing requirement file needs to be implemented end to end	Requirement Implementation

Development 🧱

For any change with a documented acceptance scope, Requirement Implementation is the preferred entry point; use this prompt only when no requirement file exists or applies.

Follow the instructions from AGENTS.md, develop <feature-or-app> by following the procedure in docs/agents/action/develop.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: develop.md

Web Development Iteration 🔁

For any change with a documented acceptance scope, Requirement Implementation is the preferred entry point; use this prompt only when no requirement file exists or applies.

Follow the instructions from AGENTS.md, iterate on web app role <role> by following the procedure in docs/agents/action/iteration/role.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. For every failing Playwright test, follow the inner-loop procedure in docs/agents/action/iteration/role.md together with the procedure in docs/agents/action/iteration/playwright.md. Before every redeploy you MUST run `make exec` and `make run` against the live stack and fully fix and inspect every failure in the container. A new deploy iteration MUST NOT start until every error is resolved and the fix has been empirically verified in-container. You MUST NOT use any commit command, push command, or any command that would require an `ask`-mode approval. You MUST NOT stop the iteration early under any circumstance. Premature termination is explicitly forbidden. The iteration is finished only when every role is green end-to-end.

SPOT: Role Loop

Testing ✅

Follow the instructions from AGENTS.md, run and validate tests for <scope> by following the procedure in docs/agents/action/testing.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: testing.md

Playwright Tests 🎭

Follow the instructions from AGENTS.md, write or update the Playwright test for role <role> by following the procedure in docs/agents/action/iteration/playwright.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible. Ask upfront whether to scope changes to the Playwright files only or also to any other files that cause the tests to fail.

SPOT: playwright.md

Refactor and Optimize ♻️

Follow the instructions from AGENTS.md, refactor and optimize the affected files by following the procedure in docs/agents/action/refactor.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: refactor.md

Pipeline Debugging 🛠️

Follow the instructions from AGENTS.md, triage the failing CI run at <github-actions-run-url> by following the procedure in docs/agents/action/debug/pipeline.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: pipeline.md

Local Deploy Debugging 🧰

Follow the instructions from AGENTS.md, debug the failing local deploy of role <role> by following the procedure in docs/agents/action/debug/local.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: local.md

Log File Inspection 🔍

Follow the instructions from AGENTS.md, inspect the log file <path-to-log> by following the procedure in docs/agents/action/debug/log.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: log.md

Commit 💾

Follow the instructions from AGENTS.md, commit the staged changes by following the procedure in docs/agents/action/commit.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: commit.md

Pull Request Creation 📤

Follow the instructions from AGENTS.md, open a pull request for the current branch by following the procedure in docs/agents/action/pull-request.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: pull-request.md

Push, Trigger, Pull 📡

Follow the instructions from AGENTS.md, push branch <branch>, run it through the manual-CI draft cycle, and transition the PR to ready-for-review by following the procedure in docs/agents/action/push-trigger-pull.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: push-trigger-pull.md

Requirement Creation ✍️

Follow the instructions from AGENTS.md, create a new requirement for <topic> by following the procedure in docs/contributing/requirements.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.

SPOT: requirements.md

Requirement Implementation 🚀

If no requirement file exists yet for the work, run Requirement Creation first to produce one.

Follow the instructions from AGENTS.md, implement requirement docs/requirements/<NNN-topic>.md by following the procedure in docs/agents/action/requirements.md. Begin by clarifying every open requirement through active listening, then act autonomously through to completion with as few follow-up questions as possible.