Skip to content

Expecho/Agent42 / .claude/skills/gotcha

gotcha

Verified

Capture a non-obvious constraint or a new canonical exemplar in .agentic/gotchas.md, with an evidence path and verified date.

FileKindSize
SKILL.mdskill md1.3 KB
---
name: gotcha
description: Capture a non-obvious constraint or a new canonical exemplar in .agentic/gotchas.md, with an evidence path and verified date.
user-invocable: true
argument-hint: "<the trap or exemplar to record>"
---

# Capture a gotcha or exemplar

Admission test — record it ONLY if all three hold:
1. The code cannot express it (otherwise: add a type, lint rule, or test instead —
   propose that to the user first).
2. An agent without this fact would plausibly do the wrong thing.
3. You can point at a concrete file as evidence.

## Constraint entry

Append under `## Constraints` in `.agentic/gotchas.md`:
- `### <one-line title>` naming the trap
- **Claim:** the constraint + what goes wrong if violated (one or two sentences)
- **Evidence:** repo-relative path you verified THIS session
- **Verified:** today's date

## Exemplar entry

Add a row to the `## Exemplars` table: shape name, path, today's date. An exemplar
must be a current, well-formed instance of the pattern — if the best example has
warts, note them in a constraint entry rather than pointing at a worse file.

## Hygiene

While in the file, scan existing entries touching the same area: if one is now
wrong or the constraint has been lifted, correct or delete it in the same edit.
Entries are cheap; stale entries are expensive.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall