Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
al-guidelines - Skill - OpenSmartRoute
Skillv1.0.0
al-guidelines
AL Core principles — transversal rules for Microsoft Dynamics 365 Business Central development
Instruction file imported from javiarmesto/APM-ALDC (.github/instructions/al-guidelines.instructions.md). Copyright stays with the author.
AL Core Principles
Transversal framework principles. Concrete rules for style, naming, performance, errors, events and testing live in their own micro-instructions.
Event-driven model. Never modify Business Central base objects; extend via event subscribers or table/page extensions.
App focus by default. Main implementation in App/; tests are only generated if the user explicitly requests them.
AL-Go App/Test separation. The Test/ project depends on App/; never the other way around. Do not mix application logic with tests.
Naming is infrastructure. The pattern <ObjectName>.<ObjectType>.al is not aesthetic: the narrow globs in other instructions depend on it. A misnamed file silently misses its rules.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/javiarmesto-apm-aldc-al-guidelines-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "javiarmesto-apm-aldc-al-guidelines-instructions",
"kind": "skill",
"name": "al-guidelines",
"description": "AL Core principles — transversal rules for Microsoft Dynamics 365 Business Central development",
"publisher": "javiarmesto",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"AL Core principles — transversal rules for Microsoft Dynamics 365 Business Central development"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/javiarmesto/APM-ALDC",
"path": ".github/instructions/al-guidelines.instructions.md",
"ref": "2996697faec4ac70abf01648714ebd18f5128e28",
"url": "https://github.com/javiarmesto/APM-ALDC/blob/2996697faec4ac70abf01648714ebd18f5128e28/.github/instructions/al-guidelines.instructions.md",
"key": "javiarmesto/APM-ALDC/.github/instructions/al-guidelines.instructions.md"
},
"applies_to": "**/*.al"
},
"instructions": "# AL Core Principles\n\nTransversal framework principles. Concrete rules for style, naming, performance, errors, events and testing live in their own micro-instructions.\n\n1. **Event-driven model**. Never modify Business Central base objects; extend via event subscribers or table/page extensions.\n2. **App focus by default**. Main implementation in `App/`; tests **are only generated if the user explicitly requests them**.\n3. **AL-Go App/Test separation**. The `Test/` project depends on `App/`; never the other way around. Do not mix application logic with tests.\n4. **Naming is infrastructure**. The",
"cost": {
"context_tokens": 188
}
}
Fetch it by URL: GET /api/v1/registry/javiarmesto-apm-aldc-al-guidelines-instructions/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
