deployment

deployment is a cursor rule for Cursor from lacymorrow/paperclip-hub. It costs 0 tokens per session (635 once invoked), scanned A, original, MIT.

Deployment guidelines are instructions for publishing and configuring a multi-zone web application, where separate applications work together under one domain.

In plain words
What is it for?
Use them to set up separate Vercel projects, environment files, domains, databases, authentication, monitoring, and zone-specific behavior.
Why use it?
They reduce configuration mistakes between local, test, and production environments, including missing variables, broken navigation, and inconsistent authentication.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them to set up separate Vercel projects, environment files, domains, databases, authentication, monitoring, and zone-specific behavior.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/lacymorrow/paperclip-hub/deployment
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.

agentmods badge for deployment

README.md
[![agentmods](https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/deployment/github.svg)](https://agentmods.dev/rules/lacymorrow/paperclip-hub/deployment)
Your own site
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/deployment"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/deployment/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.

agentmods 80×15 button for deployment

Your own site · 80×15
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/deployment"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/deployment.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 635 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00635
Opus 5.5 $0.00000 $0.00254
Sonnet 5.5 $0.00000 $0.00127
Haiku 4.5 $0.00000 $0.00064

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

Security

Grade A, and why

deployment 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/deployment.mdc · 120 lines

How it starts

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

Deployment Best Practices

Multi-Zone Deployment

Zone Deployment Strategy

  • Deploy each zone as separate Vercel project
  • Use consistent naming: main-shipkit, docs-shipkit, blog-shipkit, ui-shipkit, tools-shipkit
  • Configure environment variables pointing to zone URLs
  • Assign custom domain to main application
  • Test cross-zone navigation and functionality

Zone Environment Configuration

  • Main app contains zone domain environment variables
  • Each zone has its own environment configuration
  • Use separate databases or shared database per zone requirements
  • Configure authentication to work across zones
  • Set up monitoring for each zone independently

Zone-Specific Optimizations

  • Documentation zone: Static generation, search optimization
  • Blog zone: ISR for posts, SEO optimization
  • UI zone: Component isolation, visual regression testing
  • Tools zone: Client-side rendering, real-time features

Environment Setup

  • Use .env.local for local development
  • Use .env.production for production
  • Use .env.test for testing
  • Never commit environment files
  • Document all required variables
  • Use strong naming conventions
  • Validate environment variables at startup

Docker Configuration

  • Use multi-stage builds
  • Optimize layer caching
  • Include only necessary files
  • Use appropriate base images
  • Set proper environment variables
  • Configure health checks
  • Document all configurations

CI/CD Pipeline

  • Automate build process
  • Run tests before deployment
  • Check code quality
  • Scan for vulnerabilities
  • Use proper caching
  • Implement proper rollbacks
  • Monitor deployment status

Production Deployment

  • Use proper build optimization
  • Enable proper caching
  • Configure proper headers
  • Set up monitoring
  • Configure logging
  • Set up alerts
  • Plan for scaling

Infrastructure

  • Use infrastructure as code
  • Implement proper monitoring
  • Set up logging
  • Configure backups
  • Plan for disaster recovery
  • Document architecture
  • Monitor costs

Read the full file on GitHub · 120 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.

  1. yesterday First seen · 120 lines · 0 tokens per session scan A 2313fb4795c9

Subscribe to this mod's changes

deployment 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 635 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.

Related

deployment compared with cursor rules from other repositories

deployment next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
deploymentlacymorrow/paperclip-hubCursor rule15yesterdayMITA0Cursor
vercel-cligiselles-ai/giselleCursor rule560yesterdayApache-2.0A5Cursor
infrastructurefirst-fluke/fullstack-starterCursor rule2262d agoMITA0Cursor
always-push-pritsmemeworks/adhxCursor rule195d agoMITA279Cursor
supabase-edgeshipkit-io/bonesCursor rule21yesterdaynoneA0Cursor
00-cloud-agent-mandatoryfirtoz/cf-multiworker-starter-kitCursor rule1120d agononeA4Cursor
aws-vpcjimmypocock/cursor-rulesCursor rule81y agoMITA6Cursor