al-development-collection-for-claude-code — Claude Code plugin for AL
A Claude plugin that ships agents, skills and path-scoped rules for AL development in Microsoft Dynamics 365 Business Central.
/plugin marketplace add anthropics/claude-plugins-community
/plugin install al-development-collection-for-claude-code@claude-community
/plugin install aldc-al-development-plugin-for-business-central@claude-community
/plugin install aldc-spec-tdd-development-framework-for-al@claude-communityWhat al-development-collection-for-claude-code does
ALDC installs 12 agents, 9 role entry skills, 11 workflow skills and 16 knowledge skills into Claude, all under the aldc: prefix. It also adds 8 AL rules scoped by path and templates for requirement artifacts. Each agent comes with a contract, so the permissions are written down rather than assumed.
Start with /aldc:al-initialize. The scripts/init.js script copies the rules into .claude/rules/, seeds .claude/plans/memory.md and appends a managed block to the project's CLAUDE.md. You can preview with --project <dir>, apply with --apply, check drift with --verify and roll back with --rollback. Files you edited yourself stay collisions until a reviewed replacement runs with --force.
Node 20+ is required, and AL compilation needs the AL command-line tool. Publishing, test runs and debugging stay with a human or CI. The manifest declares al-symbols-mcp, context7 and microsoft-docs, yet a declared server that never loads is reported as unavailable. The Microsoft AL MCP is configured separately under the alias al; ALDC does not start it, and compilation and build operations go only to the Developer and Implementer roles.
What it helps with
- scaffold an AL project layout inside Claude
- give agents written role contracts instead of loose instructions
- spot rule files that drifted from the canonical version
- roll back a failed project initialization
- query AL symbols through an MCP server
Example prompts for the agent
- Initialize the project with
/aldc:al-initialize - Preview initialization for the
srcdirectory - Check rule drift with
--verify
How to install al-development-collection-for-claude-code
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install al-development-collection-for-claude-code@claude-community/plugin install aldc-al-development-plugin-for-business-central@claude-community/plugin install aldc-spec-tdd-development-framework-for-al@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about al-development-collection-for-claude-code
How do I install al-development-collection-for-claude-code in Claude Code?
From the marketplace: run /plugin marketplace add anthropics/claude-plugins-community, then /plugin install al-development-collection-for-claude-code@claude-community. Check the catalog afterwards with /plugin.
What does al-development-collection-for-claude-code do?
It adds agents, skills and rules for AL development in Microsoft Dynamics 365 Business Central to Claude. Initialization places the rules in .claude/rules/ and creates a plan memory file.
What does the plugin need to run?
Claude CLI and Node 20+. AL compilation requires the AL command-line tool. Publishing, test runs and debugging are done by hand or in CI.
Source text
claude-plugin · MIT
# ALDC — AL Development Collection for Claude Code <!-- Generated by scripts/sync-plugin-support.js. Do not edit. --> AI-Native development toolkit for Microsoft Dynamics 365 Business Central. Every file in this directory is generated from the canonical ALDC trees at the repository root; each one cites its canonical source and sha256. ## Installation From the plugin marketplace: ``` /plugin marketplace add javiarmesto/ALDC-AL-Development-Collection /plugin install aldc@aldc-marketplace ``` From a clone, register this directory as a local marketplace: ``` /plugin marketplace add ./claude-plugin /plugin install aldc@aldc-marketplace ``` Verify with `/plugin`, the actual Agent catalog and `/`. Claude 2.1.278 removed the `/agents` wizard. You should see 12 agents, 9 role entry skills, 11 workflow skills and 16 knowledge skills, all prefixed `aldc:`. Plugin loading, tool availability and any Business Central operation still need local verification; installation certifies none of them. ## First-time setup ``` /aldc:al-initialize ``` Initialization runs `scripts/init.js`: preview with `--project <dir>`, apply with `--apply`, inspect drift with `--verify`, restore with `--rollback`. Customized files stay collisions unless a reviewed replacement uses `--force`. Node 20+ is required. It copies the path-scoped AL rules to `.claude/rules/`, seeds `.claude/plans/memory.md` and adds a managed block to the project's `CLAUDE.md`. ## Layout ``` claude-plugin/ ├── .claude-plugin/plugin.json # manifest (MCP servers, userConfig) ├── .claude-plugin/marketplace.json # marketplace entry ├── agents/ # 12 agent contracts ├── skills/<role>/ # 9 short role entry skills ├── skills/<workflow>/ # 11 explicit workflow skills ├── skills/skill-*/ # 16 knowledge skills ├── rules/ # 8 path-scoped AL rules ├── docs/templates/ # requirement artifact templates ├── tools/ # Context Doctor, BCQuality, validator ├── hooks/ # SessionStart context, BCQuality precondition ├── aldc.yaml # toolkit root (plans.root: .claude/plans) ├── CLAUDE.md # plugin guidance └── README.md # this file ``` ## AL language tooling Read [Claude AL tooling](docs/claude-al-tooling.md) to reuse the existing AL LSP for Agents companion and verify access from each agent mode. ALDC declares no second LSP server and does not change user or project provider configuration. ## MCP servers **al-symbols-mcp** (read-only AL symbol queries), **context7** (library docs) and **microsoft-docs** (Microsoft Learn). A declaration in the manifest is not proof of connection: a server that is not loaded is `unavailable`, never simulated. The Microsoft AL MCP is optional and separately configured under user/project alias `al`; see [setup and role grants](docs/claude-al-tooling.md). ALDC grants its query operations explicitly and compilation/build/restore only to Developer and Implementer. It does not start that server or grant publish/authentication. Optional BC29 profiling/snapshot proxies are granted only to Triage after explicit connection setup; see the same guide for capture scope and runtime acceptance. ## Requirements Claude Code CLI, Node 20+, and — for AL compilation — the AL command-line tool. Publishing, running tests and debugging remain human- or CI-gated steps. ## License MIT · [javiarmesto](https://github.com/javiarmesto)
© javiarmesto · MIT · javiarmesto/ALDC-AL-Development-Collection
