Terraform Stacks
Designs and works with Terraform Stacks for composing and deploying infrastructure units.
Skills for coding agent.
192 skills · 161–180
Designs and works with Terraform Stacks for composing and deploying infrastructure units.
Generates and reviews Terraform HCL using HashiCorp’s official style conventions.
Writes and runs Terraform tests using HashiCorp's recommended testing patterns.
Enforces TDD: write failing tests before implementation for features and bug fixes.
Applies Tinybird Engineering guidelines for datasources, pipes, endpoints, SQL, deployments, and testing.
Turns an under-specified decision into a questionnaire someone else can fill in.
Turns the current conversation into a published project-tracker specification without a new interview.
Breaks a plan or conversation into tracer-bullet tickets with clear done criteria.
Sets up or migrates Cloudflare Turnstile bot verification in frontend and backend flows.
Design intelligence for professional web/mobile/desktop UI—layout, hierarchy, and polish guidance while building or reviewing interfaces.
Sets up git worktrees so feature work stays isolated from the current workspace.
Searches a codebase for other instances of a discovered bug’s root cause.
Applies Vercel composition patterns for React component architecture and reuse.
Optimizes Vercel cost and performance for deployed Next.js and related framework projects.
Applies Vercel Engineering React Native/Expo performance rules—lists, animations, navigation, UI, and monorepos.
Forces verification (tests, checks, evidence) before declaring work done.
Plans multi-session work as a shared map of decision tickets so large efforts stay navigable.
Builds interactive web artifacts (HTML/JS widgets) suitable for Claude artifacts-style delivery.
Reviews UI code against Web Interface Guidelines for accessibility, UX, and interface quality.
Improves web performance with Cloudflare-aware guidance—caching, edge, and measurement.
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.