Nenji

Nenji is the default guide inside Nenjo. It is designed to help you turn a blank workspace into a working system of projects, agents, routines, knowledge, permissions, and execution infrastructure.

Use Nenji when you know what outcome you want but do not yet know which Nenjo resources should exist. It can help you shape the workspace, ask clarifying questions, draft resource configurations, and connect the pieces through the platform.

What Nenji was designed for

Nenji is a bootstrap and orchestration agent. Its job is to help you:

• Map your work into Nenjo resources
• Create useful first projects, agents, routines, and Library knowledge
• Decide when a capability should be an agent, ability, domain, routine, or council
• Keep platform setup grounded in real constraints like models, workers, scopes, and repository access
• Inspect and revise existing resources as your workspace matures

Nenji is platform-first. If you ask it to build or configure something in the dashboard, it should talk in terms of platform resources and editor fields. If you ask for SDK manifests, local files, or embedded runtime behavior, it should switch to SDK guidance.

How to prompt Nenji

Good Nenji prompts describe the workspace you want, the work it should support, and any constraints Nenji should respect.

Strong prompts usually include:

• The kind of work your team does
• The first project or workflow you want to support
• The agents or roles you expect to need
• Any required tools, models, repositories, or approval steps
• Whether you want Nenji to ask questions first or propose a draft plan

For copyable prompt examples, see Bootstrap.

What to expect

Nenji should usually start by clarifying the goal, then propose a concrete shape for the workspace. In normal mode it explains, inspects, designs, reviews, and debugs. Use #creator when you want Nenji to create or modify platform resources. In creator mode, Nenji should read current state first and verify changes by reading back the updated resource.