performance-memory

Use when reading or writing performance history for a client site, calculating trend deltas, comparing snapshots, tracking issue lifecycle, or managing performance-history.json. Also use when any skill needs to persist a partial metrics snapshot after completing its own analysis.

Model	Source
sonnet	pack: assessment

Full Reference

Performance Memory

Manages performance-history.json at the project root. Shared infrastructure layer for the assessment pack and any skill that wants to persist performance data between runs.

Quick Reference

Operation	When
`snapshot.create`	After a full `master-performance-assessment` run
`snapshot.compare`	Calculating MoM/QoQ deltas for trend display
`trends.calculate`	Generating sparkline data for reports
`issues.track`	Marking an issue resolved or wont-fix
`issues.correlate`	Surfacing cross-domain issue relationships
`history.prune`	Archiving snapshots older than `retentionMonths`
`partial.write`	Single-skill writes (seo-audit, cro-audit, etc.)

Item	Value
File location	`performance-history.json` at project root
Schema version	1.0
Default retention	24 months
Snapshot fields	seo, performance, analytics, ads, local, cro, content, ai, competitor

Reference Index

I want to…	File
Understand the full JSON schema and all field definitions	`reference/schema.md`
Implement create, compare, trend calculation, and prune operations	`reference/operations.md`
Write a partial snapshot from a single skill (seo-audit, cro-audit, etc.)	`reference/integration.md`

Usage: Read the reference file matching your current task. Each file is self-contained.

Announcement

┏━ 🧠 performance-memory ━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Performance history CRUD — trends, snapshots, ┃ ┃ issue tracking, cross-skill shared layer ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛