apify-reference-architecture
Production-grade architecture patterns for Apify-powered applications. Use when designing scraping infrastructure, building multi-Actor pipelines, or integrating Apify into a larger system architecture. Trigger with "apify architecture", "apify best practices", "apify project structure", "scraping architecture", "apify system design".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill apify-reference-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Apify Reference Architecture ## Overview Production-ready architecture patterns for applications built on Apify. Three patterns scale from a single scraper to a full-stack integration: 1. **Standalone Actor** — one scraper deployed to the Apify platform. 2. **Multi-Actor Pipeline** — a discover → scrape → transform chain of Actors. 3. **Full-Stack Integration** — an application using Apify as a
What does the apify-reference-architecture skill do?
Production-grade architecture patterns for Apify-powered applications. Use when designing scraping infrastructure, building multi-Actor pipelines, or integrating Apify into a larger system architecture. Trigger with "apify architecture", "apify best practices", "apify project structure", "scraping architecture", "apify system design".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill apify-reference-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
