Skip to content

docs: outsider-facing clarity pass on README + skills.json#9

Merged
next-devin merged 1 commit into
mainfrom
docs/readme-outsider-clarity
May 28, 2026
Merged

docs: outsider-facing clarity pass on README + skills.json#9
next-devin merged 1 commit into
mainfrom
docs/readme-outsider-clarity

Conversation

@next-devin

Copy link
Copy Markdown
Contributor

Summary

Quick clarity pass on the public-facing surfaces of this repo. Three small changes:

  1. Drop the internal bleed in the "Campaigns OS Skill Boundary" section. The previous text named the private next-campaigns-ops repo and "internal Sellmore orchestration" — neither of which an outside developer reading this README has any context for. The new version explains why the lifecycle skills live with the campaigns-os package (they're version-locked to the package's CLI and contract versions), which makes the split make sense instead of feeling arbitrary.
  2. Replace "CPK" with "Next Commerce campaign repo" in the New Campaign Setup table row and the boundary text. CPK is internal shorthand; outsiders had no way to know what it meant.
  3. Fix a stale install string: pip install 29next-theme-kitpip install next-theme-kit. The PyPI package is next-theme-kit. The bad string appeared in both skills.json (next-theme-dev prerequisites) and next-theme-dev/SKILL.md (preamble environment check).

Why

Came out of a session reviewing how the README reads to a client landing cold. The same pattern (internal/self-references bleeding into public-facing material) showed up in campaigns-os/README.md too — there's a companion PR there: NextCommerceCo/campaigns-os#50.

Test plan

  • Render README on GitHub and confirm the boundary section reads cleanly for someone with no Sellmore/NEXT context
  • cat skills.json | jq '.skills[] | select(.id=="next-theme-dev").prerequisites' shows next-theme-kit
  • No remaining occurrences of 29next-theme-kit in repo: grep -r "29next-theme-kit" . returns nothing

- Boundary section: drop the "Internal Sellmore orchestration" /
  next-campaigns-ops reference (private-repo bleed in a public README) and
  reframe the split as a *why* (version-lock to campaigns-os CLI/contracts)
  instead of an arbitrary boundary.
- Replace "CPK" jargon with "Next Commerce campaign repo" in the New
  Campaign Setup row and boundary text — readers landing cold had no way
  to know what CPK meant.
- Fix stale install string: pip install 29next-theme-kit → next-theme-kit,
  in both skills.json (prerequisites) and next-theme-dev/SKILL.md (preamble
  environment check). The PyPI package is next-theme-kit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@next-devin next-devin marked this pull request as ready for review May 28, 2026 04:15
@kilo-code-bot

kilo-code-bot Bot commented May 28, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 1 Observation Found | Recommendation: Merge (with optional cleanup)

Changes Reviewed

File Change Assessment
README.md Replace "CPK" with "Next Commerce campaign repo"; rewrite "Campaigns OS Skill Boundary" section Correct — removes internal references
next-theme-dev/SKILL.md:42 Fix pip install 29next-theme-kitpip install next-theme-kit Correct — PyPI package is next-theme-kit
skills.json:27 Fix pip install 29next-theme-kitpip install next-theme-kit Correct — matches PyPI package name

Issue Details

Severity File Line Issue
SUGGESTION skills.json 105 next-campaigns-setup description still says "CPK campaign" — internal shorthand not yet replaced
SUGGESTION skills.json 138-140 Prerequisites still reference "CPK project root" and "CPK_ROOT environment variable"
Files Reviewed (3 files)
  • README.md
  • next-theme-dev/SKILL.md
  • skills.json

Reviewed by minimax-m2.7 · 161,471 tokens

@next-devin next-devin merged commit 863c9ec into main May 28, 2026
1 check passed
@next-devin next-devin deleted the docs/readme-outsider-clarity branch May 28, 2026 04:41
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