gabrielmoreira c--projects-dashclaw-route-changes
Trigger
Use when an HTTP route or server module needs to be added or changed.
Files to inspect first
C:\Projects\DashClaw\app\api-keys\page.jsC:\Projects\DashClaw\appC:\Projects\DashClaw\app\lib\sessionViewer.mjsC:\Projects\DashClaw\app\api\mcp\route.jsC:\Projects\DashClaw\middleware.js
Steps
- Read each file listed above before any edit.
- Establish a verification baseline before any edit.
- Plan the changes — list edits up front.
- Apply edits in one pass; avoid re-reading the same file ≥ 3 times.
- Run the project's verification command; do not declare done until it passes.
Verification gates
- No new high-confidence repeated-run signals in the session's tool sequence.
- No secret-output guard hits.
What not to do
- Don't introduce new abstractions when an existing one fits.
- Don't add error handling for scenarios that can't happen — only at system boundaries.
- Don't widen scope to a refactor when the trigger calls for a focused change.
Generated by AgentLens from session acec7ebd-b7d3-4e21-8582-f9617e66b654 at 2026-05-12T21:42:09.652Z.
Skill candidate distilled from 3 similar prior session(s). Review and edit before relying on it.