Menu
Foundation patterns for building context operating systems
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
This skill should be used to periodically defragment a multi-app/multi-service codebase — both CODE (duplicate deploy targets, colliding bindings, stale forks) and CONTEXT (parallel spec conventions, orphan docs, scattered context packages) — on any platform (Cloudflare, Railway, Vercel, Fly, Render, Docker Compose). Converts the vague "things are getting messy" feeling into specific, located, severity-ranked findings. Detect-only — does NOT auto-consolidate. Apply on a monthly cadence, before any risky deploy, after a migration, or whenever canonical-source ambiguity is suspected. Core principle — agentic coding fragments state faster than humans consolidate it, so drift accumulates silently until a deploy fires from the wrong place or an agent onboards from the wrong context.
This skill should be used when making SEO, AEO (Answer Engine Optimization), or search visibility decisions. Apply expert perspectives (Eli Schwartz, Mike King, Lily Ray, Rand Fishkin, Cyrus Shepard) to diagnose what actually matters for search performance — programmatic page generation, structured data, title tags, E-E-A-T signals, and AI Overview optimization. Use when building pages for search visibility, adding structured data, evaluating whether programmatic pages have search value, or optimizing for AI-generated answers.
This skill should be used when producing content (newsletter posts, blog posts, LinkedIn posts) from existing corpus material. Discovers relevant context from the knowledge graph, selects the right content framework, assembles a draft against a spec, then runs an eval loop of anti-slop checks until the output clears quality gates. Built from real content production pipelines with 142 automated anti-slop tests and the eval-loop methodology.
This skill should be used when making architectural decisions, writing specs, or reviewing decisions that contain "future work", "v2", "simpler for now", "out of scope", or complexity claims. Verifies assumptions are grounded and catches corner-cutting disguised as pragmatism. Applies to code, specs, data models, auth flows, and context structures.
This skill should be used when processing raw content (transcripts, documents, notes, current conversation) into structured knowledge nodes for a Context OS. Extracts atomic concepts, creates nodes with complete frontmatter and [[wiki-links]], and routes each node to the correct knowledge_base/ domain. Use when user says "ingest this", "process into knowledge base", "turn this into nodes", or provides raw content to structure. Uses tags consistent with existing graph nodes; new concepts start as status emergent.
This skill should be used when a user wants to build their first Context OS or kick off initial setup of a knowledge graph system. Guides through a 10-minute flow — assess content, create the two-layer directory structure, generate CLAUDE.md, ingest first content, and verify compounding works. Adapts to blank-slate vs existing-content starting points. Use when user says "set up a context OS", "get started with context OS", "build a knowledge graph from scratch", or "quickstart".
Based on SOC occupation classification
| name | context-os-basics |
| description | Foundation patterns for building context operating systems |
| model | inherit |
A context operating system is a structured knowledge system where:
Individual reusable concepts:
Each node:
Strategic artifacts that COMPOSE Layer 1:
Key principle: Operational docs REFERENCE atomic concepts, they don't redefine them.
Defines blessed tags for your system:
Start small. Add tags only after 3+ nodes demonstrate need.
Defines how concepts relate:
Every claim needs a source:
Quality standard: If you can't cite a source, don't claim it.
Problem: Single long conversation without writing to files Fix: Write intermediate results to files, preserve attribution chains
Problem: "Need to read all files to answer this" Fix: Use synthesis docs (5% of content answers 95% of questions)
Problem: "Many customers want this" (no source) Fix: Quantify everything: "14 of 166 (8.4%)" not "many"
Never automate without sampling first:
For complex implementations:
These require customization for your specific context. Learn more: https://taste.systems
