AIPM
Theme

AIPM package

Platform Factory

@affaan-m/platform-factory@1.0.0

Build deterministic OCI images, SBOM/provenance evidence and hardened container or microVM runs from a compiled executable with the Platform Factory (pf) CLI…

Scanned · no issues · Nov 17, 2026

GitHub stars: ★ 305K

LinkedInPost

Install Skill

Pins this version in aipm.package.json and aipm-lock.json.

aipm add @affaan-m/platform-factory@1.0.0

Without project tracking

Writes the skill files only. Add --no-init to skip aipm.package.json and the lockfile.

aipm add @affaan-m/platform-factory@1.0.0 --no-init

How to use

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.

Core Workflow

bash
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

  1. Freeze before build. Any change to a dependency manifest makes .platform-factory/freeze.lock.json stale. Run pf project freeze, then pf build.
  2. Treat pf verify as the gate. A build is not done until verify passes.
  3. 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.
  4. 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.
  5. Never add secrets to build inputs. Inputs end up in the image and its evidence.
  6. 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.
  7. 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:

EventTriggerBehavior
PostToolUseEdit/Write/MultiEdit on a dependency manifestReminds you to run pf project freeze
PreToolUseBash running pf build|publish|launch|deployWarns 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+):

text
/plugin marketplace add CYPT71/platform-factory
/plugin install platform-factory-guard@platform-factory

Anti-Patterns

bash
# 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

Loading package files…

Share this package

Add an Install with AIPM badge

Add this badge to a GitHub README so readers can open the package page and install the same version.

Install with AIPM
[![Install with AIPM](https://www.aipm-registry.com/install-with-aipm.svg)](https://www.aipm-registry.com/skills/affaan-m/platform-factory/1.0.0?utm_source=github&utm_medium=readme&utm_campaign=package_badge)

Publisher

Affaan Mustafa

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...

Install
aipm add @affaan-m/platform-factory@1.0.0
Use after install
/platform-factory <your description>

Tool targets

Install command by target

Add --no-init to any of these when you want the skill files without aipm.package.json or aipm-lock.json.

cursor

Run this variant when you want to install the package into cursor.

aipm add @affaan-m/platform-factory@1.0.0 --target cursor --ci

claude

Run this variant when you want to install the package into claude.

aipm add @affaan-m/platform-factory@1.0.0 --target claude --ci

Discussion

Comments (0)

Loading comments…

Keep exploring

Affaan Mustafa/ui-canvas

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...

Published by Affaan Mustafa

skillScanned · no issues★ 308KImported · UnverifiedAll toolsNov 21, 2026, 1:11 AM6.61 KBMIT

Affaan Mustafa/yoruba-localization-testing

Test Yoruba (yo) and English bilingual interfaces for tone marks, underdots, Unicode normalization, translation fallback, and accessibility.

Published by Affaan Mustafa

skillScanned · no issues★ 306KImported · UnverifiedAll toolsNov 18, 2026, 1:19 AM3.43 KBMIT

Affaan Mustafa/web-perimeter-owasp-2025-audit

Passive, non-destructive web perimeter security auditing mapped to OWASP Top 10:2025 surface leads, CDN Unkeyed Header Web Cache Poisoning (X-Forwarded-Host), supply chain manifest exposure, git object dumping prevention (/.git/HEAD), cr...

Published by Affaan Mustafa

skillScanned · flagged★ 305KImported · UnverifiedAll toolsNov 17, 2026, 1:13 AM8.86 KBMIT

Package FAQ

Install and compatibility

How to install
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.