Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.claude/rules/component-api.md:
- Around line 14-21: The fenced code block showing the component folder
structure is missing a language tag and triggers markdownlint MD040; update the
block in component-api.md (the block with the lines listing
src/components/button/ etc.) to include a language identifier (for example use
```text or ```bash) immediately after the opening backticks so the fence is
labeled and MD040 is resolved.
In @.claude/rules/docs.md:
- Around line 16-20: The fenced code block showing the folder structure (the
block containing "src/components/button/" and its files) is unlabeled which
triggers markdownlint MD040; fix it by adding a language label after the opening
backticks (e.g., use "text" or "bash") so the block becomes a labeled fenced
code block and the lint rule is satisfied.
In @.claude/rules/styling.md:
- Around line 16-25: The markdown fenced code blocks shown (the block containing
the snippets for resolveStyles, cn, and BaseComponent) are missing language
tags; update those fenced blocks by adding an explicit language label (e.g.,
```text or ```markdown) so they pass MD040 linting—specifically edit the block
that documents resolveStyles, cn, and <BaseComponent .../> and the similar block
around lines 193–199 to prepend the appropriate language identifier.
In @.claude/rules/testing.md:
- Around line 66-70: The fenced code block showing the file tree
("src/components/button/" with "button.tsx" and "button.test.tsx") is missing a
language tag which triggers MD040; update the opening fence from ``` to include
a language (e.g., ```text or ```bash) so the block is language-qualified; ensure
the same fence content (the file tree) remains unchanged and commit the markdown
edit.
In `@CLAUDE.md`:
- Around line 88-90: Update the fenced code block containing "<type>(<scope>):
<subject>" to specify a language for markdownlint (MD040); change the opening
fence from ``` to ```text so the block reads as a text code block and resolves
the linter warning.
In `@packages/core/CLAUDE.md`:
- Around line 27-34: Several fenced code blocks in the CLAUDE.md file are
missing language identifiers (e.g., the block that starts with
"src/components/button/"); update each unlabeled fenced block by adding an
appropriate language tag (for example use ```text or ```bash for file
trees/terminal snippets, or ```tsx/```tsx for React code) so that the blocks
that contain the "src/components/button/" listing and the other unlabeled blocks
are annotated with the correct language identifier.
- Around line 15-19: Update the malformed rule file paths in CLAUDE.md by
replacing the incorrect `@.claude/...` prefixes with the repo-conventional
`.claude/...` versions (e.g. change `@.claude/rules/component-api.md`,
`@.claude/rules/styling.md`, `@.claude/rules/typescript.md`,
`@.claude/rules/testing.md`, `@.claude/rules/docs.md` to
`.claude/rules/component-api.md`, `.claude/rules/styling.md`,
`.claude/rules/typescript.md`, `.claude/rules/testing.md`,
`.claude/rules/docs.md`) so the links match the actual `.claude/rules/`
directory at the repo root.