`Cursor` Official Plugin Spec and Marketplace Repo

Plugins now have a concrete manifest, skills, rules, and MCP layout. The useful part is not the list itself, but the repeatable packaging pattern for agent workflows.

[ KEY POINTS ]

Each plugin is a standalone root directory with .cursor-plugin/plugin.json, making distribution and validation manifest-driven.
The catalog covers memory updates, PR review canvases, docs canvases, SDK integrations, and parallel agent orchestration.
create-plugin scaffolds and validates new plugins, lowering the setup cost for reusable internal workflows.
orchestrate points to a planner-worker-verifier pattern for large tasks, useful when one agent session gets too wide.

Originalgithub.com/cursor/pluginsRead original →

// related

#0001
#0001Agents & tools Awesome MCP Servers4 hours ago
`bulkrender-mcp` added for template-based `DOCX`/`PDF` generation
50radar
bulkrender-mcpMCP server — template-based DOCX/PDF generation
Template-driven document output is now exposed as an MCP server. Useful for automating invoices, reports, and client docs without wiring a custom export stack.
- bulkrender-mcp targets DOCX/PDF generation from templates, so agents can produce formatted documents through MCP workflows.
- The signal is narrow but practical: document generation can move from app code into an agent-callable tool layer.
- Best fit is repetitive business output such as proposals, invoices, reports, and onboarding packets.
Source: github.com/punkpeye/awesome-mcp-servers/commit/77d2a851bRead original →
FIG-0011:1
50radar
FIG-0011:1
#0002
#0002Agents & tools r/ClaudeAI6 hours ago
Learning App Building with `Claude Code`: Start from Architecture, Not Code
50radar
Claude CodeTerminal coding agent — edits and generates code from prompts
Running code is not the finish line. Auth, APIs, hosting, version control, tests, analytics, and security decide whether a prototype can handle real users.
- The proposed stack map is simple: frontend, backend, database, and plumbing. The biggest skill gap sits in the plumbing layer, not screen generation.
- Claude Code can scaffold UI, backend, and database quickly, but it will not automatically make security, deployment, observability, or data boundaries solid.
- Good prompting should ask for architecture first: auth flow, API contracts, persistence model, testing path, and hosting assumptions before implementation.
- Best use case is turning app ideas into maintainable prototypes. Pure vibe coding burns tokens and hides production risks.
Source: www.reddit.com/r/ClaudeAI/comments/1tonzj9/im_a_softwareRead original →
50radar
PHOTO
FIG-0021:1
#0003
#0003Agents & tools GitHub Changelog8 hours ago
`Copilot Memory` adds deletion, repo scope controls, and CLI settings
70radar
Copilot MemoryCoding assistant memory — persists project context for suggestions
Memory governance is getting less risky. Repo-level shutoff and CLI controls make preview trials easier.
- Improved deletion controls reduce stale or sensitive context risk when Copilot Memory learns the wrong thing.
- A repository-level off switch matters for client work, OSS repos, or codebases where persisted context is unwanted.
- More controls in the Copilot CLI move memory management closer to daily terminal workflows, not just web settings.
Source: github.blog/changelog/2026-05-26-copilot-memory-has-moreRead original →
FIG-0031:1
70radar
FIG-0031:1

`Cursor` Official Plugin Spec and Marketplace Repo

// related

`bulkrender-mcp` added for template-based `DOCX`/`PDF` generation

Learning App Building with `Claude Code`: Start from Architecture, Not Code

`Copilot Memory` adds deletion, repo scope controls, and CLI settings