LighghtEeloo

Edit repository material in a Sirno-managed project. Use for source, tests, docs, config, witness blocks, or skill packages that must start from the configured lake.

Rebuild Sirno skill templates, MCP resources, wrappers, and installed packages from the active project's lake.

Use when writing git commit messages for this project, choosing a commit prefix, or checking that a commit message follows the prefix: lowercase description convention.

Install Sirno and register its stdio MCP server in the current repository, idempotently and revertably. Use to set up Sirno from a fresh clone before any other Sirno skill or MCP tool, or to repair a missing binary or missing MCP registration.

Actualize lake entries into repository material when the governing design entry is known.

Finalize reviewed Sirno work: validate the lake, clear Tide, update Anchor, stage scoped files, and commit by default.

Internalize durable repository facts into the configured lake when material reveals design knowledge.

Assess and improve an existing Sirno Lake's entry framing, structure, review neighborhoods, and witness alignment. Propose first; edit only after approval.

Thin orchestrator bootstrap prompt. Read Multorum's shipped orchestrator methodology before acting.

Thin worker bootstrap prompt. Read Multorum's shipped worker methodology before acting.

Write, repair, or validate Sirno.toml. Use for creating or editing a Sirno project config, adding repository witness members, configuring structural fields, repairing missing generated comments, or explaining the exact Sirno.toml schema and validation workflow.

Edit a Sirno Lake. Use for creating, revising, or reorganizing compact Markdown entries, moving design knowledge from DESIGN.md or another mono form into the lake, choosing entry ids and structural metadata, expanding entries, or validating generated Sirno links.

Explore a Sirno-managed repository by using `sirno query`, exact structural predicates, `sirno witness`, and targeted code inspection. Use for understanding a codebase through its Sirno Lake, finding relevant entries before editing, tracing design concepts to repository evidence, mapping an implementation area, answering questions about where behavior lives, or preparing a change by following Sirno entries and witness blocks.

Conduct adaptive Sirno narrative sessions with users and materialize the resulting route as a Sirno Lake entry. Use for teaching, onboarding, reviewing, or exploring project knowledge through questions, feedback loops, reader-state tracking, narrative route design, or serialized narrative artifacts in `sirno-docs/`.

Rebuild the packaged Sirno agent skill wrappers and MCP skill resources from the lake. Use for regenerating or auditing `.agents/skills/sirno-*/SKILL.md`, editing a `meta`-categorized discipline entry, finding a skill resource or wrapper that has drifted from the Sirno Lake, or adding a new skill to the `agent-skills` roster.

Create, refine, or review Sirno repository witnesses. Use for inserting or splitting `sirno:witness:<entry-id>:begin` blocks, linking code/tests/config to Sirno Lake entries, deciding whether a witness needs a new or more specific Sirno Lake entry, interpreting `sirno witness` output, or checking whether a Sirno entry has precise repository evidence.

Use when writing or rewriting DESIGN.md for a software project from sparse product intent, especially when the document should name implementation concepts, define components, and stay concise.