PrimeLab Foundation avatar

PrimeLab Foundation

Official

@PrimeLab-Foundation

0Followers
|
3Public Repos
|
7Published Skills

PrimeLab Foundation maintains strata, a C++ JSON parsing library with CPython bindings, JSONPath evaluation, and a documented build, benchmark, and performance engineering knowledge base.

Skills Distribution
DomainDeveloper To...C++ JSON Parsing E.. (35%)CPython Binding La.. (20%)JSONPath Query Eva.. (20%)Build, Test & CI I.. (15%)

Agent Skills by PrimeLab Foundation

Showing 7 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About PrimeLab Foundation

FAQPage Schema
What 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.