Codebase analysis and impact mapping. Use when reviewing, modifying, or understanding user code where the blast radius spans multiple files. Provides code-review-graph MCP integration and grep-fallback protocols for computing change impact.
Cross-session task continuation and handoff. Use when resuming incomplete work from a previous session, after context compaction, or when a task spans multiple sessions. Provides structured handoff fingerprints and resume protocols.
Debug-first diagnosis protocol for unknown failures. Use when the cause is unknown, a bug needs diagnosis before fixing, or the user asks 'what's wrong' without requesting a fix. Provides structured hypothesis-probe-decision loop with evidence tracking.
Remote, stateful, or embedded system operations. Use when working with routers, OpenWrt, embedded Linux, VMs, containers, remote servers, or any target where a restart or 'ready' label is not proof of function. Provides management path preservation and verification protocols.
FP self-evolution: auto-capture lessons from tasks, nudge reflection every 10 turns, update MEMORY.md and USER.md across projects. Use when any task completes or after a significant error, correction, or complex workflow (5+ tool calls).
Use automatically when the user's goal is engineering work (build, change, diagnose, review, test, operate, or plan software, repositories, infrastructure, or agent tooling), or when explicitly invoked with "FP:" or "$fp". Do not use for casual conversation or other non-engineering goals.
Instructions for MiaoY0uShan/FP: Use this broadly applied file only as a lightweight gate. When the user's goal is engineering work or explicitly invokes FP:/$fp, read fp/SKILL.md as the canonical router and load only route-relevant resources; otherwise keep the full router dormant. Lock the goal — never substitute a…