714 skills · sorted by relevance
Review Claude Code settings for duplicate skills, outdated memory files, unused permissions, and other clutter. The workflow presents evidence for each candidate, requests individual approval, and records reversible cleanup actions.
Implement and review GSAP animations in Vue, Nuxt, Svelte, and SvelteKit. It explains when to start animations, how to limit element selection to one component, and how to clean up when that component is removed.
Audit account settings, privacy pages, and API routes for a complete data deletion flow. Check browser storage cleanup, server deletion requests, and user confirmation, then identify missing pieces and guide implementation.
Find and fix JavaScript memory leaks that accumulate as people use a web app. Review event listeners, timers, retained page elements, and outdated asynchronous tasks, then explain how to verify cleanup in the browser.
Review how tests use mocks, substitutes for external services or resources. Identify excessive mocking and missing cleanup, suggest more realistic tests, and check whether automated checks consistently catch problems and prevent regressions.
Improve GSAP animation performance by reviewing animated properties, browser layout work, and simultaneous updates. Use transforms, grouped updates, reusable animations, and targeted cleanup to reduce stuttering in lists, mouse followers, and scroll effects.
Build GSAP animations in Vue, Svelte, and related frameworks with clear setup and cleanup patterns. Scope element selection to each component, start animations after elements exist, and remove animations when the component is destroyed.
Helps agents build the foundations of a Three.js scene, including cameras, rendering settings, object grouping, and movement. Code examples cover coordinate systems, resizing, animation timing, resource cleanup, and basic performance improvements for browser-based 3D projects.
Audit a codebase across nine areas, including architecture, tests, security, and documentation. Produces TECH_DEBT_AUDIT.md with source locations, severity ratings, estimated repair effort, and prioritized recommendations to help plan maintenance work.
Guides code cleanup and restructuring by mapping dependencies, assessing test coverage, and planning small changes. Supports tasks such as extracting functions or renaming symbols, with checks after each step and recovery when verification fails.
Audit a Claude Code setup for installation problems, broken settings, unused extensions, and duplicated instructions. It reviews local usage evidence, recommends cleanup, and applies approved fixes, with separate confirmation for permission changes.
Review code changes in a diff, pull request, branch, or file path to identify bugs and cleanup opportunities. Findings include file locations and concrete failure scenarios, with options to apply fixes or post comments.
Investigate Cherry Studio code to identify unused behavior, duplicated state, and unnecessary abstractions. Turn a few well-supported findings into cleanup proposals that document current consumers, removal scope, risks, and observable acceptance criteria.
Build Python features that identify a speaker’s intent and extract details such as names from conversation text using Azure. Get guidance on request structure, authentication, client cleanup, and exception handling.
Write and review Rust, C++, and C code with safer memory and resource management. Covers ownership, automatic cleanup tied to scope, and smart pointers to help prevent leaks, double frees, and access to freed memory.
Review AI-generated code for problems hidden behind successful runs. Check failure handling, resource cleanup, unusual inputs, nonexistent dependencies, and departures from project conventions to identify missing safeguards before merging or accepting the work as complete.
Prepare spreadsheet data for analysis by finding extra spaces, inconsistent capitalization, numbers stored as text, mixed date formats, and duplicates. Review proposed fixes, apply traceable formula-based changes, and compare results before and after cleanup.
Set up and maintain an OpenViking server, from configuration and installation to startup, shutdown, and health checks. Includes troubleshooting through logs and a data cleanup procedure with backups and explicit deletion confirmation.
Write and improve C# unit tests with MSTest 3.x/4.x. Covers assertions that check expected results, tests with multiple input sets, asynchronous setup, cleanup, and test organization, with guidance on APIs that differ between versions.
Write C# unit tests with TUnit using clear test structure, asynchronous checks, and multiple input cases. Get guidance on setup and cleanup, execution controls, test organization, and converting existing xUnit tests to TUnit.
Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.
Break a large development brief into ordered goals and save plans, progress events, blockers, and evidence in the repository. Coordinate Claude Code sessions through handoff instructions, with final completion requiring cleanup, verification, and code review evidence.
Collect and review SGLang startup logs to identify unnecessary output and trace its source. Get saved logs and specific cleanup proposals while preserving useful diagnostics, with runtime changes left for user approval.
Write and register SGLang unit and end-to-end tests, from choosing models and file locations to reusing server fixtures. Follow project rules for meaningful assertions, CI registration, dependency mocking, and safe server cleanup after tests.