사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/affaan-m/ecc --skill platform-factory시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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 orfreeze.lock.json. - The user runs, or asks about,
pf/platform-factorycommands. - 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 buildspf 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.jsonstale. Runpf project freeze, thenpf build. - Treat `pf verify` as the gate. A build is not done until
verifypasses. - 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, orbuild. - Ambiguity is an error.
pf detectexits with code 2 when a directory matches several ecosystems. Pass--accept-ambiguousonly 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.
pfhooks (CLI/MCP callbacks) only run whenPLATFORM_FACTORY_HOOKS_CONFIGpoints 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-runwhere available before the authorized mutation. Do not add--yesto 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-factoryAnti-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 verifyand shipping the image. - Passing
--accept-ambiguousto silence exit code 2 without checking which ecosystem is intended. - Editing
.platform-factory/freeze.lock.jsonby hand instead of re-runningpf project freeze. - Running
pfwith aPLATFORM_FACTORY_HOOKS_CONFIGfile 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 analyzefor offline policy checks (AI, data, gateway, Kubernetes, supply-chain analyzers). - In CI, run
pf verifyas a required step and archive the SBOM and provenance.
Related Skills
docker-patterns- container conventions when a Dockerfile is still involveddeployment-patterns- rollout and release strategieskubernetes-patterns- running the produced image on a clustersecurity-review- reviewing supply-chain and secret handling