gk-shadcn-investigate

Resolve shadcn-svelte and Bits UI component API and styling uncertainties via documentation and source inspection.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/MartinoPolo/Grovekeeper --skill gk-shadcn-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-shadcn-investigate
Source: https://github.com/MartinoPolo/Grovekeeper/tree/main/.claude/skills/gk-shadcn-investigate
Command: npx skills add https://github.com/MartinoPolo/Grovekeeper --skill gk-shadcn-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes guesswork when working with shadcn-svelte and Bits UI by letting you verify how components are implemented, styled, and documented so you can debug or make correct design decisions.

Core Features & Use Cases

  • Upstream docs via Context7 MCP: Fetches the latest published API contract for components, including prop types and usage patterns.
  • Source-level exploration via local clones: Inspects real implementation details such as component structure, internal state, utilities, and style tokens.
  • Targeted research for practical outcomes: Helps resolve issues, compare approaches, discover component APIs (props/slots/events), and troubleshoot CSS/animation behavior by tracing what upstream expects.

Quick Start

Ask the AI: “Research how the shadcn-svelte Tabs component implements its props and styling in Bits UI terms, and tell me the key file paths and the exact API surface.”

Frequently Asked Questions about gk-shadcn-investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug broken shadcn-svelte component behavior and styling?

Debug broken shadcn-svelte component behavior by combining Context7 MCP documentation queries with local source code inspection. This approach verifies upstream API contracts, internal state, and style tokens to resolve CSS, animation, and prop issues accurately.

How does Bits UI component API discovery work for shadcn-svelte?

Bits UI component API discovery works by fetching published API contracts via Context7 MCP and inspecting locally cloned repositories. This dual approach reveals exact prop types, slots, events, and implementation-level details for shadcn-svelte components.

Can I use local repository inspection to verify shadcn-svelte component implementation details?

You can verify shadcn-svelte component implementation details using local repository inspection. This method exposes real component structure, internal state, utilities, and style tokens that upstream documentation may not fully detail.

What's the best way to compare shadcn-svelte implementation approaches against Bits UI documentation?

Compare shadcn-svelte implementation approaches by querying Bits UI documentation through Context7 MCP while tracing local source code. This resolves uncertainty by contrasting documented API contracts with actual component structure and runtime behavior.

Why does my shadcn-svelte component styling not match the Bits UI documented behavior?

Your shadcn-svelte component styling may not match documented behavior due to undocumented internal state or style token overrides. Inspecting local source clones alongside Context7 MCP documentation queries traces the exact upstream expectations and resolves discrepancies.