What opchain knows.
Every oc-stack-forge pack opchain
ships, grouped by what role it plays in the dispatch graph.
Languages have a canonical test-runner / build /
lint command. Frameworks attach to a language pack.
Mobile packs dispatch through a release checklist
instead of executable commands. Deploy-targets are
the leaves of the dispatch graph — the hosting providers a
language / framework / mobile pack can land on.
Languages
Top-level toolchains. Each emits a skills.coverage.<id>.enabled
flag and ships with a canonical test / build / lint command set.
- Bun stable
bun - C# stable
csharpFrameworks:
dotnet-aspnet - Deno stable
deno - Elixir stable
elixirFrameworks:
phoenix - Go stable
go - Java stable
javaFrameworks:
spring-java - Kotlin stable
kotlinFrameworks:
spring-kotlin - PHP stable
phpFrameworks:
laravel-php - Python stable
python - Ruby stable
ruby - Rust stable
rust - Swift stable
swiftFrameworks:
swiftui - TypeScript stable
typescript
Frameworks
Application frameworks layered on a language pack. Inherit the language's test / build / lint command set; oc-stack-forge picks them when the workload signal matches the framework profile.
- ASP.NET Core stable
dotnet-aspnet - Laravel stable
laravel-php - Phoenix stable
phoenix - Remix stable
remix - SolidStart stable
solid - Spring Boot (Java) stable
spring-java - Spring Boot (Kotlin) stable
spring-kotlin - SvelteKit stable
sveltekit - SwiftUI stable
swiftui
Mobile
Mobile platforms. oc-stack-forge dispatches these
through the dispatchMobile() envelope — the
ref doc is rendered as a release checklist (App Store review,
Play Console rollout, EAS Submit) rather than executed as
commands. There is no mix test-equivalent for an
app-store submission.
- Android (Kotlin) stable
kotlin-android - Flutter stable
flutter - iOS (SwiftUI) stable
ios-swiftui - React Native (Expo) stable
react-native-expo
Deploy targets
Hosting providers that language / framework / mobile packs can
target. No coverage flag is emitted —
deploy-targets are sub-selections under another offer, not
top-level coverage units. oc-deploy-ops uses these to
pick the right provider section of its SKILL.md.
- App Store stable
app-store - AWS Amplify stable
aws-amplify - Google Play stable
play-store - Heroku stable
heroku - Netlify stable
netlify - Railway stable
railway
Vector databases
Vector stores that oc-rag-forge picks from when designing a
RAG or semantic-search app. Each emits a
skills.coverage.<id>.enabled flag. They are leaves of
the dispatch graph — no language/framework edges — selected
by retrieval needs (scale, latency, ops, cost), not by toolchain.
- pgvector (Postgres) stable
pgvector - Pinecone stable
pinecone - Supabase Vectors stable
supabase-vectors - Turbopuffer beta
turbopuffer
How to use
Every pack ships with a reference doc in
skills/oc-stack-forge/packs/<id>/
covering when to pick it, the canonical tooling, default deploy
targets, and gotchas. Click any pack name above to jump to the
source on GitHub.
Adding a pack is one pack.yml + one ref doc. See
CONTRIBUTING.md
for the contract. The scripts/gen-stack-packs.mjs
validator runs on every build, so accidental schema drift fails
CI rather than silently breaking oc-stack-forge's
recommendations.