Menü
Compact the current conversation into a handoff document for another agent to pick up.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Consolidated compressed-communication skill. Use for caveman mode, terse mode, reduced-token replies, /caveman intensity levels, Wenyan variants, or /caveman:compress memory-file compression. Includes both live response style and natural-language file compression into caveman format.
Use when writing or reviewing code in any language. Covers typed-language rules (TypeScript, Python, Go), naming conventions, file organisation, error handling, import ordering, and universal quality rules. Read project conventions first to identify the stack, then apply only the relevant language sections.
Consolidated UI/UX design skill for product-fit direction, new interface implementation, redesigns, animation and micro-interactions, GSAP/ScrollTrigger choreography, style modes such as soft/minimalist/brutalist, UX critique, UI audits, UI performance optimization, Google Stitch DESIGN.md generation, and complete output enforcement. Use for any request naming design-intelligence, redesign, animate, gsap, soft, minimalist, brutalist, stitch, critique, ui-audit, ui-optimize, output, or any UI/UX/frontend visual work.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Use when writing SQL or migrations, designing schemas, troubleshooting slow queries, implementing Row Level Security, tuning connection pooling, or reviewing database changes. Based on Supabase-leaning Postgres practice.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the /memory/handoff directory of the current workspace, if that folder is not there make sure to create it in /docs/handoff and delete it after the task is done.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
