Fetches axiom-storage-diag from charleswiltgen/axiom and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/axiom-storage-diag
Restart Cursor to activate axiom-storage-diag. Access via /axiom-storage-diag in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Core principle 90% of file storage problems stem from choosing the wrong storage location, misunderstanding file protection levels, or missing backup exclusions—not iOS file system bugs.
The iOS file system is battle-tested across millions of apps and devices. If your files are disappearing, becoming inaccessible, or causing backup issues, the problem is almost always in storage location choice or protection configuration.
Red Flags — Suspect File Storage Issue
If you see ANY of these:
Files mysteriously disappear after device restart
Files disappear randomly (weeks after creation)
App backup size unexpectedly large (>500 MB)
"File not found" after app background/foreground cycle
Files inaccessible when device is locked
Users report lost data after iOS update
Background tasks can't access files
❌ FORBIDDEN "iOS deleted my files, the file system is broken"
iOS file system handles billions of files daily across all apps
System behavior is documented and predictable
99% of issues are location/protection mismatches
Mandatory First Steps
ALWAYS check these FIRST (before changing code):
// 1. Check WHERE file is storedfuncdiagnoseFileLocation(_ url:URL){let path = url.path
if path.contains("/tmp/"){print("⚠️ File in tmp/ - system purges aggressively")}elseif path.contains("/Caches/"){print("⚠️ File in Caches/ - purged under storage pressure")}elseif path.contains("/Documents/"){print("✅ File in Documents/ - never purged, backed up")}elseif path.contains("/Library/Application Support/"){print("✅ File in Application Support/ - never purged, backed up")}}// 2. Check file protection levelfuncdiagnoseFileProtection(_ url:URL)throws{let attrs =tryFileManager.default.attributesOfItem(atPath: url.path)iflet protection = attrs[.protectionKey]as?FileProtectionType{print("Protection: \(protection)")if protection ==.complete {print("⚠️ File inaccessible when device locked")}}}// 3. Check backup statusfuncdiagnoseBackupStatus(_ url:URL)throws{let values =try url.resourceValues(forKeys:[.isExcludedFromBackupKey])iflet excluded = values.isExcludedFromBackup {print("Excluded from backup: \(excluded)")}}// 4. Check file existence and sizefuncdiagnoseFileState(_ url:URL){ifFileManager.default.fileExists(atPath: url.path){iflet size =try?FileManager.default.attributesOfItem(atPath: url.path)[.size]as?Int64{print("File exists, size: \(size) bytes")}}else{print("❌ File does not exist")}}
Decision Tree
Files Disappeared
Files missing? → Check where stored
├─ Disappeared after device restart
│ ├─ Was in tmp/? → EXPECTED (tmp/ purged on reboot)
│ │ → FIX: Move to Caches/ or Application Support/
│ │
│ ├─ Was in Caches/? → System purged (storage pressure)
│ │ → FIX: Move to Application Support/ if can't be regenerated
│ │
│ └─ Protection level .complete? → Inaccessible until unlock
│ → FIX: Wait for unlock or use .completeUntilFirstUserAuthentication
│
├─ Disappeared randomly (weeks later)
│ ├─ In Caches/? → System purged under storage pressure
│ │ → EXPECTED if re-downloadable
│ │ → FIX: Re-download when needed, or move to Application Support/
│ │
│ └─ In Documents or Application Support/?
│ → Check if user deleted app (purges all data)
│ → Check iOS update (rare, but check migration path)
│
└─ Only some files missing
→ Check isExcludedFromBackup + iCloud sync
→ Check if file names have special characters
→ Check file permissions
Files Inaccessible
Can't access file?
├─ Error: "No permission" or NSFileReadNoPermissionError
│ ├─ Device locked? → Check file protection
│ │ └─ .complete protection? → Wait for unlock
│ │ → FIX: Use .completeUntilFirstUserAuthentication
│ │
│ └─ Background task accessing? → .complete blocks background
│ → FIX: Change to .completeUntilFirstUserAuthentication
│
├─ File exists but read returns empty/nil
│ └─ Check actual file size on disk
│ → May be zero-byte file from failed write
│
└─ File exists in debugger but not at runtime
→ Check if using wrong directory (Documents vs Caches)
→ Check URL construction
Backup Too Large
App backup > 500 MB?
├─ Check Documents directory size
│ └─ Large files (>10 MB each)?
│ ├─ Can they be re-downloaded? → Move to Caches + isExcludedFromBackup
│ └─ User-created? → Keep in Documents (warn user if >1 GB)
│
├─ Check Application Support size
│ └─ Downloaded media/podcasts?
│ → Mark isExcludedFromBackup = true
│
└─ Audit backup with code:
```swift
func auditBackupSize() {
let docsURL = FileManager.default.urls(
for: .documentDirectory,
in: .userDomainMask
)[0]
let size = getDirectorySize(url: docsURL)
print("Documents (backed up): \(size / 1_000_000) MB")
}
```
Common Patterns by Symptom
Pattern 1: Files in tmp/ Disappear
Symptom: Temp files missing after restart or even during app lifecycle
Cause: tmp/ is purged aggressively by system
Fix:
// ❌ WRONG: Using tmp/ for anything that should persistlet tmpURL =FileManager.default.temporaryDirectory
let fileURL = tmpURL.appendingPathComponent("data.json")try data.write(to: fileURL)// WILL BE DELETED// ✅ CORRECT: Use Caches/ for re-generable datalet cacheURL =FileManager.default.urls(for:.cachesDirectory,in:.userDomainMask
)[0]let fileURL = cacheURL.appendingPathComponent("data.json")try data.write(to: fileURL)
Pattern 2: Caches Purged, Data Lost
Symptom: Downloaded content disappears weeks later
Cause: Caches/ is purged under storage pressure (expected behavior)
Fix: Either re-download on demand OR move to Application Support if can't be regenerated
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
