メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Use when an agent needs to discover Jumbo command syntax after session routing. Directs command discovery through CLI help instead of static command catalogs.
Use when implementation discovers durable project context that must be recorded in Jumbo. Captures decisions, components, dependencies, relations, guidelines, and invariants during the work.
Use when the user corrects an approach, constraint, workflow, or style. Converts corrections into Jumbo guidelines or invariants so future sessions receive the constraint.
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing. Captures new learnings, updates stale entities, and ensures documentation reflects the work performed.
| 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.