Purpose: Comprehensive reference for storage pressure, purging policies, disk space, and URL resource values
Works with
Availability: iOS 5.0+ (basic), iOS 11.0+ (modern capacity APIs)
Context: Answer to "Does iOS provide any way to mark files as 'purge as last resort'?"
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-storage-management-refExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-storage-management-ref 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-management-ref. Access via /axiom-storage-management-ref 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
Purpose: Comprehensive reference for storage pressure, purging policies, disk space, and URL resource values Availability: iOS 5.0+ (basic), iOS 11.0+ (modern capacity APIs) Context: Answer to "Does iOS provide any way to mark files as 'purge as last resort'?"
Use this skill when you need to:
"Does iOS provide any way to mark files as 'purge as last resort'?"
Answer: Not directly, but iOS provides two approaches:
Location-based purging (implicit priority):
tmp/ → Purged aggressively (anytime)Library/Caches/ → Purged under storage pressureDocuments/, Application Support/ → Never purgedCapacity checking (explicit strategy):
volumeAvailableCapacityForImportantUsage — For must-save datavolumeAvailableCapacityForOpportunisticUsage — For nice-to-have data| Resource Key | Type | Purpose | Availability |
|---|---|---|---|
volumeAvailableCapacityKey |
Int64 | Total available space | iOS 5.0+ |
volumeAvailableCapacityForImportantUsageKey |
Int64 | Space for essential files | iOS 11.0+ |
volumeAvailableCapacityForOpportunisticUsageKey |
Int64 | Space for optional files | iOS 11.0+ |
volumeTotalCapacityKey |
Int64 | Total volume capacity | iOS 5.0+ |
isExcludedFromBackupKey |
Bool | Exclude from iCloud/iTunes backup | iOS 5.1+ |
isPurgeableKey |
Bool | System can delete under pressure | iOS 9.0+ |
fileAllocatedSizeKey |
Int64 | Actual disk space used | iOS 5.0+ |
totalFileAllocatedSizeKey |
Int64 | Total allocated (including metadata) | iOS 5.0+ |
// ✅ CORRECT: Check appropriate capacity before saving
func checkSpaceBeforeSaving(fileSize: Int64, isEssential: Bool) -> Bool {
let homeURL = FileManager.default.homeDirectoryForCurrentUser
do {
let values = try homeURL.resourceValues(forKeys: [
.volumeAvailableCapacityForImportantUsageKey,
.volumeAvailableCapacityForOpportunisticUsageKey
])
if isEssential {
// For must-save data (user-created content, critical app data)
let importantCapacity = values.volumeAvailableCapacityForImportantUsage ?? 0
return fileSize < importantCapacity
} else {
// For nice-to-have data (caches, thumbnails)
let opportunisticCapacity = values.volumeAvailableCapacityForOpportunisticUsage ?? 0
return fileSize < opportunisticCapacity
}
} catch {
print("Error checking capacity: \(error)")
return false
}
}
// Usage
if checkSpaceBeforeSaving(fileSize: imageData.count, isEssential: true) {
try imageData.write(to: documentsURL.appendingPathComponent("photo.jpg"))
} else {
showLowStorageAlert()
}
volumeAvailableCapacityForImportantUsage:
volumeAvailableCapacityForOpportunisticUsage:
// ✅ CORRECT: Different thresholds for different data types
func shouldDownloadThumbnail(size: Int64) -> Bool {
let capacity = try? FileManager.default.homeDirectoryForCurrentUser
.resourceValues(forKeys: [.volumeAvailableCapacityForOpportunisticUsageKey])
.volumeAvailableCapacityForOpportunisticUsage ?? 0
// Only download optional content if there's plenty of space
return size < capacity
}
func canSaveUserDocument(size: Int64) -> Bool {
let capacity = try? FileManager.default.homeDirectoryForCurrentUser
.resourceValues(forKeys: [.volumeAvailableCapacityForImportantUsageKey])
.volumeAvailableCapacityForImportantUsage ?? 0
// User documents are essential
return size < capacity
}
Files in Caches/ are automatically excluded from backup, but you should explicitly mark re-downloadable files in other directories.
// ✅ CORRECT: Exclude large re-downloadable files from backup
func markExcludedFromBackup(url: URL) throws {
var resourceValues = URLResourceValues()
resourceValues.isExcludedFromBackup = true
try url.setResourceValues(resourceValues)
}
// Example: Downloaded podcast episodes
func downloadPodcast(url: URL) throws {
let appSupportURL = FileManager.default.urls(
for: .applicationSupportDirectory,
in: .userDomainMask
)[0]
let podcastURL = appSupportURL
.appendingPathComponent("Podcasts")
.appendingPathComponent(url.lastPathComponent)
// Download file
let data = try Data(contentsOf: url)
try data.write(to: podcastURL)
// Mark as excluded from backup (can re-download)
try markExcludedFromBackup(url: podcastURL)
}
When to exclude from backup:
// ✅ Check if file is excluded from backup
func isExcludedFromBackup(url: URL) -> Bool {
let values = try? url.resourceValues(forKeys: [.isExcludedFromBackupKey])
return values?.isExcludedFromBackup ?? false
}
Mark files as candidates for automatic purging by the system.
// ✅ CORRECT: Mark cache files as purgeable
func markAsPurgeable(url: URL) throws {
var resourceValues = URLResourceValues()
resourceValues.isPurgeable = true
try url.setResourceValues(resourceValues)
}
// Example: Thumbnail cache
func cacheThumbnail(image: UIImage, for url: URL) throws {
let cacheURL = FileManager.default.urls(
for: .cachesDirectory,
in: .userDomainMask
)[0]
let thumbnailURL = cacheURL.appendingPathComponent(url.Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for axiom-storage-management-ref matched our evaluation — installs cleanly and behaves as described in the markdown.
axiom-storage-management-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend axiom-storage-management-ref for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: axiom-storage-management-ref is the kind of skill you can hand to a new teammate without a long onboarding doc.
axiom-storage-management-ref reduced setup friction for our internal harness; good balance of opinion and flexibility.
axiom-storage-management-ref is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: axiom-storage-management-ref is focused, and the summary matches what you get after install.
axiom-storage-management-ref fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added axiom-storage-management-ref from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for axiom-storage-management-ref matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 55