Comparison with prometheus-skill-pack
The current mini distribution contains 97 skills, including 40 portable UI/UX entries from a shared 41-entry catalog. Selected React/Vercel and mobile UI guidance is now included; the broader entity-management, DevOps and testing families remain outside this port.
UI/UX and project teams
| Capability | Current scope |
|---|---|
| Shared UI/UX protocol and router | Context first, project protocol override, focused Pro Max query, one craft selection and manifest-based platform guidance. |
| Taste selection | New work uses the actual model family; explicit redesign uses redesign guidance. Refinement and review exclude taste and overlays. |
| Pro Max | TypeScript 7 with shipped Node ESM and pinned assets; no Python, runtime download or extra service. |
| Impeccable | Full-only native engine is excluded. Mini carries bounded prometheus-impeccable-core context/workflow guidance, without native detector/browser parity. |
| Completed-phase review | phase-boundary emits an unexecuted evidence contract; prometheus-ui-review requires independent read-only review and real acceptance evidence. User-only skills remain user-only. |
| Project teams | Creator install-project installs discovery records/instructions and missing native definitions. Explicit team selection wins, a sole team is adopted, and ambiguity requires a choice. Export alone remains proposal-only. |
| Native authority | Existing files, role ownership, permissions, model configuration and concurrency are preserved. Zed instructions are supported; unavailable native delegation uses disclosed sequential role instructions. |
Follow UI/UX routing and adoption and Agent Teams. The prior delivery record records macOS and offline Linux-container integration plus packaged-helper evidence. Native Windows execution, live invocation of every harness and full Electron installed-app acceptance remain unverified. These are implementation/evidence limits, not current release certification.
Historical process-port baseline
The following process-port snapshot was recorded at commit 8497ae8 (the Phase C KBD port).
Its module test totals and older platform gaps describe that boundary only. They do not report
results from the current documentation change or certify the later UI/team implementation.
Process capabilities at the recorded boundary
| Capability | Status |
|---|---|
KBD lifecycle (24 skills: parent + 22 sub-skills + kbd-evolve/kbd-goal-check) | Ported. See KBD Skills. |
KBD state-machine core (lib/kbd/, 12 modules) | Ported, 230 tests. |
Adversarial review (lib/review/, skills/adversarial-review/) | Ported, 176 tests. Cross-model judge dispatch, packet builder, sycophancy anti-theater gate, decision log, model-role resolution. python3 and curl eliminated. |
Ideation mindmap (lib/ideation/, skills/ideation-mindmap/) | Ported, 38 tests. Independent-dispatch recording and structural verification. |
Karpathy progress memory (lib/karpathy/) | Ported (already complete in a prior session; verified, not rebuilt, in the Phase C commit). |
Plugin/marketplace distribution (lib/distribution/, skill-system.json) | Ported, 61 tests. Claude Code + Codex packages, both marketplaces, the slash-command generator. Copy-mode throughout, never symlink. |
Artifact refinement (lib/refiner/, 20 skills) | Ported. See Artifact Refinement. |
| OpenSpec integration (12 skills × 4 harnesses) | Ported and the default planning backend. |
Platform primitives (lib/platform/) | Ported and CI-verified on Windows (platform-foundation phase): atomic write, lock, CRLF-tolerant text, shell-free spawn. |
Docker services (docker/compose.yaml, docker/compose.build.yaml, scripts/services.mjs) | Ported. Three containers (SurrealDB, surreal-memory, liter-llm), loopback-bound, env-file secrets, named volumes, memory limits, digest-pinned SurrealDB image. This was listed as a future roadmap item in earlier documentation; it now exists on disk. |
Doctor (lib/doctor/, skills/doctor/) | Ported. Runtime, KBD position, services, optional tools, home-directory skill copies, and the install-scope rule, in that report order. |
Context bootstrap (lib/context-bootstrap/) | Ported. |
What is a deliberate exclusion (not a gap)
These are excluded by explicit constraint, not because porting them was deferred:
| Excluded | Why |
|---|---|
| ZeeSpec | openspec/config.yaml binding constraint: OpenSpec is the default; no ZeeSpec anywhere. |
| Python anywhere | Hard constraint (C4 in the original port analysis). Every Python call site in the source pack (record-progress.py, state-* scripts' python3 invocations) was translated to Node stdlib (JSON.parse/stringify, crypto.randomUUID(), toISOString()). |
Shell scripts (.sh) | Hard constraint. Hooks use exec-form Node commands exclusively. |
| Symlink-based installs | This pack's installer and distribution generator are copy-mode only — the full pack symlinks 11 of 13 install targets, which needs Developer Mode or elevation on Windows. |
The Rust execution substrate (prometheus-exec, substrate/*, the research daemon, the surface bridge) | Unix-socket daemons and sandbox machinery with no Windows-native design; explicitly out of scope for this pack's process-focused architecture. |
prometheus-knowledge's HTTP companion (pk-cherry) and its learning-worker timer daemon | This pack replaced the timer/worker model with durable receipts flushed opportunistically at SessionStart — see Karpathy Progress Memory. |
| Entity-management, DevOps/GitOps and BDD/Cucumber families | Deliberately outside this port. Selected React/Vercel UI guidance is now included through the UI catalog; that does not add the full entity-development family. |
karpathy-tokenizer | Despite the name, it trains BPE tokenizers via Python (rustbpe, tiktoken) — unrelated to Karpathy logging, and a Python dependency either way. |
native-agent / start-business-build | Generates a full service stack by design (Docker + surreal-memory + pk + liter-llm as application dependencies, not this pack's own two services) — out of scope for a process-focused mini pack. |
Recorded gaps and acceptance limits
The UI/team acceptance gaps are listed above. The historical process-port notes below remain boundary-scoped records, distinct from the deliberate exclusions:
- Deep research. Planned as a checkpoint-only Node port (
openspec/config.yaml: "deep-research ... runs in checkpoint mode only"; the Rustprometheus-researchserver is explicitly not shipped). Not present in this checkout as a skill yet. Sycophancy correction (as a standing hook, not the review-pipeline gate) is optional and off by default per the original port analysis — the review pipeline's ownlib/review/sycophancy-binary.mjs/sycophancy-gate.mjsare ported and active; a project-widesycophancy-correctionMCP server integration is a separate, still-optional item. - Windows runtime verification for the Phase C batch.
platform-foundation's Windows claims are CI-verified onwindows-latest. The later KBD/adversarial-review/ideation-mindmap/distribution work (1,000+ tests) ran on macOS only as of the port commit — Windows verification for that batch is recorded as still owed, not assumed passing. See Windows Constraints. versions.toml's[npm]table.docs/versions-toml.mddocuments a proposed[npm]table pinning@docusaurus/core/@docusaurus/preset-classicfor this very docs site, gating adocs-siteOpenSpec change. As of this writing,versions.tomlhas[node],[submodules], and[images]tables, but no[npm]table yet — the operator has not authored it. This documentation site itself was built ahead of that formal gate being satisfied;rules/test/versions-toml.test.mjswill need an[npm]entry before adocs-siteOpenSpec change can pass its own first task.- Neither container stack has been run on real Windows hardware. The Compose design is derived from reading Dockerfiles/Compose files; image build time, VM memory during build, and first-start model download for local embeddings remain unmeasured on Windows, per the original port analysis's own open questions.
- Rust toolkit skills remain thinner than the full pack's. This pack has one house-router skill
(
prometheus-rust-workspace) that routes to externally-installed skills rather than vendoring a full parallel set ofmcp-server/rust-cli/workspace-structure/etc. skills the way the full pack does. See Rust Workspace Guidance.
Skill count
This pack ships 97 distributed skill directories under skills/,
versus the full pack's much larger multi-hundred-skill catalog spanning many domains this pack does
not attempt to cover (entity development, DevOps/GitOps, BDD testing, Feynman learning,
broad multi-language guidance, native-agent generation, and more). See the
Skills Catalog for the complete, generated list.
See also
- Introduction — the top-level framing of why this port exists.
- Windows Constraints — the rules every ported capability follows.