6c3e5ace35
Observed live: a consultant hit "no" reflexively on a setup confirmation while moving fast through onboarding, and only noticed afterward. Most of this document's ja/nej gates aren't real choices -- the standard is company policy, not a per-developer preference -- and a blocking question with only one sane answer just invites that kind of misclick. v24 -> v25. Converted to act-and-report (no question) wherever the file is git-tracked and the replacement is already verified correct: the v6-era repo-mirror cleanup, CLAUDE.md's obsolete-forms replacement, and the v24 migration's repo-local agent-file / find-altool.ps1 removal -- all fully recoverable via git revert if anyone ever wants the old version back. Converted the two genuine multi-developer-coordination steps (.mcp.json, .claude/settings.json -- whether every developer has migrated their own machine is a fact only a human knows) from a blocking question to a safe default (leave in place, report, offer removal later once a developer explicitly confirms). Left three gates as real questions, on purpose: uncommitted local changes on CLAUDE.md (actual risk of lost work), the developer's personal ~/.claude/CLAUDE.md (not git-tracked, carries personal customization), and the two "should I commit this?" prompts (commit timing is a legitimate choice, not a policy with one right answer). |
||
|---|---|---|
| .. | ||
| agents | ||
| architecture | ||
| knowledge | ||
| scripts | ||
| setup | ||
| skills | ||
| README.md | ||
Custom layer
This folder is the template for partner- and customer-specific overrides. Use it to add knowledge and skills that apply to your organization but are not appropriate for the shared Microsoft or Community layers.
Structure
custom/
├── knowledge/ # Your organization's knowledge files (same format as /microsoft/knowledge/)
└── skills/ # Your organization's action skills
How to use
Fork or clone BCQuality into your own repository and add your content here. Knowledge files in /custom/knowledge/ follow the same frontmatter schema and section requirements as every other layer. Action skills in /custom/skills/ follow the Action Skill template defined in /skills/.
When agents consume BCQuality, the custom layer is loaded alongside Microsoft and Community — your overrides apply automatically.
CURABIS — BCQuality customizations
Developer onboarding (new machine)
Two files must be placed on the developer's machine. Everything else is automatic.
1. Global Claude Code instructions
Copy setup/machine/CLAUDE.md to ~/.claude/CLAUDE.md
and fill in your name and username.
This file tells Claude Code about CURABIS Standard in every session — including brand-new, unconfigured repositories.
2. BC MCP credentials
Create ~/.bc-mcp.config.json with your BC service-to-service credentials:
{
"tenantId": "<your-tenant-id>",
"clientId": "<your-client-id>",
"clientSecret": "<your-client-secret>",
"baseUrl": "https://api.businesscentral.dynamics.com"
}
Never commit this file. It contains secrets.
Configuring a new project
Once the two machine files are in place, open any AL-Go repository in VS Code and tell Claude Code:
"Konfigurer dette projekt til CURABIS Standard"
Claude fetches setup/curabis-standard.agent.md
and writes all project files automatically:
CLAUDE.md, .mcp.json, .github/.agents/, cspell.json, projectmemory/.
The BC MCP bridge (bc-mcp-bridge.js) is also installed to ~/.claude/
from this repo — so it stays up to date every time setup is re-run.
Folder structure
custom/
README.md ← this file
knowledge/
architecture/ ← AL architecture rules
testing/ ← test quality rules
mcp/ ← BC MCP / API page rules
setup/
curabis-standard.agent.md ← project setup agent
bc-mcp-bridge.js ← BC MCP bridge (authoritative copy)
machine/
CLAUDE.md ← global Claude Code instructions template
templates/
bcquality.agent.md ← BCQuality review agent (per project)
immanuel.agent.md ← Rule guardian agent (per project)
cspell.json ← Standard spell-check config