菜单
Use liberally when you discover or are told a non-negotiable constraint — something that must always be true regardless of context. Registers the invariant so future sessions never violate it.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jumbocontext/cli --skill jumbo-add-invariant命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when a Jumbo goal needs QA review after implementation. Runs the review protocol, verifies every objective, criterion, and related entity constraint, and approves the goal for codification or rejects it with feedback.
Use when the user's prompt is delivered outside the execution context of an existing Jumbo goal, the prompt is imbued with an objective that is not already defined as a Jumbo goal.
Use when a Jumbo-managed agent file tells the agent to bootstrap the session. Runs Jumbo's session router only when the agent has not already received a routed Jumbo command.
基于 SOC 职业分类
正在显示 SKILL.md
| name | jumbo-add-invariant |
| description | Use liberally when you discover or are told a non-negotiable constraint — something that must always be true regardless of context. Registers the invariant so future sessions never violate it. |
Register an invariant with Jumbo when you discover a non-negotiable constraint — a rule that must hold true across the entire project at all times, regardless of which goal is being implemented.
Important: Invariants must be generally applicable to the project. Do not word them for a specific use case, goal, or task. An invariant that only applies during one piece of work belongs in a goal's criteria, not in the invariant registry. If you find yourself writing "when working on X" or "for the Y feature", it is not an invariant.
Check for an existing invariant to avoid duplication. Consider reversing, updating, or superseding a previously registered invariant before registering a new one.
Use the search subcommand to locate previously registered invariants:
jumbo invariants search -q <query>
jumbo invariant add \
--title "<Invariant title>" \
--description "<What must always be true>" \
--rationale "<Why this is non-negotiable>"
jumbo invariant add \
--title "Session endpoint must validate tokens" \
--description "The /api/session endpoint must check JWT expiry" \
--rationale "Security requirement for session management"
Too narrow — applies to one endpoint. This is a requirement for a specific feature, not a project-wide invariant.
jumbo invariant add \
--title "All API endpoints must validate authentication tokens" \
--description "Every endpoint that accepts authenticated requests must verify token validity, expiry, and scope before processing the request" \
--rationale "Security compliance requirement — unauthenticated access to protected resources is a critical vulnerability"
Applies to every endpoint, not just one. States the full constraint. Rationale explains why violation is unacceptable.