Diff a project's BOM against the user's local on-hand inventory (the free-form list captured during onboarding). Reports which parts are already available, which need to be ordered, and which have plausible substitutes on hand.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin hardware-spec-assemblyThis skill uses the workspace's default tool permissions.
Lightweight local inventory check — uses the inventory captured during `onboard` (free-form text or local file). For MCP-backed live inventory, use `check-inventory` instead.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
Lightweight local inventory check — uses the inventory captured during onboard (free-form text or local file). For MCP-backed live inventory, use check-inventory instead.
bom.json.inventory_source from config.json. If type is file, read it. If type is mcp, defer to check-inventory. If none, prompt the user to update onboarding.For each BOM line:
Substitutes are suggestions, not silent swaps. Flag every substitute so the user can decide whether the trade-off is acceptable.
Write <projects_dir>/<slug>/coverage.md:
suggest-sourcing-options.Print a one-line summary to the conversation: "X of Y parts on hand; Z need ordering."