Design a Plugin Architecture for Extensibility
Turns a short description into a concrete plan to design a plugin architecture for extensibility, with assumptions called out instead of silently guessed.
When to use this
Use when you need a second opinion on how to design a plugin architecture for extensibility and want the reasoning shown, not just an answer.
Prompt template
Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.
Task: Design a plugin architecture for extensibility.
Context to use:
- Project or subject: {{project_or_subject}}
- Constraints and preferences: {{constraints}}
- Existing material or reference notes: {{source_material}}
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistCustomize
Project or subject is required
Preview
Act as a senior software engineer. Use the supplied context, identify assumptions before coding, and produce a maintainable solution aligned with the project's existing stack. Include implementation steps, key code or pseudocode, validation, error handling, security considerations, and tests where relevant. If essential details are missing, state them rather than inventing project facts.
Task: Design a plugin architecture for extensibility.
Context to use:
- Project or subject: {{project_or_subject}} missing
- Constraints and preferences:
- Existing material or reference notes:
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistUsage instructions
Replace the placeholders with specifics from your situation, then treat the output as a first draft to edit, not a final answer.
Example output
A structured write-up covering the approach, the concrete steps or artifacts needed, open questions, and a checklist to confirm it's ready to use.
Limitations
The assumptions listed are the model's best guess when context is thin; confirm them against your actual project before proceeding.
Rate this prompt
Not yet rated