Skip to content

Improve plugin customizer for scoped and general customization#54

Open
lee-weisberger wants to merge 2 commits intomainfrom
lee/plugin-customizer-improvements
Open

Improve plugin customizer for scoped and general customization#54
lee-weisberger wants to merge 2 commits intomainfrom
lee/plugin-customizer-improvements

Conversation

@lee-weisberger
Copy link
Collaborator

@lee-weisberger lee-weisberger commented Feb 13, 2026

Summary

  • Flexible customization modes: The plugin customizer now supports three modes — scoped (targeting a specific plugin section), generic (template setup with ~~ placeholders), and general (tweaking an already-configured plugin) — instead of only handling generic template setup.
  • Phase 0 for user intent: Added an upfront intent-gathering phase so the customizer uses context the user already provided and avoids redundant questions. Without this, it felt weird getting peppered with questions when I didn't even describe what I wanted to do

(unrelated)

  • MCP and schema improvements: Clarified SSE/HTTP transport descriptions in component schemas, documented name-based matching for MCP directory entries without URLs.

Test plan

  • Verify scoped customization works when user asks to customize a specific plugin section (e.g., "customize the connectors")
  • Verify generic plugin setup still works for plugins with ~~ placeholders
  • Verify general customization mode activates for already-configured plugins
  • Verify Phase 0 captures user-provided context and skips redundant questions

Changelog

Plugin customizer now supports scoped and general customization in addition to generic template setup, with improved user intent gathering.

🤖 Generated with Claude Code (0% 1-shotted by claude-opus-4-6)

- Add three customization modes: scoped (specific section), generic
  (template setup with ~~ placeholders), and general (tweaking existing)
- Add Phase 0 for gathering user intent before diving into customization
- Clarify MCP server type descriptions (SSE/HTTP transport labels)
- Document directory entries without URLs (name-based matching)
- Update component-schemas.md with consistent MCP terminology

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@lee-weisberger lee-weisberger requested a review from a team February 13, 2026 20:15
Comment on lines +326 to +330
| Type | Best for | Transport |
|------|----------|-----------|
| stdio | Local tools, custom servers | Subprocess (stdin/stdout) |
| SSE | Remote servers using server-sent events | HTTP + SSE streaming |
| HTTP | Remote servers using streamable HTTP | HTTP request/response |
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thoughts on just removing this section? it isn't helpful

Comment on lines +89 to +91
### Directory Entries Without a URL

Some directory entries have no `url` because the endpoint is dynamic — the admin provides it when connecting the server. These servers can still be referenced in the plugin's MCP config by **name**: if the MCP server name in the config matches the directory entry name, it is treated the same as a URL match. No newline at end of file
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is useful functionality. The thing I deleted is not accurate - they can still be added like all other mcps

Comment on lines -28 to -34
The process:
1. **Gather context** — use knowledge MCPs to learn what tools and processes the organization uses
2. **Create todo list** — grep for `~~\w` to find all customization points and build a todo list
3. **Complete todo items** — apply gathered context, falling back to user questions when unclear
4. **Search for useful MCPs** — find and connect MCPs for identified tools
> **Important**: Never change the name of the plugin or skill being customized. Do not rename directories, files, or the plugin/skill name fields.
If an answer cannot be found via knowledge MCPs or user input, leave the customization point unchanged for a future customization cycle.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude recommended deleting this - it's all stated later and this only applies for the generic plugin setup

## Customization Workflow

### Phase 0: Gather User Intent (scoped and general customization only)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It felt broken without this - I asked to customize a single thing and I got peppered with questions before I could say what I wanted to customize

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