backnotprop

backnotprop/prompt-tower

Instructions file

Claude Code instructions for backnotprop/prompt-tower, covering development guide, architecture overview, source directory structure, /api and /models.

backnotprop/pstack

Agent

A deranged comment-hater that savors deletion and condemns workaround code.

backnotprop/pstack

Agent

Routing target for /poteto-mode and any request for poteto's style. Resume an existing poteto-agent for the conversation rather than spawning a sibling. Reads the poteto-mode skill's SKILL.md in full before any work, including its inline Principles index. Substituting generalPurpose skips that read and drifts.

backnotprop/pstack

Skill Claude CodeCodex

Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.

backnotprop/pstack

Skill Claude CodeCodex

Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

backnotprop/pstack

Skill Claude CodeCodex

Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

backnotprop/pstack

Skill Claude CodeCodex

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

backnotprop/pstack

Skill Claude CodeCodex

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

backnotprop/pstack

Skill Claude CodeCodex

Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.

backnotprop/pstack

Skill Claude CodeCodex

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

backnotprop/pstack

Skill Claude CodeCodex

Restate the last message in plain human language, with no jargon.

backnotprop/pstack

Skill Claude CodeCodex

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.

backnotprop/pstack

Skill Claude CodeCodex

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no…

backnotprop/pstack

Skill Claude CodeCodex

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for…

backnotprop/pstack

Skill Claude CodeCodex

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

backnotprop/pstack

Skill Claude CodeCodex

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

backnotprop/pstack

Skill Claude CodeCodex

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

backnotprop/pstack

Skill Claude CodeCodex

Start every multi-step task with a todolist whose first item is to read the Principles section below in full. The principles ground every trigger here. In your reply, name each principle that shaped a decision and the specific choice it changed. A citation with no decision behind it means you skipped its leaf skill…

backnotprop/pstack

Skill Claude CodeCodex

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

backnotprop/pstack

Skill Claude CodeCodex

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

backnotprop/pstack

Skill Claude CodeCodex

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

backnotprop/pstack

Skill Claude CodeCodex

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

backnotprop/pstack

Skill Claude CodeCodex

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

backnotprop/pstack

Skill Claude CodeCodex

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.