Receber por email
← Voltar para o catálogo

openskills-plugin-separation

Enforce clean separation between core openskills-runtime and optional WASM build plugins so plugin compilation does not break runtime consumers or language bindings.

60estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add Geeksfino/openskills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/openskills-plugin-separation/svg)](https://www.skillteca.com.br/skills/openskills-plugin-separation)

Skills relacionadas

Ver todas de Dados e Análise →

Alerta por categoria

Receba novas skills de Dados e Análise toda segunda

1 email curto, só com as skills novas de Dados e Análise. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

OpenSkills Plugin Separation

Use this skill when changing plugin features, build-tool wiring, or runtime dependency topology.

Objective

Keep core runtime usable without plugin toolchains, especially for bindings and non-build execution paths.

Key Files

  • runtime/Cargo.toml
  • runtime/src/lib.rs
  • runtime/src/bin/openskills-runtime.rs
  • runtime/src/build/**
  • bindings/ts/Cargo.toml
  • bindings/python/Cargo.toml

Separation Rules

  1. Build plugins must be gated behind explicit features.
  2. Core runtime defaults should not force plugin toolchains.
  3. Bindings should opt out of plugin-heavy default features when appropriate.
  4. Public exports for build functions must be feature-gated.
  5. CLI build commands must degrade gracefully when build features are disabled.

Validation Checklist

  • cargo check -p openskills-runtime passes with default features.
  • Bindings compile without pulling plugin-specific dependencies unintentionally.
  • Runtime tests that do not require plugin build paths continue to pass.

Output Format

  • Feature graph summary
  • Leakage findings (if any)
  • Minimal patch plan
  • Post-change verification commands
Compartilhar X LinkedIn