ALDC-AL-Development-Collection
CLAUDE.md115 starsChanged 10 days agoMITView on GitHub
@import ./docs/framework/ALDC-Core-Spec-v1.2.md AL (Application Language) workspace for Microsoft Dynamics 365 Business Central. Architecture: ALDC Core v1.2 — 13 agents (5 core + 3 on-demand + 4 subagents + 1 extension) + 16 skills + 11 workflows + 9 instructions. 11 workflows (6 core + 5 BC Agents pack). The 6 core, invoked via /workflow-name: 16 composable knowledge modules (8 required + 4 recommended + 3 BC Agents + 1 utility) loaded on-demand by agents (not invoked directly): Agents MUST declare…
In this repository55 other files it gives its agents.
- claude-plugin/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- instructions/copilot-instructions.mdCopilot instructions
- agent-builderSkill
- al-agent-build-instructionsSkill
- al-agent-createSkill
- al-agent-instructionsSkill
- al-agent-taskSkill
- al-agent-testSkill
- al-buildSkill
- al-context-createSkill
- al-initializeSkill
- al-memory-createSkill
- al-pr-prepareSkill
- al-spec-createSkill
- architectSkill
- auditSkill
- conductSkill
- developSkill
- presalesSkill
- reviewSkill
- skill-agent-instructionsSkill
- skill-agent-task-patternsSkill
- skill-agent-toolkitSkill
- skill-al-review-pipelineSkill
- skill-apiSkill
- skill-contribution-assistantSkill
- skill-copilotSkill
- skill-debugSkill
- skill-estimationSkill
- skill-eventsSkill
- skill-migrateSkill
- skill-pagesSkill
- skill-performanceSkill
- skill-permissionsSkill
- skill-testingSkill
- skill-translateSkill
- specSkill
- triageSkill
- skill-agent-instructionsSkill
- skill-agent-task-patternsSkill
- skill-agent-toolkitSkill
- skill-al-review-pipelineSkill
- skill-apiSkill
- skill-contribution-assistantSkill
- skill-copilotSkill
- skill-debugSkill
- skill-estimationSkill
- skill-eventsSkill
- skill-migrateSkill
- skill-pagesSkill
- skill-performanceSkill
- skill-permissionsSkill
- skill-testingSkill
- skill-translateSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 142
No npm/yarn build steps. AL compilation is handled by the AL Language VS Code extension.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ALDC — Claude Code Instructions
@import ./docs/framework/ALDC-Core-Spec-v1.2.md
Overview
AL (Application Language) workspace for Microsoft Dynamics 365 Business Central. Architecture: ALDC Core v1.2 — 13 agents (5 core + 3 on-demand + 4 subagents + 1 extension) + 16 skills + 11 workflows + 9 instructions.
Core Principles
- Extension-only development — Never modify base application objects. Use tableextensions, pageextensions, event subscribers.
- Human-in-the-Loop (HITL) — All critical decisions require user confirmation before proceeding.
- TDD / spec-driven — Features follow:
architecture (MEDIUM/HIGH)->al-spec-agentviaal-spec.create-> human approval -> test-plan -> implementation -> review. - Least privilege — Generate only the minimum permissions required. Use XLIFF for all user-facing strings.
Agent Routing
| Intent | Agent | What it does |
| Specification from approved design | delegate to agent al-spec-agent | Technical contracts and human approval before implementation |
| Design, architecture, strategy | delegate to agent al-architect | Solution design, data modeling, integration strategy |
| Implement, code, debug, fix | delegate to agent al-developer | Tactical implementation with full AL MCP tools |
| TDD orchestration (plan -> implement -> review -> commit) | delegate to agent al-conductor | Orchestrates planning, implementation, and review subagents |
| Estimate, size, propose | delegate to agent al-presales | PERT estimation, SWOT analysis, cost breakdown |
Quick Routing
New feature (MEDIUM/HIGH)? -> al-architect -> /al-spec.create -> al-conductor
New feature (LOW)? -> /al-spec.create -> al-developer
Bug fix / debugging? -> al-developer
Architecture review? -> al-architect
Full TDD cycle? -> al-conductor
Project estimation? -> al-presalesWorkflows
11 workflows (6 core + 5 BC Agents pack). The 6 core, invoked via /workflow-name:
| Workflow | When to use |
/al-spec.create | Create functional-technical specifications before development |
/al-build | Build, package, and deploy extensions |
/al-pr-prepare | Prepare pull requests with documentation and validation |
/al-memory.create | Generate/update memory.md for session continuity |
/al-context.create | Generate project context.md for AI assistants |
/al-initialize | Complete environment and workspace setup |
Skills
16 composable knowledge modules (8 required + 4 recommended + 3 BC Agents + 1 utility) loaded on-demand by agents (not invoked directly):
| Skill | Domain | Loaded by |
/skill-debug | Debugging, snapshot debugging | al-developer |
/skill-api | API pages, OData, REST | al-developer, al-architect |
/skill-copilot | AI features, PromptDialog | al-developer, al-architect |
/skill-events | Event subscribers, publishers | al-developer, al-architect |
/skill-permissions | Permission sets, XLIFF, security | al-developer |
/skill-pages | Page types, FastTabs, actions | al-developer |
/skill-migrate | BC version migration, upgrade codeunits | al-developer |
/skill-translate | XLF translation, NAB AL Tools | al-developer |
/skill-performance | CPU profiling, FlowField optimization | al-developer, al-architect |
/skill-testing | TDD, test strategy, AL Test Toolkit | al-architect, al-conductor |
/skill-estimation | PERT estimation, complexity scoring | al-presales |
Skills Evidencing
Agents MUST declare which skills they loaded and which patterns they applied:
- al-architect ->
> **Skills applied**: skill-api, skill-eventsat top of architecture.md - al-developer ->
> **Skills loaded**: skill-debug (root cause analysis)at start of response - al-conductor ->
Skills Applied in This Phasetable in phase-complete.md
Auto-Applied Instructions
Active automatically based on file type (no invocation needed):
Always on *.al: al-guidelines, al-code-style, al-naming-conventions, al-performance
Context-activated: al-error-handling (errors), al-events (events), al-testing (test files)
See instructions/ directory for full content.
Plans
Requirement sets live in .github/plans/, one subdirectory per requirement:
.github/plans/
memory.md # Global memory (cross-session decisions)
{req_name}/
{req_name}.spec.md # Functional-technical specification
{req_name}.architecture.md # Architecture decisions
{req_name}.test-plan.md # Test plan with acceptance criteria
{req_name}-phase-<N>-complete.md # Phase completion reports
{req_name}-complete.md # Final completion reportWorkflow with Plans
MEDIUM / HIGH complexity:
al-architectdesigns solution, creates{req_name}.architecture.md/al-spec.createreads architecture, generates{req_name}.spec.mdal-conductorreads spec + architecture, orchestrates TDD/al-pr-prepareprepares PR referencing the plan
LOW complexity:
/al-spec.creategenerates spec directly from codebaseal-developerimplements using spec as blueprint
Complexity-Based Routing
| Level | Scope | Route |
| LOW | Single phase, no integrations | /al-spec.create -> al-developer |
| MEDIUM | 2-3 areas, internal integrations | al-architect -> /al-spec.create -> al-conductor |
| HIGH | 4+ phases, external integrations | al-architect -> /al-spec.create -> al-conductor |
Present the assessment and wait for user confirmation before proceeding.
BC Agents Pack (Extension)
For agent development with AI Development Toolkit. Includes al-agent-builder agent and skill-agent-task-patterns (8 SDK integration patterns). Workflows: /al-agent.create, /al-agent.task, /al-agent.instructions, /al-agent.test.
Build & Test
# Download symbols (requires app.json configured)
al-language: Download Symbols
# Build the extension
al-language: Package
# Publish to sandbox
al-language: Publish without Debugging
# Run tests
al-language: Run TestsNo npm/yarn build steps. AL compilation is handled by the AL Language VS Code extension.
Project Structure
instructions/ # Auto-applied instruction files (9)
agents/ # Agent definitions (5 core + 3 on-demand + 3 subagents + 1 extension)
skills/ # Composable knowledge modules (16 skill directories)
prompts/ # Workflow definitions (11 prompt files)
docs/framework/ # Normative spec (ALDC-Core-Spec-v1.2.md)
docs/templates/ # Immutable templates
.github/plans/ # Requirement sets & memory
src/ # AL source code
app.json # Extension manifestReference
- ALDC Core Spec v1.2 — Normative specification
- AL Language Reference
- BC Development Docs
Framework: ALDC Core v1.2 | Primitives: 13 agents + 16 skills + 11 workflows + 9 instructions
For direct Developer increments, use AL Developer Reviewer in an independent context before human approval. Dredd remains the advisory auditor. Both load skill-al-review-pipeline; Conductor phases keep their own review subagent.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

