Jakob WennbergandClaude Sonnet 5
ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Modifier atoms
Cross-cutting attributes that aren't an industry on their own but change how the agent interprets the company. The composer can pick several modifiers per company.
.claude/skills/modifier/
├── README.md ← this file
├── single-shareholder-ab-fmb/
│ └── SKILL.md
├── enskild-firma/
│ └── SKILL.md
└── small-employer/
└── SKILL.md
When to author a modifier vs. a vertical
- Vertical = what the company does (restaurang, e-handel, konsult-IT).
- Modifier = a structural attribute (form, ownership, employer status, multi-currency, blandad verksamhet, …).
A company will typically have 0-1 vertical and 0-3 modifiers.
Authoring contract
Same SKILL.md + YAML frontmatter as industry/ atoms, but tier: modifier
and no sni_prefixes:
---
id: modifier/<slug>
tier: modifier
title: "Display name"
description: >
One paragraph the composer reads when deciding whether to load this.
Cover the qualifying conditions (e.g. "AB med en aktieägare") and the
most distinctive accounting implications.
trigger_signals:
ownership: "single_shareholder"
bas_account_patterns: ["2898", "2899"]
estimated_tokens: 6000
version: 1
---
Suggested body sections
- When this applies: the precise conditions the agent should look for.
- Implications: what changes in day-to-day bookkeeping.
- Regulatory edge cases: laws that fire because of this modifier.
- BAS account patterns: accounts that show up because of it.
- References: links to horizontals and into
references/*.mdfiles.
Adding / removing
Same workflow as industry/: write the SKILL.md, run
npx tsx scripts/seed-agent-atom-registry.ts. Set is_active: false to
deprecate.