ai-context-layer
Installation
SKILL.md
App Context Layer
Design and review the application layer that selects, assembles, grounds, and learns from context for a product surface. Keep operational truth in tools, APIs, SQL, or a system of record; use derived memory only for durable facts or preferences with provenance, retention, and correction paths. This skill covers architecture and runtime contracts, not repo instruction files or prompt wording.
Quick Reference
| Question | Default | Load when needed |
|---|---|---|
| Where should operational truth live? | Tools, APIs, SQL, or system-of-record services | context-layer-detail |
| Is the problem retrieval or context assembly? | Use RAG for corpus retrieval; use this skill when personalization, relationships, action context, or surface bundles change the answer | ai-rag, context assembly |
| Is graph worth it? | Only when relationship traversal changes the answer | graph and relationship layer |
| Which architecture pattern fits? | Select the smallest pattern that meets tenancy, freshness, evidence, and budget needs | patterns catalog, reference architectures |
| Relational, graph, or vector storage? | Use the owning database design matrix alongside the context decision | storage paradigm selection |
| Is the scenario known (personal assistant, support/CRM, coding agent, multi-agent, regulated KB, code hub, incident, procedural, voice, analytics, on-device)? | Load its playbook first: R1–R7 defaults, upgrade trigger, acceptance tests | memory-scenario-playbooks |
| Building or auditing a KB or memory system end to end? | Classify the workload first, then audit the seven responsibilities (admission to materialisation) one by one; when precision and coverage both matter, link current state to its evidence (P22) | memory-responsibilities-audit |
| Is a memory/retrieval service safe to adopt? | Keep app-owned truth, provenance, isolation, retention, and rebuild paths; compare engines by representation × output and the responsibilities they implement natively | managed-memory boundaries, security threat model, vendor landscape |