jorgex-stack weekly downloads statistics

JorgeX Stack

Shared configuration for Claude Code, Codex CLI, OpenCode v2 and official Pi: thirteen local skills, six subagents and native integrations, applied through each runtime's own mechanisms. Stack does not install a second Pi runtime and keeps no private provider contracts or receipts.

Quick start

You need Node >= 22.5 and pnpm. Install the runtimes you want through their official channels first; Stack configures them, it does not install them.

Run it (recommended)

pnpm dlx jorgex-stack@latest

This is the only command most people need. It downloads the latest published release into pnpm's temporary cache and opens the interactive menu. Nothing is installed globally and nothing is added to your PATH, so there is no old copy to update or remove later.

pnpm reuses that download for one day (dlxCacheMaxAge), so repeated runs start immediately and work offline. After a day, the next run checks the registry again and picks up a new release if there is one.

Install it as a permanent command (optional)

pnpm add -g jorgex-stack@latest

This installs a global jorgex-stack command; run jorgex-stack to open the same menu. The copy stays at the version you installed: the menu's Actualizar action updates your runtimes' configuration, not Stack itself. To update Stack, run the same pnpm add -g jorgex-stack@latest again. To remove it, run pnpm remove -g jorgex-stack.

Use a single package manager. A second global copy installed with npm or another tool can come first in your PATH and run an older version without any warning.

What opens

Both commands open the same menu, in Spanish. It takes no subcommands or flags (not even --version or --yes) and has no headless mode. Without an interactive terminal it changes no files and does not wait for input. The distribution version lives in package.json and in the registry, not in an installer alias.

Menu entry	What it does
Instalar / configurar	Applies Stack's skills, subagents and configuration to the runtimes you select.
Actualizar	Updates runtime configuration through native channels and re-applies Stack's resources.
Doctor	Read-only check of the local configuration.
Desinstalar	Removes the managed resources you select, with confirmation and backup.
Limpiar	Removes leftovers from earlier versions and old backups (details).

The first four entries offer the sections Todo (everything), Skills compartidas (shared skills), Configuración por runtime (per-runtime configuration) and Subagentes (subagents). Limpiar chooses neither section nor runtime.

Pick a target and a unit, then Aplicar. Navigating or going back never runs an installation. Editing a subagent's model or effort has its own Guardar, independent of Aplicar: saved changes remain when you go back, and unsaved drafts are discarded when you leave the editor. A failure leaves the applied and pending units visible; there is no global rollback and no automatic retry.

Missing runtimes are not installed when you open a screen. Updating configuration uses native channels (claude update, codex update, opencode upgrade, pi update --all and the official package registry); updating only skills or subagents does not update tools. Doctor compares local configuration without installing, downloading, starting a browser or writing memories. It does not certify that a runtime actually loads the resources, has access to a model, or enforces permissions.

Shared canon

Skills: diagnose, grilling, landing-launch, lean-code, mcp-builder, orchestrator, project-architect, retro, skill-creator, to-spec, visual-director, what and xreview. They are copied whole from stack/skills to ~/.agents/skills, with no updater for external repositories and no skill pins. Pi, Codex and OpenCode discover them natively; Claude uses one link per skill from its native path, not another copy.

Subagents: implementer, analyst, reviewer, security-auditor, simplifier and generalist. The primary agent belongs to the runtime and loads orchestrator as a skill. There are no tiers and no factory models or efforts, and Stack does not impose defaultProvider, defaultModel or defaultThinkingLevel on Pi. Implementer owns code and tests; simplifier is always read-only. Models are saved per agent in its native file, preserving body and permissions.

A single profile serves both human and programmatic use. Native APIs (SDK/CLI, Codex app-server, OpenCode v2 server, Pi RPC) allow structured operations according to each host, not a universal takeover of an open TTY. Herdr is neither installed nor configured: an existing personal integration is kept.

The canonical workflow is orchestrator and is not duplicated here. Visual Director, retro and what keep their manual-invocation limits. The active Visual Director is portable; its historical dossier is not a runtime dependency and is not included in the npm package. Likewise, the historical Landing Launch dossier is not a runtime dependency and is not packaged; it was built with material from Marketing Skills (MIT), whose notice ships in stack/skills/landing-launch/NOTICE.md. The historical Project Architect dossier follows the same rule; its decision record template derives from MADR (MIT OR CC0-1.0), noted in stack/skills/project-architect/NOTICE.md.

Configuration and integrations…