convez.ai
MCP ServerIntegração & APIsAvançado
Royalti-io

Ikenga Packages

Royalti-io/ikenga-pkgs

Monorepo centralizado para engines, MCP servers e apps do Ikenga

Ver no GitHub
BomPluginScore · de 0 a 100

Monorepo open-source que centraliza pacotes oficiais do Ikenga: engines de IA, MCP servers, mini-apps e conectores. Fornece exemplos funcionais de cada arquétipo de pacote e gerencia versionamento e publicação via Changesets para o npm.

Instalação

$npx convez-ai Royalti-io/ikenga-pkgs

1 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

Estrelas
0
Forks
0
Acompanhando
0
Saúde
100%
Último commit
há 1 dia
Versão
@ikenga/skill-groundwork@0.8.4
Issues abertas
1
Contribuidores
2

Casos de uso

  • Criar adaptadores personalizados de engines de IA
  • Desenvolver novos MCP servers dentro do ecossistema Ikenga
  • Construir conectores com serviços externos
  • Aprender arquétipos de pacotes da plataforma

Veredito

Estrutura sólida para quem quer estender o Ikenga com novos componentes. Exige familiaridade com TypeScript e fluxo de monorepos, mas oferece documentação clara e padrões bem estabelecidos.

README

A tradução para o português deste README ainda está na fila.

ikenga-pkgs

License Discussions

The canonical home for first-party Ikenga packages — engines, MCP servers, mini-apps, and helpers — in one Apache-2.0 monorepo.

What it is

Every first-party Ikenga package lives here (ADR-009), versioned and published with Changesets. It's a good place to read working examples of each pkg archetype before authoring your own.

Layout

packages/
  engine/       AI engine adapters (claude-code, noop, …)
  mcp/          MCP servers (iyke, …)
  apps/         User-facing iframe mini-apps (studio, tasks, …)
  connectors/   External-service adapters
  sidecars/     Long-lived headless processes

Workflow

This monorepo uses Changesets for per-package versioning and publish.

pnpm install
pnpm -r build
pnpm changeset            # author a changeset describing your change
git commit -am "feat: ..."
# Open PR; on merge to main, "Version Packages" PR opens.
# Merging that PR publishes all bumped packages to npm and updates the registry index.

Each PR that changes a package must include a .changeset/*.md (the changeset-bot will nag you on PRs that don't).

Registry

Published versions appear in the ikenga-registry within seconds of pnpm changeset publish completing, via the scripts/update-registry-index.mjs step in the release workflow. The shell and ikenga CLI both consume that registry for discovery and install.

Links

  • ikenga — the desktop shell that loads these
  • ikenga-contract — the manifest schema each pkg validates against

License

Apache-2.0 — see LICENSE.

Ver o original no GitHub

Bom para

Relacionados