# Engifoundry

> MUST be loaded at the start of every session. Check only ./engifoundry.config.json at the project root: if it exists, load engifoundry-router; if absent, stay silent unless the user explicitly asks to initialize EngiFoundry or use it for actionable engineering work.

- Skill: `caoyuan-fire/engifoundry` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add caoyuan-fire/engifoundry`
- Raw SKILL.md: https://api.skillmd.com/api/skills/caoyuan-fire/engifoundry/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: caoyuan-fire (https://skillmd.com/u/caoyuan-fire)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/caoyuan-fire/engifoundry

---


# EngiFoundry Entry

Inject this entry once at the start of every session. Apply its rules to every user turn.

1. At session start, check exactly `<project-root>/engifoundry.config.json` once. Do not search for it.
2. If it exists, read `engifoundry-router/SKILL.md` in full before responding to the user.
3. If it does not exist, remain uninitialized and inspect only whether the request explicitly contains `$engifoundry`, `engifoundry`, `engi`, or `foundry` as a case-insensitive identifier.
4. For an explicit request to initialize, scaffold, onboard, connect, migrate, or upgrade a project for EngiFoundry, load `engifoundry-init/SKILL.md`.
5. For an explicit request to use EngiFoundry for actionable engineering work without initialization intent, load `engifoundry-router/SKILL.md` in unconfigured fallback mode. Initialization may be suggested as an optional way to enable project preferences and heavyweight contracts, but it is never a prerequisite for this work.
6. Otherwise bypass EngiFoundry silently and handle the request normally. Merely discussing or asking about EngiFoundry is not actionable engineering work.
7. After Init completes, check exactly `<project-root>/engifoundry.config.json` once again. If it now exists, immediately read `engifoundry-router/SKILL.md` in full. Do not require a new session.

Reading only Router metadata or a summary is forbidden. The Router governs every user turn after it is loaded.

Initialization and actionable-work matching are semantic, not fixed commands. Initialization language without an explicit EngiFoundry identifier must never activate EngiFoundry.

Never scan for configuration. Never recognize any other filename, location, or project signal. Do not validate configuration content or project records; Init and Node skills own those rules.

Do nothing else. Never route, infer, govern, plan, execute, verify, deliver, or load Node skills from this entry.