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.
Core Workflow
pf detect ./my-app # native executable inspection; JSON output
# Directory detection runs loaded language-plugin inspection commands.
pf init --language node . # create pf.yaml (language plugin must be loaded: pf plugin load node)
pf plan # project plan (platform-factory.dev/project-plan/v1)
pf project freeze # pin dependencies -> .platform-factory/freeze.lock.json
pf build # deterministic OCI image
pf verify .platform-factory/image # strict release gate: digests, diff_ids, platforms
pf run --runtime podman .platform-factory/image
pf diff # compare builds
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.
Install it as a plugin (requires Node.js 18+):
/plugin marketplace add CYPT71/platform-factory
/plugin install platform-factory-guard@platform-factory
Anti-Patterns
# 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
1---2name: platform-factory3description: 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 project contains .platform-factory/, when the user runs or asks about pf/platform-factory (detect, plan, freeze, build, verify, run, launch), or wants reproducible OCI builds without a Docker daemon.4metadata:5 source: https://skillmd.com/skills/affaan-m/platform-factory6 origin: community7---89# Platform Factory1011[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.1213Full reference: the project's [CLI guide](https://github.com/CYPT71/platform-factory/blob/main/docs/cli-guide.md). This skill covers the workflow an agent should follow and the guard hook that protects it.1415## When to Activate1617- The repository has a `.platform-factory/` directory or `freeze.lock.json`.18- The user runs, or asks about, `pf` / `platform-factory` commands.19- The task is reproducible OCI image builds, SBOM/provenance evidence, or microVM execution of a legacy or dynamically linked binary.20- You edit a dependency manifest (`package-lock.json`, `go.sum`, `requirements.txt`, `Cargo.lock`, `pom.xml`, ...) in a Platform Factory project.2122## Core Workflow2324```bash25pf detect ./my-app # native executable inspection; JSON output26# Directory detection runs loaded language-plugin inspection commands.27pf init --language node . # create pf.yaml (language plugin must be loaded: pf plugin load node)28pf plan # project plan (platform-factory.dev/project-plan/v1)29pf project freeze # pin dependencies -> .platform-factory/freeze.lock.json30pf build # deterministic OCI image31pf verify .platform-factory/image # strict release gate: digests, diff_ids, platforms32pf run --runtime podman .platform-factory/image33pf diff # compare builds34```3536`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.3738### Rules that matter39401. **Freeze before build.** Any change to a dependency manifest makes `.platform-factory/freeze.lock.json` stale. Run `pf project freeze`, then `pf build`.412. **Treat `pf verify` as the gate.** A build is not done until `verify` passes.423. **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`.434. **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.445. **Never add secrets to build inputs.** Inputs end up in the image and its evidence.456. **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.467. **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.4748## Companion Claude Code Hook: freeze guard4950The project ships a Claude Code plugin, [`platform-factory-guard`](https://github.com/CYPT71/platform-factory/tree/main/integrations/claude-code), that runs next to ECC's own hooks:5152| Event | Trigger | Behavior |53|-------|---------|----------|54| `PostToolUse` | `Edit`/`Write`/`MultiEdit` on a dependency manifest | Reminds you to run `pf project freeze` |55| `PreToolUse` | `Bash` running `pf build\|publish\|launch\|deploy` | Warns when a manifest is newer than the freeze lock; denies if `PF_GUARD_STRICT=1` |5657It 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`.5859Install it as a plugin (requires Node.js 18+):6061```text62/plugin marketplace add CYPT71/platform-factory63/plugin install platform-factory-guard@platform-factory64```6566## Anti-Patterns6768```bash69# BAD: build right after changing dependencies70npm install left-pad && pf build7172# GOOD: refresh the lock first73npm install left-pad && pf project freeze && pf build && pf verify .platform-factory/image74```7576- Skipping `pf verify` and shipping the image.77- Passing `--accept-ambiguous` to silence exit code 2 without checking which ecosystem is intended.78- Editing `.platform-factory/freeze.lock.json` by hand instead of re-running `pf project freeze`.79- Running `pf` with a `PLATFORM_FACTORY_HOOKS_CONFIG` file you did not review.8081## Best Practices8283- 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.84- 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.85- Use `pf extensions list` / `pf extensions analyze` for offline policy checks (AI, data, gateway, Kubernetes, supply-chain analyzers).86- In CI, run `pf verify` as a required step and archive the SBOM and provenance.8788## Related Skills8990- `docker-patterns` - container conventions when a Dockerfile is still involved91- `deployment-patterns` - rollout and release strategies92- `kubernetes-patterns` - running the produced image on a cluster93- `security-review` - reviewing supply-chain and secret handling