frontend-cache-coherence
Skill40 starsChanged 3 days agoApache-2.0View on GitHub
Use when auditing or changing Hussh frontend cache-first screen behavior, warm-cache UX, stale-while-revalidate resources, route TTL policy, or reviewer-backed cache coherence checks.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with frontend-architecture, frontend-native-surface-mapper, and security-audit.
- Distinctive: line 59
Run the cache and manifest checks before trusting screen coverage.
- Very specific: line 61
Use useStaleResource or a service-owned resource wrapper for warm-cache rendering.
- Distinctive: line 63
Use reviewer env identity only through the existing resolver.
- Distinctive: line 64
Treat performance as part of cache coherence: choose the safest available UX path before showing a blocking loader.
- Distinctive: line 65
Verify route/cache KPI coverage for changed screens: readiness, resource resolution, refresh completion, and warmup where applicable.
- Distinctive: line 66
Keep performance events metadata-only: route ID, resource class, cache tier, freshness, result, duration bucket, and footprint bucket.
- Very specific: line 67
When a route split reuses an existing workspace, regenerate and verify cache-coherence-screen-manifest.generated.json.
- Very specific: line 71
If route inventory, package scripts, or generated surface-map shape changes, hand off to frontend-architecture.
- Very specific: line 72
If native parity or API dependency mapping changes, hand off to frontend-native-surface-mapper.
- Very specific: line 73
If PKM/vault persistence semantics change, hand off to security-audit.
- Very specific: line 74
If browser proof policy changes, hand off to quality-contracts.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Frontend Cache Coherence Skill
Purpose and Trigger
- Primary scope:
frontend-cache-coherence - Trigger on cache-first screen UX, route TTL policy, stale-while-revalidate resources, warm-cache audits, and reviewer-backed cache checks.
- Avoid overlap with
frontend-architecture,frontend-native-surface-mapper, andsecurity-audit.
Coverage and Ownership
- Role:
spoke - Owner family:
frontend
Owned repo surfaces:
hushh-webapp/lib/cachehushh-webapp/lib/services/cache-service.tshushh-webapp/lib/cache/cache-sync-service.tshushh-webapp/scripts/architecture/audit-cache-coherence.mjshushh-webapp/cache-coherence-screen-manifest.generated.jsondocs/development/contracts/cache-coherence.mddocs/development/quality/app-surface-design-system.md
Non-owned surfaces:
frontendfrontend-architecturefrontend-native-surface-mappersecurity-audit
Do Use
- Screen-level cache posture audits and warm-cache UX fixes.
- Resource hooks, TTL policy, background refresh, and cache invalidation contract work.
- Reviewer-backed checks proving protected routes do not block on loaders when cache is warm.
Do Not Use
- Broad route inventory or package-script ownership; use
frontend-architecture. - Route/API/native/plugin mapping; use
frontend-native-surface-mapper. - PKM protocol, vault key, or encrypted storage boundary changes; use
security-audit.
Read First
docs/development/contracts/cache-coherence.mddocs/development/quality/app-surface-design-system.mdhushh-webapp/cache-coherence-screen-manifest.generated.jsonhushh-webapp/scripts/testing/verify-signed-in-routes.mjshushh-webapp/lib/cache/use-stale-resource.ts
Workflow
- Classify the prompt claim as existing, partial, missing, future-state, wrong-direction, or needs-verification.
- Run the cache and manifest checks before trusting screen coverage.
- Preserve the security posture: decrypted PKM, vault keys, and consent secrets stay memory-only.
- Use
useStaleResourceor a service-owned resource wrapper for warm-cache rendering. - Route all mutation invalidation through
CacheSyncServiceor a domain service that delegates to it. - Use reviewer env identity only through the existing resolver; never hardcode reviewer values.
- Treat performance as part of cache coherence: choose the safest available UX path before showing a blocking loader.
- Verify route/cache KPI coverage for changed screens: readiness, resource resolution, refresh completion, and warmup where applicable.
- Keep performance events metadata-only: route ID, resource class, cache tier, freshness, result, duration bucket, and footprint bucket. Never emit raw cache keys, user IDs, workflow IDs, PKM payloads, prompts, or decrypted values.
- When a route split reuses an existing workspace, regenerate and verify
cache-coherence-screen-manifest.generated.json; every canonical nested route needs explicit route readiness/resource-class coverage even if the cache posture is inherited from the parent workspace.
Handoff Rules
- If route inventory, package scripts, or generated surface-map shape changes, hand off to
frontend-architecture. - If native parity or API dependency mapping changes, hand off to
frontend-native-surface-mapper. - If PKM/vault persistence semantics change, hand off to
security-audit. - If browser proof policy changes, hand off to
quality-contracts.
Required Checks
cd hushh-webapp && npm run verify:cache
cd hushh-webapp && npm run audit:cache-coherence
cd hushh-webapp && npm run verify:analytics
cd hushh-webapp && npm run verify:surface-map
cd hushh-webapp && npm run verify:service-boundaryDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

