cumulocity-dynamic-mapper: Command for Claude Code

Documentation Quality Assurance

Audit all project documentation for broken image references, stale cross-links, and content quality issues. Report every problem with a concrete fix.

Scope

Markdown files to audit (search recursively from repo root, skip node_modules, .git, target):

• docs/**/*.md
• *.md at repo root (README.md, CHANGES.md, FAQ.md, CLAUDE.md, AGENTS.md, CONTRIBUTING.md)
• dynamic-mapper-ui/public/docs/*.md — in-app documentation, fetched and rendered live by the deployed plugin

Image registries:

• Filesystem: resources/image/ — source-of-truth for image files
• Build config: dynamic-mapper-ui/cumulocity.config.ts buildTime.copy array — images bundled into the Angular app

Config requirement rule: Images referenced from these sources need to be in cumulocity.config.ts:

1. dynamic-mapper-ui/src/introduction/**/*.html — Angular in-app documentation components
2. dynamic-mapper-ui/README.md — the README bundled with the UI plugin
3. dynamic-mapper-ui/public/docs/*.md — see note below

Images referenced only in other docs (docs/**/*.md, root README.md/CHANGES.md/FAQ.md, etc.) are served from GitHub and do NOT need a config entry.

public/docs/*.md image syntax is deliberately GitHub-shaped, but still config-required. These files write image references as a repo-relative path — ![...](../../../resources/image/<name>.png) — identical in shape to a docs/**/*.md reference, so that the raw .md file also renders correctly when browsed directly on GitHub. DocMarkdownService.resolveImageHref() (dynamic-mapper-ui/src/introduction/doc-markdown.service.ts) rewrites that prefix to the bundled asset path (/apps/<contextPath>/image/<name>.png, resolved against document.baseURI) at render time in the deployed app — so despite the relative-looking source syntax, these images are still app-facing and do need the cumulocity.config.ts entry (rule 1a below). Don't misclassify them as 1b just because the path looks like a docs/**/*.md reference.