Use when observations from different surfaces appear to disagree and the agent must keep each observation in its observed form before explaining causes: UI vs behavior, logs vs state, metrics vs reports, tool output vs user-visible result.
Use when writing durable public design prose for RFCs, proposals, architecture notes, and canonization summaries where the document must serve users, implementers, maintainers, educators, and future readers.
Background guidance for all plugin work: keep language inside the work, focus on what we're doing, and use precise and meaningful language that stays attached to the work underway.
Use when helping the user articulate their own thinking — when they have insight they haven't fully formed, or when the task requires the user to see something the agent can point to but not resolve.
Use when selecting among locally valid project moves by relating them to a durable project thesis, or when new evidence should revise the route while the user's situated judgment remains authoritative about what the project is for.
Restructure mature code so it directly expresses what the system has learned through use and evolution, preserving meaningful constraints and distinctions while removing historical residue and accidental complexity.
★not rated 10 1mo agoA36 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: