MCP - Add prompts to assist with component selection, implementation, and debugging

[zamoore]

📌 Summary

Adds four MCP prompts to help users select, implement, review, and troubleshoot Helios components and patterns using documented guidance and resolved component APIs.

🛠️ Detailed description

• Adds and registers four prompts:
  • choose_hds_component — recommends a component or pattern with rationale, alternatives, accessibility considerations, and a verified API starting point.
  • implement_hds_pattern — guides clients to produce a focused Ember .gts implementation with integration test examples and explicit application-owned responsibilities.
  • review_hds_usage — reviews supplied code for API usage, composition, and accessibility responsibilities, returning prioritized findings and suggested corrections.
  • troubleshoot_hds_component — compares expected and observed behavior to suggest evidence-backed causes, targeted diagnostics, and minimal corrections.
• Guides clients through documentation discovery and API verification, with shared guidance for handling fallback package versions, bundled documentation, and missing evidence.
• Introduces a typed registration helper that preserves each prompt’s argument schema and callback types.
• Adds shared argument validation and message construction, including whitespace trimming, blank-input rejection, length limits, and separation of user input from workflow instructions.
• Adds integration coverage for prompt discovery, argument metadata, generated messages, input separation, and validation boundaries, plus minor changesets for the MCP package.

🔗 External links

Jira ticket: HDS-6690

---

👀 Component checklist

• Percy was checked for any visual regression
• A changelog entry was added via Changesets if needed (see templates here)

💬 Please consider using conventional comments when reviewing this PR.

📋 PCI review checklist

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've worked with GRC to document the impact of any changes to security controls.
  Examples of changes to controls include access controls, encryption, logging, etc.
• If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
  Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
hds-showcase	Ready	Preview	Sep 18, 2026 7:00pm UTC
hds-website	Ready	Preview	Sep 18, 2026 7:00pm UTC

[Copilot]

🟢 Approval recommended

The implementation, tests, documentation, and changeset are consistent with the stated scope, with no blocking defects found.

Pull request overview

Adds four MCP prompts for selecting, implementing, reviewing, and troubleshooting Helios components using verified APIs and documentation.

Changes:

• Registers typed prompt workflows with shared validation and context handling.
• Adds integration tests for discovery, schemas, normalization, and validation.
• Updates MCP documentation and adds a changeset.

File summaries

File	Description
packages/mcp/src/prompts/*.ts	Implements and registers the four prompts and shared helpers.
packages/mcp/tests/integration/prompts/*.test.ts	Covers prompt behavior and validation.
packages/mcp/README.md	Formats the MCP configuration example.
.changeset/clear-components-guide.md	Documents the new prompts.

Review details

• Files reviewed: 11/11 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.