菜单
Use liberally when the user expresses a preference about how work should be done — coding style, process, testing approach, communication style. Captures the guideline so future sessions follow it without being told again.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | jumbo-add-guideline |
| description | Use liberally when the user expresses a preference about how work should be done — coding style, process, testing approach, communication style. Captures the guideline so future sessions follow it without being told again. |
Register a guideline with Jumbo when the user states a preference about how work should be done. Guidelines shape agent behavior across all future sessions.
Important: Guidelines must be generally applicable to the project. Do not word them for a specific use case, goal, or task. A guideline that only applies to one situation belongs in a goal's criteria, not in the guideline registry.
Check for an existing guideline to avoid duplication. Consider removing, or updating, a previously registered guideline before registering a new one.
Use the search subcommand to locate previously registered guidelines:
jumbo guidelines search -q <query>
jumbo guideline add \
--category "<testing|codingStyle|process|communication|documentation|security|performance|other>" \
--title "<Guideline title>" \
--description "<What to do and when>" \
--rationale "<Why this matters>"
jumbo guideline add \
--category codingStyle \
--title "Use arrow functions in the auth module" \
--description "All functions in src/auth/ should be arrow functions" \
--rationale "Consistency in auth code"
Too narrow — scoped to one module and one task. This is a goal criterion, not a project guideline.
jumbo guideline add \
--category codingStyle \
--title "Prefer arrow functions for non-method declarations" \
--description "Use arrow functions for callbacks, inline handlers, and standalone function expressions. Use function declarations for exported named functions and class methods." \
--rationale "Consistent lexical scoping and concise syntax across the codebase"
Applies project-wide. States when to use and when not to use. Rationale explains the benefit.
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.