Ship faster with working baselines for real AI coding workflows.
Field notes and installable artifacts from teams already shipping with Claude Code, Codex, Cursor, and Gemini.
Or pick a shelf · curated entry points
Fix a specific problem
13 cablesTargeted how-tos: prompt caching, bugfix loops, QA, tracing, setup drift.
Follow a track
2 tracksSequential onboarding and team-leverage tracks, progress-saved.
Study a builder
4 seriesPlaybooks distilled from Karpathy, Amodei, Chase, Cherny — what they said and what to do about it.
Move between ecosystems
2 cablesPort skills, command packs, and CLAUDE.md between Claude ↔ Codex ↔ Cursor ↔ Gemini.
Start a new stack
5 cablesFirst-run setup for Cursor rules, Gemini CLI, and team contracts on other tools.
Roll out to a team
7 cablesTeam contracts, subagent patterns, CLAUDE.md split patterns, leverage frameworks.
Latest from teams shipping with AI
full catalog →Use auto mode, not --dangerously-skip-permissions
Two flags promise to stop Claude Code from pausing at every tool call. One of them reads your settings, honours your allowlist, and refuses to run anything g…
Publish your stack to Cables (automated)
A skill that walks Claude Code through publishing your Claude stack to the Cables community in one conversation. No manual repo setup, no hand-written `stack…
Replicate Ragav's stack (skills + plugins + scripts)
Pick the stack that matches what you're building. Each one is a single `npx` command. Plugins installed, skills synced, marketplaces configured, no bash scri…
Work with FRE|Nxt
We build the production AI systems we write about.
Cables are the field notes. The playbooks come from client engagements — multi-agent systems, RAG pipelines, and LLM cost cuts that ship and hold up in production. If something here maps to a problem on your roadmap, two ways in:
Audit capacity: 5 slots/month · No pitch deck · NDA on request