pmcp

app-builder-lib 26.x

Practical app-builder-lib ^26.0.0 API guidance for programmatic use, with runnable checks for architecture and platform helpers and cautions about packaging-only APIs.

For
app-builder-lib@26.15.3
Verified
2026-09-08, 2 examples executed
Package
@modootoday/pmcp-app-builder-lib@26.0.0

What it covers

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here. 

import assert from "node:assert/strict";
import { Arch, archFromString } from "app-builder-lib";

assert.equal(Arch.ia32, 0);
assert.equal(Arch.x64, 1);
assert.equal(Arch.armv7l, 2);
assert.equal(Arch.arm64, 3);
assert.equal(Arch.universal, 4);

assert.equal(archFromString("ia32"), Arch.ia32);
assert.equal(archFromString("x64"), Arch.x64);
assert.equal(archFromString("armv7l"), Arch.armv7l);
assert.equal(archFromString("arm64"), Arch.arm64);
assert.equal(archFromString("universal"), Arch.universal);

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription: 

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-app-builder-lib

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.