Component catalog - Accordion

[zamoore]

📌 Summary

If merged, this PR documents the Accordion component group in the MCP component manifest file.

Copilot instructions

• Treat packages/mcp/src/catalogs/components/catalog.json as generated data; review source-of-truth docs/types, not prose style preferences.
• For component/arg/yield description, verify it matches website/docs/components/**/partials/code/component-api.md wording and meaning (no invented behavior).
• For default, require exact match to docs <C.Property ... @default="..."> when present; missing or different defaults are errors.
• For args, avoid duplicate info in description that is already encoded in type/default; keep behavioral nuance and constraints.
• For blocks, allow only name and yields; block-level descriptions should not be added.
• For yields, confirm name, type, kind, componentName, and boundArgs come from component signature parsing (packages/components/scripts/generate-component-catalog.mjs), not guessed from docs.
• If docs claim contextual yields not present in parsed signatures, classify as docs inconsistency (non-blocking) rather than schema/content corruption.
• Flag placeholders like "description": "TODO" as failures: enrichment did not resolve docs content.
• Ensure final catalog conforms to packages/mcp/src/catalogs/components/schema.ts; schema-valid output is required before accepting additions.
• Prefer exact docs text (minus context-only phrases like “see below”) over paraphrased rewrites when filling descriptions.

📸 Screenshots

🔗 External links

Jira ticket: HDS-6500
Figma file: [if it applies]

---

👀 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 (UTC)
hds-showcase	Ready	Preview	Jul 2, 2026 1:33am
hds-website	Ready	Preview	Jul 2, 2026 1:33am

[Copilot]

Pull request overview

Adds initial MCP component catalog data for the Accordion component group, alongside a Zod schema intended to validate the catalog structure in packages/mcp.

Changes:

• Introduces a Zod schema for the MCP components catalog (componentCatalogSchema).
• Adds catalog.json entries for HdsAccordion and HdsAccordionItem, including args, blocks, and yields metadata.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
packages/mcp/src/catalogs/components/schema.ts	Adds Zod schema/types for validating a component catalog payload.
packages/mcp/src/catalogs/components/catalog.json	Adds Accordion + Accordion::Item catalog entries (args/blocks/yields) for MCP consumption.