Skill Claude CodeCodex
Use when deciding what to work on next, when progress is stuck, or when the reflex is to build or automate before proving the current bottleneck. Identifies the single dominating constraint, drills to an attackable mechanism, and applies the ordered sequence question requirements → delete → simplify → accelerate →…
Skill Claude CodeCodex
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).…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
Enumerate required context, check what exists, and find the simplest path forward before any task. Prevents hallucinations by forcing the agent to verify assumptions before acting.
Skill Claude CodeCodex
Foundation patterns for building context operating systems.
Skill Claude CodeCodex
This skill should be used when users ask about their work context, what they're working on, recent activity, file relationships, or knowledge graph structure. Uses context-os CLI (including graph health/search/stats commands) combined with grep/glob for context restoration. Every claim MUST cite a receipt ID for user…
Skill Claude CodeCodex
This skill should be used when decomposing a spec into a multi-agent implementation plan with dependency ordering, parallelism decisions, contract testing, and verification strategy. Applies evidence from 5 verified multi-agent builds (sequential handoff, parallel fanout, mixed waves, corpus-wide single-agent, phased…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
Ground implementation decisions in domain knowledge before designing solutions. Prevents over-engineering by checking what documentation exists, making assumptions explicit, and verifying them against canonical sources. Core principle - know what you don't know before designing.
Skill Claude CodeCodex
This skill should be used when a specific quality problem (UX, data, architecture, feature) needs systematic diagnosis and iterative fixing toward a defined target. Traces symptoms to root causes, sets measurable targets with automated backpressure (unit tests, Playwright, LLM-as-judge, or rubric scoring), and…
Skill Claude CodeCodex
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 knowledgebase/ domain. Use when user…
Skill Claude CodeCodex
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…
Skill Claude CodeCodex
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…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: