Skip to content

chore: standardize metadata + brand-consistency rules across repo#12

Merged
a-essawy merged 1 commit into
mainfrom
claude/standardize-metadata
Apr 27, 2026
Merged

chore: standardize metadata + brand-consistency rules across repo#12
a-essawy merged 1 commit into
mainfrom
claude/standardize-metadata

Conversation

@a-essawy
Copy link
Copy Markdown
Contributor

Summary

Aligns this repo with the cross-rendobar brand-consistency standard rolled out in the apex monorepo (rendobar/rendobar PR #85) and the docs site (rendobar/docs PR #4). No source code changes — only README, issue template, and agent docs.

What changed

Trailing-slash fixes on apex page links

Apex Astro is configured with trailingSlash: "always". Every link from this repo to an https://rendobar.com/<path> page should end with / to match the canonical URLs the apex emits:

File Before After
README.md (header) rendobar.com/docs rendobar.com/docs/
README.md ("Full usage") rendobar.com/docs/cli rendobar.com/docs/cli/
README.md ("What is Rendobar" + Support) rendobar.com/docs rendobar.com/docs/
.github/ISSUE_TEMPLATE/config.yml rendobar.com/docs rendobar.com/docs/

Install/uninstall script URLs (rendobar.com/install.sh, install.ps1, uninstall.sh, uninstall.ps1) are FILES, not pages — they correctly stay slash-less.

CLAUDE.md + AGENTS.md — new "Cross-repo brand consistency" section

Both files now reference the apex .claude/rules/brand-consistency.md as the canonical source of truth, and embed the critical rules locally so an agent (Claude Code, Cursor, etc.) working in this repo doesn't need to context-switch. Embedded:

  • Canonical brand strings table (Rendobar, https://rendobar.com, https://api.rendobar.com, etc.)
  • Forbidden brand-string variants (Rendobar.com, the Rendobar platform, etc.)
  • package.json description rules — em-dash, sentence case
  • README + issue-template trailing-slash rule
  • No AI attribution in commits / PRs (Co-Authored-By: Claude, "Generated with [Claude Code]")
  • Anti-patterns list

CLAUDE.md and AGENTS.md were already kept in sync — both updated identically.

Why this PR exists

Without a written rule, the rendobar.com/docs (no trailing slash) drift will keep recurring every time someone updates a link. The new section in CLAUDE.md / AGENTS.md makes the convention explicit so any future agent edit conforms automatically.

Verification

  • package.json description already em-dash + sentence case (no change needed)
  • All apex page links in README + issue templates now have trailing slash
  • homepage field unchanged (https://rendobar.com — apex root, slash-less)
  • Install script URLs unchanged (files, not pages)
  • No code changes; no version bump

Related PRs

Trailing-slash fixes on apex page links (apex Astro is `trailingSlash:"always"`):
- README.md: 4 instances of `https://rendobar.com/docs` → `/docs/`
  (header link, "Full usage" link, two Support section links)
- README.md: `https://rendobar.com/docs/cli` → `https://rendobar.com/docs/cli/`
- .github/ISSUE_TEMPLATE/config.yml: docs URL gains trailing slash

Install/uninstall script URLs are unchanged — `rendobar.com/install.sh` etc.
are files, not pages; they correctly stay slash-less.

CLAUDE.md / AGENTS.md updates:
- New "Cross-repo brand consistency" section pointing to apex
  `.claude/rules/brand-consistency.md` as the canonical source of truth
- Embedded critical rules locally so an agent in this repo doesn't need to
  context-switch: canonical brand strings, package.json description format
  (em-dash, sentence case), README/issue-template trailing-slash rule, no
  AI attribution in commits/PRs
- Anti-patterns list

These rules mirror the apex monorepo's brand-consistency rule and the
docs repo's CLAUDE.md, so future agents working in any rendobar repo land
on the same conventions.

No code changes. No release-please bump (chore commit).
@a-essawy a-essawy merged commit 06f7f3f into main Apr 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant