mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
3fe2823ce1
1. hillclimb.md: port steps 1-2 (workload grounding before choosing the ruler; harness sensitivity proof before freezing), fold the how-skill grounding into step 1 and rewrite step 4 to reference it. 2. refactoring.md: insert missing step 2 (name the structure the code is missing per principle-model-the-domain), renumber 3-8, and restore the "safety net" framing sentence in the intro. 3. feature.md + poteto-mode SKILL.md: expand the delegation scope and the any-code trigger to choose the organizing structure per principle-model-the-domain. 4. typescript-best-practices: restore the dropped "Real tests" and "Structured telemetry" rules in generic form. 5. poteto-mode Subagents: add the difficulty tiering criteria (judgment vs precisely specified vs trivial mechanical) and the setup-pstack rule override semantics. 6. One-liner tells ported verbatim into bug-fix, runtime-forensics, session-pickup, autonomous-run, and authoring-a-skill. 7. Bug fix: interrogate is "(multi-model adversarial)", not four-model; the default panel is three models. 8. Leak fix: drop the dangling databricks-use-dbt-models skill reference in why/references/sources/databricks.md. Plus: arena cross-judge pool role line in setup-pstack, version bump to 0.11.3.
2.1 KiB
2.1 KiB
Session pickup
You own the resume point. Read the prior trail, don't redo it. For "take over this", "resume this conversation", "continue from ", "you're taking over", "pick up where X left off", a cloud-agent URL handoff, or a pushed branch you're meant to continue.
A pickup is inheritance. The prior agent already paid the cost of reading the code, running the repros, making the design choices. Redoing loses the bias check and burns context. Resist the urge to re-derive; read.
- Locate the prior trail. A local transcript under the active workspace's
agent-transcripts/directory (the system prompt names the path; do not glob across~/.cursor/projects/*/, that crosses workspace boundaries and reads private chats from unrelated projects), a cloud-agent URL, or a pushed branch. Read the metadata overview and last messages first, then scan back for the decision points. Parse a long transcript in a subagent and keep the reduced timeline in the main thread (the principle-guard-the-context-window skill). - Reconstruct operational state. The branch and worktree, what already landed (
git log,git diffagainst the base), the open todos, the decisions made. The prior trail is authoritative input. Resist the bias to re-derive it. - Diff done vs pending. Compare what shipped against what was planned, name the resume point, do not re-run the prior repro or redo completed work. A "let me verify from scratch" pass is the tell that you're treating the trail as untrustworthy when it's actually authoritative.
- Route the remaining work to the matching playbook and pick the verdict: continue the execution, ship a finished recommendation, ratify or override a prior conclusion, or postmortem a failed run. The pickup playbook ends here; the routed playbook owns the rest.
- Verify the inherited claims against the original goal on the real artifact (the principle-prove-it-works skill). A passing prior self-report is not the proof.
Reply: where the prior agent stopped, what you inherited vs redid (ideally nothing redone), the resume point, and the outcome.