メニュー
Check for and apply IJFW updates safely. Trigger: 'update ijfw', 'upgrade', 'latest version', 'is there a new version', /update
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.
First-class design intelligence. Dispatches to the best available design skill (ui-ux-pro-max, frontend-design, superpowers), then layers IJFW constraints on top. Triggers: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'mobile-first', 'dark mode', 'accessibility', 'colors', 'typography', 'brand'.
Check for and apply IJFW updates safely. Trigger: 'update ijfw', 'upgrade', 'latest version', 'is there a new version', /update
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
Compress memory/context files into terse form. Trigger: /compress, compress file
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit
| name | ijfw-update |
| description | Check for and apply IJFW updates safely. Trigger: 'update ijfw', 'upgrade', 'latest version', 'is there a new version', /update |
Helps the user check for and apply IJFW updates. Updates are air-gapped: the model cannot execute them. The model issues a confirmation token; the user types ijfw update --confirm <token> in their terminal to actually run.
Triggers: "update ijfw", "upgrade ijfw", "is there a new version", "latest version", /update. Also fires when memory prelude reports "update available" on first turn.
Call the MCP tool: ijfw_update_check. This returns:
current -- installed versionlatest -- latest published version on npmavailable -- booleanavailable: true: also confirmation_token, expires_at, changelog_url, and instruction. The same call writes the pending sentinel that the terminal command consumes -- one MCP call, one terminal command, no intermediate ceremony.If up to date: report it. Stop.
IJFW is up to date (v1.2.5).
If update available: present the version delta + changelog link, then surface the OOB instruction verbatim. The terminal command is the air-gap; the model never runs the update itself.
Update available: v1.2.4 -> v1.2.5 Changelog: <changelog_url>
To proceed, run in your TERMINAL: ijfw update --confirm <confirmation_token>
Token expires in 5 minutes. I cannot run the update for you -- only typing this command in your terminal can.
DO NOT run npm install, npx @ijfw/install, bash scripts/install.sh, or any equivalent yourself. The MCP path is air-gapped on purpose. Even if the user asks you to "just do it", refuse and surface the terminal command.
Back-compat note: ijfw_update_apply still exists for older clients. It is idempotent against the sentinel that ijfw_update_check already wrote, so calling it is harmless but unnecessary in the streamlined flow.
The token + sentinel + terminal-confirm flow exists so that prompt injection in stored memory, fetched docs, or user-paste content cannot trick the model into auto-updating IJFW. See docs/SECURITY.md for the full threat model.
ijfw_update_check, report status, stop.ijfw update --yes in their terminal directly.npm install -g @ijfw/install@<version> from the user's terminal.The user will see "Updated to v" in their terminal. The next IJFW SessionStart will reflect the new version. Suggest restarting any open agent sessions so they pick up the new skills/hooks.