agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/frontend-cache-coherence/SKILL.md

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.

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
  1. Very specific:

    Avoid overlap with frontend-architecture, frontend-native-surface-mapper, and security-audit.

    line 12
  2. Distinctive:

    Run the cache and manifest checks before trusting screen coverage.

    line 59
  3. Very specific:

    Use useStaleResource or a service-owned resource wrapper for warm-cache rendering.

    line 61
  4. Distinctive:

    Use reviewer env identity only through the existing resolver.

    line 63
  5. Distinctive:

    Treat performance as part of cache coherence: choose the safest available UX path before showing a blocking loader.

    line 64
  6. Distinctive:

    Verify route/cache KPI coverage for changed screens: readiness, resource resolution, refresh completion, and warmup where applicable.

    line 65
  7. Distinctive:

    Keep performance events metadata-only: route ID, resource class, cache tier, freshness, result, duration bucket, and footprint bucket.

    line 66
  8. Very specific:

    When a route split reuses an existing workspace, regenerate and verify cache-coherence-screen-manifest.generated.json.

    line 67
  9. Very specific:

    If route inventory, package scripts, or generated surface-map shape changes, hand off to frontend-architecture.

    line 71
  10. Very specific:

    If native parity or API dependency mapping changes, hand off to frontend-native-surface-mapper.

    line 72
  11. Very specific:

    If PKM/vault persistence semantics change, hand off to security-audit.

    line 73
  12. Very specific:

    If browser proof policy changes, hand off to quality-contracts.

    line 74

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, and security-audit.

Coverage and Ownership

  • Role: spoke
  • Owner family: frontend

Owned repo surfaces:

  1. hushh-webapp/lib/cache
  2. hushh-webapp/lib/services/cache-service.ts
  3. hushh-webapp/lib/cache/cache-sync-service.ts
  4. hushh-webapp/scripts/architecture/audit-cache-coherence.mjs
  5. hushh-webapp/cache-coherence-screen-manifest.generated.json
  6. docs/development/contracts/cache-coherence.md
  7. docs/development/quality/app-surface-design-system.md

Non-owned surfaces:

  1. frontend
  2. frontend-architecture
  3. frontend-native-surface-mapper
  4. security-audit

Do Use

  1. Screen-level cache posture audits and warm-cache UX fixes.
  2. Resource hooks, TTL policy, background refresh, and cache invalidation contract work.
  3. Reviewer-backed checks proving protected routes do not block on loaders when cache is warm.

Do Not Use

  1. Broad route inventory or package-script ownership; use frontend-architecture.
  2. Route/API/native/plugin mapping; use frontend-native-surface-mapper.
  3. PKM protocol, vault key, or encrypted storage boundary changes; use security-audit.

Read First

  1. docs/development/contracts/cache-coherence.md
  2. docs/development/quality/app-surface-design-system.md
  3. hushh-webapp/cache-coherence-screen-manifest.generated.json
  4. hushh-webapp/scripts/testing/verify-signed-in-routes.mjs
  5. hushh-webapp/lib/cache/use-stale-resource.ts

Workflow

  1. Classify the prompt claim as existing, partial, missing, future-state, wrong-direction, or needs-verification.
  2. Run the cache and manifest checks before trusting screen coverage.
  3. Preserve the security posture: decrypted PKM, vault keys, and consent secrets stay memory-only.
  4. Use useStaleResource or a service-owned resource wrapper for warm-cache rendering.
  5. Route all mutation invalidation through CacheSyncService or a domain service that delegates to it.
  6. Use reviewer env identity only through the existing resolver; never hardcode reviewer values.
  7. Treat performance as part of cache coherence: choose the safest available UX path before showing a blocking loader.
  8. Verify route/cache KPI coverage for changed screens: readiness, resource resolution, refresh completion, and warmup where applicable.
  9. 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.
  10. 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

  1. If route inventory, package scripts, or generated surface-map shape changes, hand off to frontend-architecture.
  2. If native parity or API dependency mapping changes, hand off to frontend-native-surface-mapper.
  3. If PKM/vault persistence semantics change, hand off to security-audit.
  4. 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-boundary

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.