Build deterministic OCI images, SBOM/provenance evidence and hardened container or microVM runs from a compiled executable with the Platform Factory (pf) CLI…
Install the skill above, then run this in your AI tool:
/platform-factory <your description>
About
[Platform Factory](https://github.com/CYPT71/platform-factory) (`platform-factory`, alias `pf`) is a single Go binary that turns a compiled executable into a deterministic OCI image, attaches native supply-chain evidence (SBOM, provenance, signatures, policy) and runs the result as a hardened container or a KVM/HVF microVM. No Docker daemon, BuildKit, syft or cosign is needed for the core path. It plugs into an existing stack; it does not replace Kubernetes, CI orchestrators or registries.
Source
What gets added to your project
Preview every file this package writes on install before you run the command above.
Summary
Build deterministic OCI images, SBOM/provenance evidence and hardened container or microVM runs from a compiled executable with the Platform Factory (pf) CLI, and keep its freeze lock in sync with a companion Claude Code hook. Use when a...
Skill instructions
Platform Factory
Platform Factory (platform-factory, alias pf) is a single Go binary that turns a compiled executable into a deterministic OCI image, attaches native supply-chain evidence (SBOM, provenance, signatures, policy) and runs the result as a hardened container or a KVM/HVF microVM. No Docker daemon, BuildKit, syft or cosign is needed for the core path. It plugs into an existing stack; it does not replace Kubernetes, CI orchestrators or registries.
Full reference: the project's CLI guide. This skill covers the workflow an agent should follow and the guard hook that protects it.
When to Activate
The repository has a .platform-factory/ directory or freeze.lock.json.
The user runs, or asks about, pf / platform-factory commands.
The task is reproducible OCI image builds, SBOM/provenance evidence, or microVM execution of a legacy or dynamically linked binary.
You edit a dependency manifest (package-lock.json, go.sum, requirements.txt, Cargo.lock, pom.xml, ...) in a Platform Factory project.
pf launch --publish --yes freezes when required, builds, verifies, publishes to a registry and then starts the workload in one step, so it is an outward-facing action (see rule 7). pf sbom PATH... produces a reproducible SBOM natively.
Rules that matter
Freeze before build. Any change to a dependency manifest makes .platform-factory/freeze.lock.json stale. Run pf project freeze, then pf build.
Treat pf verify as the gate. A build is not done until verify passes.
Inspect plugins before directory detection. Native executable classification does not run the target, but directory detection invokes loaded language plugins. Review those plugins and project commands as executable configuration before detect, plan, freeze, or build.
Ambiguity is an error.pf detect exits with code 2 when a directory matches several ecosystems. Pass --accept-ambiguous only when the user confirmed the choice.
Never add secrets to build inputs. Inputs end up in the image and its evidence.
Callbacks are opt-in.pf hooks (CLI/MCP callbacks) only run when PLATFORM_FACTORY_HOOKS_CONFIG points to an explicit absolute file, so a cloned repository cannot activate executables.
Keep execution within the user's authorization. Before publishing, deploying, launching, or running a workload, identify its target, image reference, and effects. Reuse explicit authorization already given for that scope; ask only when the action exceeds it. Use --dry-run where available before the authorized mutation. Do not add --yes to bypass an approval the user has not given.
Companion Claude Code Hook: freeze guard
The project ships a Claude Code plugin, platform-factory-guard, that runs next to ECC's own hooks:
Event
Trigger
Behavior
PostToolUse
Edit/Write/MultiEdit on a dependency manifest
Reminds you to run pf project freeze
PreToolUse
Bash running pf build|publish|launch|deploy
Warns when a manifest is newer than the freeze lock; denies if PF_GUARD_STRICT=1
It never executes pf, recognizes project configuration such as pf.yaml as well as .platform-factory/, ignores the per-user plugin directory as a project marker, and fails open. Disable with PF_GUARD=off.
# BAD: build right after changing dependencies
npm install left-pad && pf build
# GOOD: refresh the lock first
npm install left-pad && pf project freeze && pf build && pf verify .platform-factory/image
Skipping pf verify and shipping the image.
Passing --accept-ambiguous to silence exit code 2 without checking which ecosystem is intended.
Editing .platform-factory/freeze.lock.json by hand instead of re-running pf project freeze.
Running pf with a PLATFORM_FACTORY_HOOKS_CONFIG file you did not review.
Best Practices
Build the executable statically when possible (CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -trimpath -ldflags='-s -w') so the image is small and reproducible.
Select a container or microVM from the workload's isolation requirements and available host support. This external CLI guide does not certify an ECC sandbox tier or replace ECC capability/evidence policy.
Use pf extensions list / pf extensions analyze for offline policy checks (AI, data, gateway, Kubernetes, supply-chain analyzers).
In CI, run pf verify as a required step and archive the SBOM and provenance.
Related Skills
docker-patterns - container conventions when a Dockerfile is still involved
deployment-patterns - rollout and release strategies
kubernetes-patterns - running the produced image on a cluster
security-review - reviewing supply-chain and secret handling
Add this badge to a GitHub README so readers can open the package page and install the same version.
[](https://www.aipm-registry.com/skills/affaan-m/platform-factory/1.0.0?utm_source=github&utm_medium=readme&utm_campaign=package_badge)
This imported publisher has not claimed its AIPM account. A connected account confirms account control, but it does not guarantee that a package is safe.
AI assistant context
What this skill is for
@affaan-m/platform-factory@1.0.0 is an AIPM skill package for All tools. Use it when a project needs the reusable AI behavior described as: Build deterministic OCI images, SBOM/provenance evidence and hardened container or microVM runs from a compiled executable with the Platform Factory (pf) CLI, and keep its freeze lock in sync with a companion Claude Code hook. Use when a...
Preview a UI component mockup in a local browser canvas where the human directly edits it (move, resize, edit text, delete, restyle), switches mobile/desktop/custom viewports, tests it, chats with you, and clicks Save and Finish. You the...
Run aipm add @affaan-m/platform-factory@1.0.0 in a project that has AIPM initialized.
Supported tools
@affaan-m/platform-factory@1.0.0 supports All tools.
Before installing
AIPM skills can add files to your project. Review the package name, target, description, license, and publisher before installing. Use a clean branch when trying a new skill.