Agent instructions — ele.dags.dk

Session entry points (auto-loaded as workspace rules every session): this file ( AGENTS.md )

Skill folders (each SKILL.md is loaded on demand): .cursor/skills/ (ele-* project skills, indexed in the table below),

This repository is an Express server with a plugin-driven architecture: core/plugins/*/plugin.js (bundled, loaded first) then plugins/*/plugin.js . Boot flow lives in core/server.js and core/src/ServerClass.js .

Always read first

- .cursor/skills/ele-aio/SKILL.md — mandatory before any task that plans from or changes this repository’s code: consult aio first (not optional); always use ele-aio for at least aio:prompt + aio:summary on substantive sessions (all session prompts/summaries must be saved — not optional, even when aio:search is not needed); state prompt id + summary saved in the attestation; end every response with **ele-aio attestation:** …; never aio:purge unless the user explicitly requests a full aio/.cache wipe. .cursor/rules/ele-aio-mandatory.mdc reinforces this. Same rule in README — AI assistants (ele-aio).

• .cursor/skills/ele-ai-agent-procedures/SKILL.md — mandatory for AI-assisted implementation (bounded scope, task envelopes, evidence): read with docs/implementation/ai-agent-procedures/README.md and contract agent_task_contract_v1 . .cursor/rules/ele-ai-agent-procedures-mandatory.mdc reinforces this. Complements ele-aio; does not replace it.
  

  

  - README.md — short runbook and links; ele-aio policy. Admin JSON inventory: docs/implementation/admin-http-surface.md (not duplicated in README).
• .cursor/rules/ele-mcp-http-cli-mandatory.mdc — query the live mcp-gateway from the agent terminal with npm run mcp:http when IDE-native MCP tools are not wired (requires a running server on ELE_MCP_HTTP_BASE ).
• For plugin authoring: docs/implementation/PLUGIN_DEVELOPER_MANUAL.md and docs/implementation/i18n.md (English JSON errors; translated user-facing UI).
• For api.* signatures and phase rules: docs/implementation/PLUGIN_API_REFERENCE.md (when the task is function-level behavior).
• For interface contracts: docs/README.md (entry index; per-id tables docs/reports/generated-contract-index.md , docs/reports/contract-usage-matrix.md ), docs/implementation/authoring/interface-lifecycle-governance.md (stability, owner, duplicate-avoidance), and the relevant docs/contracts/{datastores,services,kernel,policy-registration,behavior-http}/ *-interface-v1.md files (plus docs/contracts/content/ and docs/contracts/admin-types/ where applicable).
• For bundled core/plugins catalog and per-plugin docs: docs/core-plugins/README.md . Generated plugin reports live under docs/reports/plugins/ (see npm run generate:plugin-status / render:plugin-status in npm.md).

Plugin rules (summary)

• setup : api.prefs.declare, api.services.register, api.datastores.register, api.functions.register — not routes or api.admin.*.
• activate : routes, api.routes.disable, api.admin.registerContribution.
• start / stop : background work and cleanup (timers, pools, stores).
• Every plugin needs permissions.actions with at least one entry; validate in core/src/plugin-contract.js .