docs: structured marketplace description with USER LEVEL, PROJECT LEVEL, and BEST SUITED FOR#531
Conversation
…EL, and BEST SUITED FOR
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7d943c22b5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "displayName": "Compound Engineering", | ||
| "version": "2.63.1", | ||
| "description": "AI-powered development tools for code review, research, design, and workflow automation.", | ||
| "description": "USER LEVEL: You brainstorm, plan, review, and ship features with structured multi-persona feedback instead of a single pass. PROJECT LEVEL: Knowledge compounds—decisions, reviews, and patterns get captured so the team doesn’t re-discover the same lessons. Agent-native development kit—brainstorm and plan features, run multi-persona code reviews, polish frontend design, and automate Git, CI, PRs, deploys, and docs. BEST SUITED FOR: • Full-stack teams using Rails, Python, or TypeScript • Projects that want structured review before every merge • Teams practicing knowledge management alongside shipping", |
There was a problem hiding this comment.
This edit makes plugins/compound-engineering/.cursor-plugin/plugin.json diverge from the canonical description used by the release tooling (COMPOUND_ENGINEERING_DESCRIPTION in src/release/metadata.ts), so scripts/release/validate.ts now reports metadata drift and exits non-zero (I confirmed with bun run release:validate). In practice this blocks the required release-validation check and the description will be auto-rewritten on the next metadata sync, so the change is not durable unless the canonical metadata source is updated in tandem.
Useful? React with 👍 / 👎.
|
@TroonCataroon Thanks for the contribution. I'm questioning the value here because it makes the description much much longer and harder to parse especially with where descriptions show up across various surfaces. |
2 participants
Adds structured audience sections (USER LEVEL, PROJECT LEVEL, BEST SUITED FOR) to the marketplace description so prospective users immediately see who benefits and which project types fit.