Load when preparing Event configuration with the separately installed ISLAMU Configurator CLI and Event-owned local definitions; routes to external command documentation, not bundled event-setup tools, terminal UI or backend API design.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use ISLAMU Configurator, installed
separately from Event. Its own
CLI guide
and generated schemas/islamu-configurator-command-v1.schema.json own executable
grammar and the machine result contract. Event does not maintain a second parser
or command registry. The bundled offline source roots, focused tests and release
targets are removed; install the external package and keep its notices.
Select a trusted local Event definition from
configurator/definitions/islamu-event/definition.json. Check its family,
revision and digest against the corresponding release.json. Definitions
are data; do not load arbitrary code or fetch a definition implicitly.
Choose the declared artifact ID: environment, configuration-manifest,
tenant-package, operator-identity or legal-drafts. Prepare a JSON answer
workspace matching that definition. Reference answers are test vectors,
not production credentials or a universal reverse importer.
Invoke islamu-configurator with --definition, --artifact, --input and,
for publication, --output. For example:
islamu-configurator artifact validate --definition configurator/definitions/islamu-event/definition.json --artifact configuration-manifest --input manifest-answers.json --machine
islamu-configurator env render --definition configurator/definitions/islamu-event/definition.json --artifact environment --input environment-answers.json --output deployment.env --machine
Branch on exitCode and the islamu-configurator-command/v1 envelope, not
rendered text. Success reports host-validation-required. --dry-run
never writes an artifact or authorizes restricted stdout.
Keep answer values and prepared artifacts on the protected native host. Never put secrets in process arguments, logs, environment variable names or public browser input. Output is create-only and restricted; unsupported protected-save hosts fail closed.
Submit prepared artifacts only through Event's existing authorized backend workflow. Event owns wire integrity, tenant scope, expected revisions, approval, legal publication and administrator authority.
Old event-setup command families are not aliases. Existing artifacts require
their answer-workspace proof when using --answers; the generic CLI cannot infer
lost/transformed answers. Import-semantic definitions require the explicit
artifact import revision options described in the external guide. Do not invent
an identity import wrapper or replace the target revision with a source revision.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Load for Blazor/MudBlazor UI changes involving forms, dialogs, focus, keyboard navigation, landmarks, ARIA, color contrast, RTL-safe styling, or WCAG 2.2 AA tests; not for backend-only changes.
The English summary is being prepared. Showing the original description.
Load when a task asks to research, verify, compare, or look up framework/package behavior, release notes, standards, RFCs, CVEs, or unfamiliar APIs; use repository evidence first, then official docs, and not for codebase navigation alone.
The English summary is being prepared. Showing the original description.
Load for Aspire AppHost work: start/stop/wait resources, inspect dashboard/logs/traces, add integrations/resources, rebuild a service, run isolated worktrees, or diagnose Aspire orchestration; not for plain dotnet apps, container-only deployments, or cloud deployment.
The English summary is being prepared. Showing the original description.
Load for authentication or authorization changes involving BFF cookies/tokens, JWT validation, claims/user ID extraction, policies, handler access checks, impersonation, or 401/403 bugs; not for UI affordance gating alone.
The English summary is being prepared. Showing the original description.
Load for Blazor BFF server work involving YARP proxy routes, cookie sessions, access-token forwarding/refresh, downstream API calls, BFF handlers, or browser-to-API auth failures; not for client component rendering or API JWT validation alone.
The English summary is being prepared. Showing the original description.
Load when editing Blazor `.razor.css`, scoped selectors, `::deep`, BEM class names, RTL/logical CSS properties, or styling nested MudBlazor components; not for global design tokens or non-Blazor CSS.
The English summary is being prepared. Showing the original description.