القائمة
Use liberally when you create, discover, or modify a software component. Registers the component with Jumbo so future sessions have accurate architectural context.
التثبيت باستخدام 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-component |
| description | Use liberally when you create, discover, or modify a software component. Registers the component with Jumbo so future sessions have accurate architectural context. |
Register a software component with Jumbo when you create one, discover an unregistered one, or significantly change one's responsibility.
Check for an existing component to avoid duplication. Consider renaming, updating, or deprecating and replacing a previously registered component before registering a new one.
Use the search subcommand to locate previously registered components:
jumbo components search -q <query>
jumbo component add \
--name "<ComponentName>" \
--type "<service|db|queue|ui|lib|api|worker|cache|storage>" \
--description "<What the component does>" \
--responsibility "<Single responsibility>" \
--path "<file-path>"
jumbo component add \
--name "Utils" \
--type "lib" \
--description "Helper functions" \
--responsibility "Various utilities" \
--path "src/utils.ts"
Vague name, description, and responsibility. A future agent cannot determine what this component does or whether to use it.
jumbo component add \
--name "EventStreamProjectionBuilder" \
--type "service" \
--description "Rebuilds materialized projections from event streams by replaying events through registered projection handlers" \
--responsibility "Projection rebuilding from event history" \
--path "src/infrastructure/projections/EventStreamProjectionBuilder.ts"
Name is self-documenting. Description and responsibility tell a future agent exactly what the component does and when to interact with it.