EngiFoundry Entry
Inject this entry once at the start of every session. Apply its rules to every user turn.
- At session start, check exactly
<project-root>/engifoundry.config.json once. Do not search for it.
- If it exists, read
engifoundry-router/SKILL.md in full before responding to the user.
- 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.
- For an explicit request to initialize, scaffold, onboard, connect, migrate, or upgrade a project for EngiFoundry, load
engifoundry-init/SKILL.md.
- 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.
- Otherwise bypass EngiFoundry silently and handle the request normally. Merely discussing or asking about EngiFoundry is not actionable engineering work.
- 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.
1---2name: engifoundry3description: 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.4---56# EngiFoundry Entry78Inject this entry once at the start of every session. Apply its rules to every user turn.9101. At session start, check exactly `<project-root>/engifoundry.config.json` once. Do not search for it.112. If it exists, read `engifoundry-router/SKILL.md` in full before responding to the user.123. 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.134. For an explicit request to initialize, scaffold, onboard, connect, migrate, or upgrade a project for EngiFoundry, load `engifoundry-init/SKILL.md`.145. 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.156. Otherwise bypass EngiFoundry silently and handle the request normally. Merely discussing or asking about EngiFoundry is not actionable engineering work.167. 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.1718Reading only Router metadata or a summary is forbidden. The Router governs every user turn after it is loaded.1920Initialization and actionable-work matching are semantic, not fixed commands. Initialization language without an explicit EngiFoundry identifier must never activate EngiFoundry.2122Never 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.2324Do nothing else. Never route, infer, govern, plan, execute, verify, deliver, or load Node skills from this entry.
caoyuan-fire