PrimeLab Foundation
Official@PrimeLab-Foundation
PrimeLab Foundation maintains strata, a C++ JSON parsing library with CPython bindings, JSONPath evaluation, and a documented build, benchmark, and performance engineering knowledge base.
Agent Skills by PrimeLab Foundation
Showing 7 vetted skills indexed across 1 GitHub repositories.
jsonpath
Documents the JSONPath grammar, evaluators, and semantic divergences of the strata search subsystem.
roadmap
Defines ordered rebuild milestones with acceptance criteria for incremental implementation sessions.
build-and-test
Documents the Makefile, CMake, and CI build-and-test pipeline for the strata C++20 Python extension.
architecture
Documents the C++ core architecture of the strata JSON engine for contributors.
bindings
Documents the CPython C-API binding layer for the strata JSON extension module.
benchmarking
Documents benchmark harness internals, standings, and regression tooling for the strata JSON library.
performance
Documents measured optimization techniques, negative results, and benchmark evidence for the Strata JSON engine.
Frequently Asked Questions About PrimeLab Foundation
FAQPage SchemaWhat tasks can I accomplish using PrimeLab Foundation's skills?▼
The skills guide contributors through the strata JSON library: modifying the C++ SAX/DOM parser core, editing the CPython binding layer, working on the three JSONPath evaluators, running builds and parity tests, executing benchmarks, and planning performance work from documented measured results.
Who are these skills designed for?▼
They target systems engineers and open-source contributors working on the strata codebase — specifically developers touching src/strata/, include/strata/, the bindings layer, Makefile/CMake build files, benchmark harnesses, or anyone needing project lineage context from the archive before attempting changes.
How do I use these skills during a development session?▼
Load the roadmap skill first to pick exactly one milestone increment, then load the domain skill matching the files you will touch — architecture, bindings, jsonpath, build-and-test, or benchmarking — before editing. Each skill defines load triggers tied to specific source directories.
What prerequisites and dependencies do these skills require?▼
Skills assume access to the strata repository with its C++ core, CPython bindings, Makefile/CMake build system, test suites, and benchmark harness. The history skill additionally requires the ../archive/ directory containing turbojsonpath origins and shelved rewrite artifacts.
Do these skills cover known bugs and failed approaches?▼
Yes. The manifest explicitly documents a known cycle_policy bug in config-to-policy mapping, currently-broken build tooling, the old regression tool's defects, abandoned optimization campaigns, and negative performance results so contributors do not reproduce or retry failed ideas.