Repository navigation
Add Danish business, consumer and accessibility compliance guidance #639
Description
Goal
Enable agents to flag Danish requirements when building or operating customer-facing sites, e-commerce, subscription products and Devantler's own business workflows.
Scope
Research official sources: Retsinformation, Forbrugerombudsmanden, Erhvervsstyrelsen, Skattestyrelsen, relevant accessibility authorities and cookie guidance. Include cookies/tracking, marketing consent, consumer rights and digital subscriptions, price/renewal/cancellation disclosures, invoicing/VAT and accessibility applicability. Distinguish B2B/B2C, own platform vs client project, and legal requirements vs best practice; include applicability decision tree and human review for uncertain matters.
Mandatory adoption-first workflow
- Inventory existing first-party skills and identify precise gaps; avoid duplication.
- Search reputable maintained third-party skills first. Evaluate quality, license/redistribution, security, compatibility, maintenance, provenance and scope.
- Prefer adopting a suitable upstream skill with an immutable version/commit pin and a reviewable automated update process; upstream changes must be summarized and tested before bumping the pin. Align with existing issues Bundled upstream skills: reviewable updates and clear redistribution terms #581, Updater PRs state what changed upstream for each moved skill #583 and Review and safely release the temporary git-commit upstream pin #598 rather than duplicating their implementation.
- Only author a new first-party skill when documented evaluation shows no adequate candidate. Before implementation, research authoritative standards, primary sources, realistic scenarios, failure modes, acceptance tests and maintenance ownership.
- Author first-party skills using the repository's skill-authoring skill and applicable Agent Skills specification/industry conventions; validate metadata, progressive disclosure, triggering, examples and automated evaluation. Never silently claim legal compliance.
Acceptance criteria
- Primary-source matrix with scope, jurisdiction and update dates.
- Existing third-party candidate assessment before first-party development.
- Scenario tests for brochure website, consumer webshop, B2B portal and subscription checkout.
- No blanket compliance certification.
Activity
docs: record skill coverage across the portfolio (#655)
feat(agentic-engineering): add the danish-business-rules skill files
devantler commentedon Nov 11, 2026
Research brief
Gap. Nothing tells an agent which Danish rules a checkout, a subscription, a newsletter, a cookie banner or an invoice brings with it, or whether those rules apply at all to the site in front of it.
Evidence. No incident is on record. The evidence is work that had to start from nothing each time:
Where it shows up. Client sites with offers and booking, the business site's portal and invoices, and any product that starts selling or sending marketing in Denmark.
Acceptance scenarios.
privacy-engineering. "Who may see an order?" ->application-security. "Fix the colour contrast" -> an accessibility review skill.The four sites the issue names (brochure site, consumer shop, business portal, subscription checkout) are worked through in the skill and are being tried by a fresh agent; results go on the pull request.
Already covered by.
accessibility-reviewandweb-design-guidelinescover how to test and build accessible pages, not whether the Danish act applies.stripe-best-practicescovers one payment provider.privacy-engineering(in review, #638) covers personal data. Nothing covers consumer, marketing, cookie, invoice or accessibility-applicability rules.Would something else fix it better? A lawyer's review of each site is the real control, and this guidance does not replace it. What it changes is that the questions are asked while the site is built, with the rule's section beside each, instead of at the audit.
Out of scope. Legal advice and any statement that a site is compliant. Personal data (#638). Sector rules, sales law and tax beyond what an invoice shows. Anything outside Denmark.
Decision record: build
danish-business-rulesCandidates. Searched 2026-11-11.
accessibility-review, already bundledWith no candidate there is nothing to score. The gap is rated high on the coverage page.
What the skill is written from (each read in the official text on 2026-11-10 or 2026-11-11): the cookie order (1148 of 2011), the Marketing Practices Act (consolidated act 1420 of 2024), the Consumer Contracts Act (consolidated act 1184 of 2025) and its amendment on the withdrawal function (act 723 of 2025, in force 19 June 2026), the Bookkeeping Act (700 of 2022), the tax authority's legal guide on invoice content (edition 2026-2), the Accessibility Act (801 of 2022), and the Consumer Ombudsman's page on unsolicited messages. The skill's source table gives the scope, who each applies to, and the date read.
What it deliberately does not cover, listed in the skill so nobody stretches it: the E-commerce Act (its text could not be read in the official database), detailed price-labelling rules, the VAT order's own text, the accessibility requirements themselves, sector rules, sales law, and other countries.
Known defects. None known. Results of the trial go on the pull request.
Description cost. 393 characters.
What would change this decision. A maintained upstream skill for Danish or EU consumer and marketing rules, with dated sources, would replace this one.
🤖 Generated with Claude Code
fix(agentic-engineering): correct the danish-business-rules skill aft…
fix(agentic-engineering): remove a stale invoice line and two oversta…
fix(agentic-engineering): address the review of the privacy and Danis…
feat(agentic-engineering): add the privacy-engineering and danish-bus…
devantler commentedon Nov 11, 2026
Done in #683, released as
agentic-engineering7.6.0. This note completes the decision record above.Acceptance criteria.
What changed during trial and review. Each point was read in the act before the text changed. What a customer owes after withdrawing from a started service is set by the act, not by the business. Phone selling to consumers needs a prior request. The order confirmation is a legal duty. The withdrawal period runs from the last item and has an outer limit. The withdrawal function has more steps than its first button. An amending act in force since 27 September 2026 adds pre-contract information that the consolidated text predates.
Description cost. 408 characters.
Known limits. It is engineering guidance, not legal advice, and it has not been reviewed by a lawyer. It covers only what was read. Its "not covered" list is long on purpose: the E-commerce Act (its text could not be read in the legal database), price labelling in detail, invoices to private customers, environmental claims, sales law, payment rules, sector rules and sales to other countries. The review fixes were not re-tried by the fresh agent. Whether agents load the skill in daily work is for #651 to measure.
🤖 Generated with Claude Code