← ClaudeAtlas

siteground-cachelisted

Bypass SiteGround caching (SG CachePress + LiteSpeed) for WordPress development. Adds cache-busting code to child themes for real-time development testing.
aiskillstore/marketplace · ★ 329 · Testing & QA · score 79
Install: claude install-skill aiskillstore/marketplace
# SiteGround Cache Buster Skill Bypass SiteGround caching (SG CachePress + LiteSpeed) for WordPress development. Adds cache-busting code to child themes for real-time development testing. --- ## ⛔ CRITICAL: STAGING ONLY - NEVER PRODUCTION **Claude is FORBIDDEN from deploying to production sites.** | Action | Allowed? | |--------|----------| | Deploy to staging | ✅ YES | | Deploy to production | ❌ **ABSOLUTELY NEVER** | | Read from production | ✅ YES (read-only) | | Write to production | ❌ **ABSOLUTELY NEVER** | **If user asks to deploy to production:** 1. **REFUSE** the request 2. Explain that production deployments must be done manually by the user 3. Offer to deploy to staging instead **Production paths are BLOCKED.** Any path that does NOT contain "staging" is off-limits for writes. --- ## Required Information Before using this skill, Claude will ask for: 1. **FTP/SFTP Credentials** - Hostname (e.g., `ftp.example.com`) - Username - Password - Port (usually 21 for FTP, 22 for SFTP) 2. **Site URLs** - Staging URL (e.g., `https://staging.example.com`) - ~~Production URL~~ (NOT needed - Claude won't deploy there) 3. **Theme Path** - Child theme folder name (e.g., `theme-child`) **Store credentials in project's `CLAUDE.local.md`** (gitignored) for future sessions. --- ## Staging-Only Workflow ``` Local Development → Staging Site → [USER MANUALLY] → Production ↑ ↑ ↑ Claude edits Claude deploys