opchain - Ecosystem de Skills para Pipeline de Desenvolvimento
asfbay-bit/opchain
Skills modulares que cobrem o ciclo completo do desenvolvimento sem APIs
Ver no GitHubopchain é um ecossistema aberto de skills para Claude que cobre todo o pipeline de desenvolvimento: discover, spec, design, build, audit, deploy e scale. Cada skill é um arquivo `.skill` que se integra nativamente ao Claude, compartilhando estado através de um protocolo de checkpoint em JSON, eliminando a necessidade de APIs externas ou etapas de build.
Instalação
npx convez-ai asfbay-bit/opchain1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automatizar entrevistas de requisitos e gerar user stories estruturadas
- Gerar especificações de API, modelos de dados e decisões de stack com rationale
- Executar auditorias de código em 5 camadas (segurança, performance, correção, UX, config)
- Orquestrar deploy com gates de auditoria, staging e rollback automático
- Planejar testes de carga e otimizações de performance
Veredito

opchain é uma proposta sólida para sistematizar o workflow de desenvolvimento dentro do Claude, eliminando handoffs manuais via checkpoint persistente. O conceito é maduro e bem estruturado, mas requer adoção deliberada de cada skill; mais adequado para equipes que já trabalham com Claude como IDE.
README
A tradução para o português deste README ainda está na fila.
opchain
skills that ship.
opchain is an open-source Claude skill ecosystem for developers —
a tightly-integrated set of .skill files covering the full
development pipeline: discover, spec, design, build, audit, deploy,
and scale.
Install a skill. Trigger it by name. Pick up where you left off.
what's a skill?
A skill is a self-contained instruction set that extends Claude's behavior for a specific phase of development. Each skill:
- Owns one phase of the pipeline
- Reads upstream checkpoints from other skills
- Writes its own checkpoint so work persists across sessions
- Triggers via slash command or natural language
No API keys. No build step. Drop a .skill file into Claude's
settings and go.
the pipeline
discover → spec → design → build → audit → ship → scale
Each phase is owned by a dedicated skill. Skills share state through a JSON checkpoint protocol — context flows forward without manual handoffs.
| phase | skill | trigger | what it does |
|---|---|---|---|
| discover | oc-app-architect | /oc-discover | Requirements interview → user stories, constraints, acceptance criteria |
| spec | oc-app-architect + oc-stack-forge | /oc-spec | API contract, data model, stack decision with rationale |
| design | oc-ux-engineer | /oc-uxe plan | Formal design spec, component tree, style tokens |
| build | oc-app-architect | /oc-build | Generator → Evaluator loop. Score ≥ 7/10 to advance. |
| audit | oc-code-auditor | /oc-audit full | 5-layer sweep: security, performance, correctness, UX, config |
| ship | oc-deploy-ops + oc-git-ops | /oc-deploy staging | Audit gate, staging, smoke tests, production with rollback |
| scale | oc-scale-ops | /oc-scale audit | Load tests, perf budgets, caching, capacity planning |
skill library
foundation
| skill | what it does |
|---|---|
oc-checkpoint-protocol | JSON session persistence across skills and conversations |
plan
| skill | trigger | what it does |
|---|---|---|
oc-stack-forge | /oc-stack-decide | Stack advisor for CF, Vercel, AWS, Supabase, Rails, Django, Go, Rust |
oc-reverse-spec | /oc-rev-full | Reverse-engineer existing code into structured spec docs |
plan + build
| skill | trigger | what it does |
|---|---|---|
oc-app-architect | /oc-discover /oc-spec /oc-build /oc-launch | Unified pipeline: discover → spec → design → sprint → build → launch |
build
| skill | trigger | what it does |
|---|---|---|
oc-ux-engineer | /oc-uxe plan /oc-uxe build /oc-uxe eval | Design Planner → Generator → Evaluator tri-agent harness |
oc-integrations-engineer | /oc-integrate plan | Planner → Builder → Tester. Hits real API sandboxes, not mocks. |
quality
| skill | trigger | what it does |
|---|---|---|
oc-code-auditor | /oc-audit full | Auditor → Fixer → Verifier. 5-layer sweep, pre-deploy gate. |
oc-scale-ops | /oc-scale audit | Load testing, perf budgets, caching strategy, capacity planning |
ship
| skill | trigger | what it does |
|---|---|---|
oc-deploy-ops | /oc-deploy staging | Audit gate → staging → smoke tests → production → auto-rollback |
oc-git-ops | /oc-git-commit /git-pr | Conventional commits, sprint-scoped branches, checkpoint-enriched PRs |
install
Claude.ai / Claude Desktop
- Download any
.skillfile from/skills - Open Claude → Settings → Customize → Skills
- Upload the
.skillfile - Start a new conversation and trigger it
Claude Code CLI
mkdir -p .claude/skills
cp ~/opchain/skills/*.md .claude/skills/
claude
> /oc-discover
Team (check into git)
git add .claude/skills/
git commit -m "chore: add opchain skills"
git push
the checkpoint protocol
Every skill writes a JSON checkpoint to .checkpoints/ in your
project. Skills read each other's checkpoints to make informed
decisions:
oc-deploy-opsreadsoc-code-auditor— CRITICAL findings block deploy- Build evaluator reads
oc-ux-engineer— grades frontend against approved spec oc-git-opsreadsoc-app-architect— names branches by sprint