Problem Framing Canvas
Frames problems on a canvas so teams share the same problem, users, and constraints before solutions.
Skills for coding agent.
192 skills · 121–140
Frames problems on a canvas so teams share the same problem, users, and constraints before solutions.
Optimizes prompts and agent instructions for clarity, constraints, and better outcomes.
Applies property-based testing to find edge-case bugs with generative properties.
Builds a throwaway prototype to answer a design or state-model question before implementation.
Deploys Flask, Django, and FastAPI applications to Azure App Service on Linux.
Applies Vercel Engineering’s React/Next.js performance rules (waterfalls, bundles, server/client fetching, rerenders).
Implements React View Transitions for smooth navigations and UI state changes.
Processes code-review feedback thoughtfully before implementing changes—especially pushy or unclear notes.
Audits and upgrades existing sites/apps to premium quality without breaking functionality.
Transforms monolithic Terraform into reusable modules using HashiCorp module design principles.
Routes Remotion video-in-React work to the right Remotion skill patterns and best practices.
Transcribes, displays, and animates captions inside Remotion compositions.
Scaffolds and authors new Remotion compositions and video projects in React.
Adds interactive Remotion player behaviors—scrubbing, inputs, and dynamic props.
Renders Remotion videos with the right CLI, Lambda, or CI pipeline settings.
Previews Remotion videos in Studio using the recommended local workflow.
Requests a thorough code review when finishing features or before merge to verify requirements.
Resolves in-progress Git merge and rebase conflicts through a clear sequence of file and history checks.
Reviews UI animations for timing, easing, and design-engineering craft (Emil Kowalski style).
This skill reviews a diff or pull request for correctness, readability, architecture, speed, and security. It works for code from a person or an agent, and also checks change size and the change description before the code is merged.
An agent skill is a portable pack of instructions that gives an agent specialized know-how for a task. In the open Agent Skills format (from Anthropic, now widely adopted), that pack is a folder with a SKILL.md file and optional scripts or references the agent can load when needed.
SKILL.md is the required main file in a skill folder. It starts with simple metadata (name and description) plus the instructions. Agents use the metadata to decide when a skill applies, then read the full file — and any linked files — only when the task needs them.
Open the listing and follow the source link — usually a GitHub SKILL.md. Install with your agent’s skill flow, or add the repo the way that product documents. When this site shows the skill text, Copy is on the page.
A prompt is paste-in text for one chat turn (or a short thread). A skill is a reusable file pack an agent can discover and load across a task, sometimes with code attached. Prompts live in the prompt directory; skills usually live on GitHub and we link out.
Each skill uses one sitewide category — the same set as the rest of the directory (Coding agent, Marketing, Document intelligence, and so on). Hops filter to categories that already have skills.
Yes. Submit with a public GitHub SKILL.md URL, or attach a skill as part of a method on a use case. An editor reviews it before it appears here.