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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-storage-diagExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-storage-diag from charleswiltgen/axiom and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate axiom-storage-diag. Access via /axiom-storage-diag in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
767
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
767
stars
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.
If you see ANY of these:
❌ FORBIDDEN "iOS deleted my files, the file system is broken"
ALWAYS check these FIRST (before changing code):
// 1. Check WHERE file is stored
func diagnoseFileLocation(_ url: URL) {
let path = url.path
if path.contains("/tmp/") {
print("⚠️ File in tmp/ - system purges aggressively")
} else if path.contains("/Caches/") {
print("⚠️ File in Caches/ - purged under storage pressure")
} else if path.contains("/Documents/") {
print("✅ File in Documents/ - never purged, backed up")
} else if path.contains("/Library/Application Support/") {
print("✅ File in Application Support/ - never purged, backed up")
}
}
// 2. Check file protection level
func diagnoseFileProtection(_ url: URL) throws {
let attrs = try FileManager.default.attributesOfItem(atPath: url.path)
if let protection = attrs[.protectionKey] as? FileProtectionType {
print("Protection: \(protection)")
if protection == .complete {
print("⚠️ File inaccessible when device locked")
}
}
}
// 3. Check backup status
func diagnoseBackupStatus(_ url: URL) throws {
let values = try url.resourceValues(forKeys: [.isExcludedFromBackupKey])
if let excluded = values.isExcludedFromBackup {
print("Excluded from backup: \(excluded)")
}
}
// 4. Check file existence and size
func diagnoseFileState(_ url: URL) {
if FileManager.default.fileExists(atPath: url.path) {
if let size = try? FileManager.default.attributesOfItem(atPath: url.path)[.size] as? Int64 {
print("File exists, size: \(size) bytes")
}
} else {
print("❌ File does not exist")
}
}
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
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
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")
}
```
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 persist
let tmpURL = FileManager.default.temporaryDirectory
let fileURL = tmpURL.appendingPathComponent("data.json")
try data.write(to: fileURL) // WILL BE DELETED
// ✅ CORRECT: Use Caches/ for re-generable data
let cacheURL = FileManager.default.urls(
for: .cachesDirectory,
in: .userDomainMask
)[0]
let fileURL = cacheURL.appendingPathComponent("data.json")
try data.write(to: fileURL)
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
// ✅ CORRECT: Handle missing cache gracefully
func loadCachedImage(url: URL) async throws -> UIImage {
let cacheURL = getCacheURL(for: url)
// Try cache first
if FileManager.default.fileExists(atPath: cacheURL.path),
let data = try? Data(contentsOf: cacheURL),
let image = UIImage(data: data) {
return image
}
// Cache miss - re-download
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
648mattpocock/skills
Productivitysame categorypremortem
214parcadei/continuous-claude-v3
Productivitysame categorydeslop
159cursor/plugins
Productivitysame categorytravel-planner
136ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
131pproenca/dot-skills
Productivitysame categorywrite-a-prd
128mattpocock/skills
Productivitysame categoryReviews
4.6★★★★★32 reviews- MMin Thomas★★★★★Dec 24, 2024
I recommend axiom-storage-diag for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- PPratham Ware★★★★★Dec 16, 2024
Keeps context tight: axiom-storage-diag is the kind of skill you can hand to a new teammate without a long onboarding doc.
- XXiao Taylor★★★★★Nov 15, 2024
Solid pick for teams standardizing on skills: axiom-storage-diag is focused, and the summary matches what you get after install.
- SSakshi Patil★★★★★Nov 7, 2024
Registry listing for axiom-storage-diag matched our evaluation — installs cleanly and behaves as described in the markdown.
- CChaitanya Patil★★★★★Oct 26, 2024
axiom-storage-diag reduced setup friction for our internal harness; good balance of opinion and flexibility.
- XXiao Martin★★★★★Oct 6, 2024
axiom-storage-diag has been reliable in day-to-day use. Documentation quality is above average for community skills.
- XXiao Malhotra★★★★★Sep 25, 2024
axiom-storage-diag fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- PPiyush G★★★★★Sep 17, 2024
I recommend axiom-storage-diag for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- SSophia Mensah★★★★★Sep 1, 2024
axiom-storage-diag is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- SSophia Flores★★★★★Aug 20, 2024
Keeps context tight: axiom-storage-diag is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 32
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.