ai recipes

Multi-skill walkthroughs.

A single skill does one job well. The leverage comes from chaining them. Each recipe below is an end-to-end run — one skill hands its checkpoint to the next, so the pipeline carries scope, decisions, and eval results all the way from idea to live. Pick the one closest to what you're building and follow the chain.

Ship a RAG app in a week

Go from an idea to a live, evaluated retrieval-augmented app with a goldset you can regress against.

  1. 01
    oc-app-architect /oc-discover

    Scopes the app — who it's for, what it retrieves over, the one job it has to nail.

  2. 02
    oc-stack-forge /oc-stack-decide

    Picks the platform and a kind: vector-db pack — pgvector, Pinecone, Turbopuffer, or Supabase Vectors — against your scale and budget.

  3. 03
    oc-rag-forge /oc-rag

    Runs the Designer → Builder → Evaluator loop: chunking strategy, embedding model, retrieval pipeline, and a retrieval eval that scores recall before you wire generation.

  4. 04
    oc-claude-api /oc-claude-api

    Adds the generation model on top of retrieved context, with prompt caching on the system + retrieved chunks to cut cost and latency.

  5. 05
    oc-code-auditor /oc-audit

    Runs the "Phase: AI app?" sweep — prompt-injection surfaces and tool-use boundaries, not just generic lint.

  6. 06
    oc-deploy-ops /oc-deploy

    Gates on the audit, ships to staging, then production with a health check.

Your effort

You answer the discovery questions and approve the stack pick. The skills write the chunking, eval harness, and deploy config.

You end up with

An evaluated RAG app with a retrieval goldset, live in production.

Build a Claude agent that ships PRs

Stand up a Claude Agent SDK agent that opens real pull requests, gated on an eval harness and a tool budget.

  1. 01
    oc-app-architect /oc-discover

    Scopes what the agent is for and where its PRs land before any topology is chosen.

  2. 02
    oc-agent-forge /oc-agent

    Planner picks the subagent topology, tool budget, and loop shape; the Evaluator gates the build on a task fixture suite so regressions surface before merge.

  3. 03
    oc-claude-api /oc-claude-api

    Sets model routing — a stronger model for the orchestrator, cheaper workers for the fan-out — with caching on shared context.

  4. 04
    oc-git-ops /oc-git-sync

    The agent's PRs go through the same commit gate as a human's — branch, audit, commit, push, open the PR.

Your effort

You define the task fixtures and the tool budget ceiling. The skills build the harness, wire routing, and route every PR through the gate.

You end up with

An agent with an eval harness and a capped tool budget, opening real PRs.

Migrate Sonnet 4.6 → 4.7 without regressing

Bump a model version and prove it didn't make anything worse before it reaches users.

  1. 01
    oc-claude-api /oc-claude-api migrate

    Produces a model-version migration diff PR — the SDK call sites, params, and any retired-model swaps in one reviewable change.

  2. 02
    oc-prompt-ops /oc-prompt regress

    Re-runs the eval goldset on the new model and blocks if any score drops more than regression_epsilon.

  3. 03
    oc-release-ops /oc-release

    Cuts the release once the regression suite is green — bumps the version, drafts the changelog, hands off to ship.

Your effort

You set regression_epsilon and review the diff. The skills run the goldset and refuse to ship a regression.

You end up with

A model bump gated on eval scores, shipped safely.

Run one of these.

Every skill in these recipes is in the library. Install the chain once and the orchestrator routes you between them — you rarely have to name the next step by hand.