Add Renowide Agent Marketplace cursorrules#262
Open
Renowide wants to merge 2 commits intoPatrickJS:mainfrom
Open
Add Renowide Agent Marketplace cursorrules#262Renowide wants to merge 2 commits intoPatrickJS:mainfrom
Renowide wants to merge 2 commits intoPatrickJS:mainfrom
Conversation
Build and deploy a paying AI agent to the Renowide marketplace in one flow using the @renowide/mcp-server MCP tools. Renowide is the distribution counterpart to AI coding assistants — Cursor builds the agent, Renowide gives it paying customers. No SEO, no ads, no landing-page marketing. 85% revenue to creator, 15% platform. The rule teaches Cursor the canonical deploy flow (whoami → templates → scaffold → validate → deploy), the Path A / Path B / Path C decision tree, the flat renowide.json manifest shape, pricing menu, HMAC-SHA256 webhook security, and common mistakes to avoid. Paired with: - @renowide/cli https://npmjs.com/package/@renowide/cli - @renowide/mcp-server https://npmjs.com/package/@renowide/mcp-server - create-renowide-agent https://npmjs.com/package/create-renowide-agent Docs: https://renowide.com/build Source: https://github.com/Renowide/renowide-cli Made-with: Cursor
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (3)
📝 WalkthroughWalkthroughAdds documentation and a Cursor rule that define an end-to-end Renowide Agent Marketplace build, validate, deploy, and sandbox-test workflow using Changes
Sequence Diagram(s)sequenceDiagram
participant Developer as Developer
participant CursorRule as Cursor Rule
participant MCP as MCP Server (`@renowide/mcp-server`)
participant Templates as Templates/Registry
participant Renowide as Renowide Platform
participant Sandbox as Sandbox/Test Hire
Developer->>CursorRule: invoke rule (match renowide.json / canvas)
CursorRule->>MCP: renowide_whoami (auth + retry)
MCP->>Templates: renowide_list_templates (filter/select)
MCP->>Developer: renowide_scaffold_agent (scaffold files)
Developer->>MCP: modify only allowed files (e.g., server/actions.ts)
MCP->>MCP: renowide_validate_manifest / renowide_validate_canvas
MCP->>Renowide: renowide_deploy (returns handoff_secret)
MCP->>Developer: display handoff_secret (store as RENOWIDE_WEBHOOK_SECRET)
MCP->>Sandbox: renowide_test_sandbox (simulate hire)
Sandbox-->>Developer: test results / diagnostics
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (2)
rules/renowide-agent-marketplace-cursorrules-prompt-file/renowide.mdc (1)
107-108: Avoid hard-coded roadmap dates in rule text.
Q3 2026 roadmapcan become stale quickly and reduce trust in the rule. Prefer a timeless phrasing (or point to a source of truth) to keep guidance accurate over time.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@rules/renowide-agent-marketplace-cursorrules-prompt-file/renowide.mdc` around lines 107 - 108, Replace the hard-coded date in the rule text that reads "Success / outcome-gated fees are not yet supported (Q3 2026 roadmap)." with a timeless phrasing or a pointer to a maintained source (e.g., "not yet supported; see [status page/link]" or "not yet supported as of this guidance") so it can't become stale; update the string in renowide.mdc where the sentence appears and, if appropriate, add a link or note referencing the authoritative roadmap/status resource instead of an explicit quarter/year.README.md (1)
277-277: Keep this README list description concise for consistency.This entry’s description is much longer than neighboring items in the same category. Consider shortening it to a single concise sentence to match list formatting style.
As per coding guidelines, "Use consistent formatting for list items in the README.md file" and "Use clear and concise language in all documentation and .cursorrules files."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` at line 277, Shorten the lengthy list item for "Renowide Agent Marketplace" (the link to renowide.mdc) to a single concise sentence that matches neighboring entries; e.g., state the core offering only — "Build and deploy a paying AI agent to the Renowide marketplace using `@renowide/mcp-server` tools." — remove extra implementation details (Canvas Kit v2, Persona, revenue share, marketing notes) so the README list is consistent and brief.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@README.md`:
- Line 277: Shorten the lengthy list item for "Renowide Agent Marketplace" (the
link to renowide.mdc) to a single concise sentence that matches neighboring
entries; e.g., state the core offering only — "Build and deploy a paying AI
agent to the Renowide marketplace using `@renowide/mcp-server` tools." — remove
extra implementation details (Canvas Kit v2, Persona, revenue share, marketing
notes) so the README list is consistent and brief.
In `@rules/renowide-agent-marketplace-cursorrules-prompt-file/renowide.mdc`:
- Around line 107-108: Replace the hard-coded date in the rule text that reads
"Success / outcome-gated fees are not yet supported (Q3 2026 roadmap)." with a
timeless phrasing or a pointer to a maintained source (e.g., "not yet supported;
see [status page/link]" or "not yet supported as of this guidance") so it can't
become stale; update the string in renowide.mdc where the sentence appears and,
if appropriate, add a link or note referencing the authoritative roadmap/status
resource instead of an explicit quarter/year.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c2e01fe5-7955-46d7-8f61-67f41a01b85e
📒 Files selected for processing (3)
README.mdrules/renowide-agent-marketplace-cursorrules-prompt-file/README.mdrules/renowide-agent-marketplace-cursorrules-prompt-file/renowide.mdc
…mission per hire" Replaces the "85% revenue share" framing with the sharper marketplace phrasing used on the Renowide homepage, the @renowide/cli README, the @renowide/mcp-server package, and the public renowide.com/build docs. Pricing mechanics are unchanged (developer nets the same amount per hire); only the external phrasing is sharpened. Files: - rules/renowide-agent-marketplace-cursorrules-prompt-file/renowide.mdc - rules/renowide-agent-marketplace-cursorrules-prompt-file/README.md - README.md (one-line entry under Other)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
A Cursor rule that teaches the assistant how to build and deploy a paying AI agent to the Renowide marketplace in one flow, via the
@renowide/mcp-serverMCP tools.Renowide is the distribution counterpart to AI coding assistants: Cursor builds the agent, Renowide gives it paying customers — no SEO, no ads, no landing-page marketing. 85% revenue to creator, 15% platform. Billing, VAT, GDPR, HMAC-signed webhook delivery all handled.
What the rule covers
renowide_whoami→renowide_list_templates→renowide_scaffold_agent→renowide_validate_manifest→renowide_validate_canvas→renowide_deploy→renowide_test_sandbox.renowide.jsonmanifest shape and pricing menu (5 models).Category
Added under Other (agent-marketplace deployment doesn't fit the existing frontend/backend/mobile/etc. buckets).
Placement
Inserted alphabetically between Next.js (Type LLM) and Unity (C#).
Files
rules/renowide-agent-marketplace-cursorrules-prompt-file/renowide.mdc— the rule itself (Cursor .mdc format with description + globs frontmatter)rules/renowide-agent-marketplace-cursorrules-prompt-file/README.md— installation + prerequisitesREADME.md— one-line entry in the Other sectionRelated packages
@renowide/cli— the CLI (renowide login,renowide deploy, etc.)@renowide/mcp-server— MCP server this rule teaches Cursor to drivecreate-renowide-agent— one-liner scaffolder:npm create renowide-agent@latest my-agentChecklist
renowide.json,renowide.yaml,canvas/*.json,canvas/*.tsx)<topic>-cursorrules-prompt-fileconventionSummary by CodeRabbit