Coding standards, frameworks, refactoring, and code review (15.4K skills)
Investigate slow PostgreSQL queries in Paperclip, reproduce their cost locally, and implement measured fixes. Compare performance and returned results, add regression coverage, and carry pull requests through review and automated checks.
Build and test two-way integrations between Paperclip and external bots such as Dot. Cover invitations, identity, permissions, task delivery, recovery, and Cloud deployment, with evidence from real provider accounts and deployed environments.
Maintain Paperclip Storybook examples by comparing them with shipped interfaces and the feature map. Update fixtures, classifications, and catalog references while preserving stable links and clearly identifying current examples, prototypes, historical work, and cases needing review.
Prepare user-facing changelogs for stable Paperclip releases from commits, change records, and merged pull requests. Group related changes, identify breaking changes, and explain upgrade actions using the beta version selected for release.
Prepare Paperclip changes for a pull request by organizing commits, updating the branch, writing the description, addressing automated review feedback, and checking tests and CI before reporting the result for handoff.
Track pull requests opened by a Paperclip instance, explain their purpose, and assess whether their latest changes are ready to merge. Dispatch preparation work for unresolved problems and publish an evidence-based report without merging anything.
Produces detailed HTML or Markdown reports on pull requests, branches, or large code contributions. It explains how the system works, ranks concrete findings, compares designs when needed, and recommends whether and how to merge the changes.
Create external Paperclip plugins using command-line tools. Scaffold a package, install it into a local Paperclip instance, rebuild as you edit, and check types, tests, and builds before reporting the plugin’s status.
Prepare completed changes for a GitHub pull request with organized commits, a clear title and description, verification evidence, screenshots for interface changes, and explicit replies to review comments through merge readiness.
Build or modify adapters that connect Paperclip to AI agent runtimes. Covers server execution, configuration forms, terminal output, session persistence, and environment checks for CLI agents, HTTP endpoints, and custom processes.
Turn an idea, post, or task into a skill for the Paperclip catalog. Search for existing skills first, then reference, adapt, or author one, add worked examples where applicable, validate the catalog, and prepare a pull request.
Research MCP connections, which let agents use external tools, and vendor integrations for Paperclip. Produce an evidence-backed planning pull request, obtain human approval for its exact revision, then implement and verify each approved connection separately.
Guide development of new interaction cards in Paperclip issue threads, such as approvals or structured questions. Covers shared data definitions, server behavior, interface states, CLI and MCP support, plugin helpers, documentation, and tests.
Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.
Design, implement, and review interface animation, from button feedback to drag gestures. When measurement tools are available, analyze recordings to reconstruct timing, easing—how speed changes—and spring motion, then produce code and an implementation specification.
Build interactive web motion from videos or image sequences, controlled by scrolling, pointer movement, dragging, or state changes. It covers media preparation, timeline compilation, playback controllers, delivery format selection, and checks on the target page.
Implement purposeful animations for existing interfaces or an agreed UI brief. It selects motion based on purpose and usage frequency, then handles timing, interrupted interactions, exits, and reduced-motion preferences while reusing the project’s tools and design values.
Create a reusable snapshot of an existing code repository, covering files, imports, components, and routes. It gives agents a shared reference for migration and editing work without repeatedly scanning the directory tree.
Prepare a structured plan for a code rewrite spanning multiple files. It records file responsibilities, ordered changes, and risk levels so later editing, diff review, and build testing can follow a clear, reviewable scope.
Review accumulated code edits through a patch and a readable file-by-file summary. An interactive choice screen captures acceptance, rejection, or partial approval, records the decision, and rolls back rejected changes within the planned scope.
Apply a code rewrite plan one step at a time through small, reviewable edits. Keep changes within assigned files, check risk restrictions, and record each step’s files, change summary, rationale, and completion status.
Build a single HTML visualizer for particles, fractals, simulations, or data. It moves heavy calculations into a Web Worker, a background browser process, and draws on a canvas while targeting smooth 60fps rendering.
Summarize the past 24 hours of GitHub pull requests, review requests, issues, CI runs, and merges in a daily briefing. The GitHub-style page highlights pending reviews and failed automated checks.
Reproduce an existing website locally by examining source code, collecting assets, and checking browser behavior. Follow paths for static, framework-based, or graphics-heavy sites, then compare the result with the original and replace content as needed.