What is multi-zone-architecture?

A way to split one website into several Next.js applications while showing them under one domain. For example, documentation and a blog can be separate applications with different paths.

It helps structure main applications, documentation, blogs, component libraries, and developer tools as separate zones.

It lets teams develop, deploy, and tune parts of a website independently without making users switch between domains.

multi-zone-architecture — Cursor rule for Cursor by lacymorrow

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/lacymorrow/paperclip-hub

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/multi-zone-architecture/github.svg)](https://agentmods.dev/rules/lacymorrow/paperclip-hub/multi-zone-architecture)

Your own site

<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/multi-zone-architecture"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/multi-zone-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/multi-zone-architecture"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/multi-zone-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 2,409 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02409
Opus 5.5	$0.00000	$0.00964
Sonnet 5.5	$0.00000	$0.00482
Haiku 4.5	$0.00000	$0.00241

Measured yesterday against content hash 7efd0ff547ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multi-zone-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/multi-zone-architecture.mdc · 371 lines

How it starts

The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Multi-Zone Architecture Rules

Overview

Multi-zone architecture allows Shipkit applications to be split into multiple Next.js applications while appearing as a single domain to users. This pattern is ideal for:

Scalability: Different teams can work on different zones independently
Performance: Each zone can be optimized for its specific use case
Deployment: Zones can be deployed and updated independently
Technology Freedom: Each zone can use different technologies while maintaining consistency

Zone Configuration Patterns

Standard Zone Structure

domain.com/          → Main app (marketing, dashboard, auth)
domain.com/docs/*    → Documentation zone
domain.com/blog/*    → Blog zone
domain.com/ui/*      → UI component library zone
domain.com/tools/*   → Developer tools zone

Zone Types

1. Main Zone (Primary Application)

Purpose: Core application functionality
Contains: Authentication, dashboard, marketing pages, API routes
Routing: Handles all routes not claimed by other zones
Configuration: Standard Shipkit configuration with multi-zone rewrites

2. Documentation Zone

Purpose: Product documentation, guides, API reference
Features: Search functionality, versioning, navigation tree
Content: MDX files, code examples, tutorials
Optimization: Static generation, fast search indexing

3. Blog Zone

Purpose: Blog posts, announcements, case studies
Features: CMS integration, commenting, social sharing
Content: Articles, author profiles, categories
Optimization: SEO optimization, RSS feeds

4. UI Component Library Zone

Purpose: Component showcase, design system documentation
Features: Interactive component playground, code examples
Content: Component demos, design tokens, usage guidelines
Optimization: Component isolation, visual regression testing

5. Developer Tools Zone

Purpose: Interactive utilities, API explorers, validators
Features: Real-time tools, code generators, testing utilities
Content: Interactive forms, API documentation, utilities
Optimization: Client-side interactivity, tool performance

Read the full file on GitHub · 371 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 371 lines · 0 tokens per session scan A 7efd0ff547ce

Subscribe to this mod's changes

multi-zone-architecture is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,409 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-10.

DevOps and cloud Frontend ai-agents drizzle-orm nextjs paperclip payload-cms plugin-registry

multi-zone-architecture next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
multi-zone-architecturelacymorrow/paperclip-hub	Cursor rule	15	yesterday	MIT	A	0	Cursor
always-push-pritsmemeworks/adhx	Cursor rule	19	5d ago	MIT	A	279	Cursor
codex-premium-website-skillsTheGoat395/Codex-Skills	Cursor rule	137	20d ago	MIT	A	0	Cursor
context-managementvibestackdev/vibe-stack	Cursor rule	8	yesterday	MIT	A	0	Cursor
project-contextvibestackdev/vibe-stack	Cursor rule	8	yesterday	MIT	A	508	Cursor
typescript-coding-styleWebDevPeterGriffin/The-VibeCode-Bible	Cursor rule	42	7d ago	none	A	128	Cursor
javascript-typescript-code-styleWebDevPeterGriffin/The-VibeCode-Bible	Cursor rule	42	7d ago	none	A	88	Cursor