integration-pageslisted

# Integration Pages `/integrations/[app]` pages exist to catch one question: "does X work with Y?" That's a buyer-stage question. The person asking is deciding whether to adopt you, and they'll decide in the first screenful. The page must answer concretely and fast, with a working setup in front of them, not a feature list. The bar is Zapier's app-pair pages: the canonical programmatic play, and the reason "programmatic" doesn't have to mean "thin." This skill covers the engineering: manifest design, page generation, information architecture, structured data, and rot prevention. Copywriting formulas and keyword research are out of scope. This is a site architecture problem. ## Before you start Check for `.agents/devtool-context.md` and read it if present (persona and admired references shape the template; stack determines the generation approach). If absent, ask: 1. What are your top 10 to 15 integrations by actual usage or demand, and which 2 or 3 are the ones prospects ask about in sales calls? 2. What does "integration" mean for you: a native connector you maintain, a works-via-API pattern, or a third-party bridge (Zapier/Make)? 3. What's the site stack (Next.js, Astro, Docusaurus, something else), and does it already do static generation from data files? ## Use-case-led pages, or don't bother The single biggest failure mode is the madlib page: "{Product} + {App} = seamless workflows 🚀" repeated 200 times with the noun swapped. Users bounce off it, and search engin