Control Chrome browser through MCP for testing, debugging, network analysis, and performance profiling. Use when testing web apps, measuring Core Web Vitals, analyzing network requests, debugging console errors, or when the user mentions Chrome DevTools, performance traces, or browser automation.

2025-10-260

copilotkit-pitch-deck

amo-tech-ai/medellin-spark

Production-ready CopilotKit pitch deck wizard in main application. Use when enhancing AI conversation features, optimizing Edge Function integration, debugging chat interface, or improving pitch deck generation flow. System is PRODUCTION READY (98/100).

2025-10-260

dev-checker

amo-tech-ai/medellin-spark

Runs pre-commit checks and validates code quality. Use when preparing commits, running pre-deploy checks, or validating code before deployment.

2025-10-260

frontend-component-builder

amo-tech-ai/medellin-spark

Generate and refactor React + TypeScript components with Tailwind CSS for Medellin Spark. Use when building new UI components, creating dashboards, forms, cards, or wizards. Automatically includes accessibility, responsive design, and Vite-compatible code with optional tests.

2025-10-260

pitch-deck-generator

amo-tech-ai/medellin-spark

Guides through AI pitch deck generation workflow and troubleshooting. Use when creating pitch decks, debugging wizard errors, troubleshooting Edge Functions, or working with the PitchDeckWizard component.

2025-10-260

production-deploy

amo-tech-ai/medellin-spark

Production deployment checklist and procedures for Medellin Spark. Use when deploying to production, performing releases, or setting up production infrastructure.

2025-10-260

name	commit-helper
description	Generates clear commit messages following project conventions
version	1.0.0

Commit Helper Skill

Purpose

Generate commit messages that follow project standards.

Format

<type>: <subject>

<body>

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Types

feat - New feature
fix - Bug fix
refactor - Code restructure (no behavior change)
docs - Documentation only
test - Add/update tests
chore - Build/tooling changes
security - Security improvements

Examples

Feature Addition

feat: Add user authentication flow

- Implement JWT token validation
- Add login/logout endpoints
- Update user profile schema
- Add protected route component

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Bug Fix

fix: Resolve slide grid loading issue

- Enable RLS policy for public presentations
- Update query to include is_public filter
- Add error handling for missing data

Fixes presentation viewer stuck on loading state.

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Security Update

security: Move API keys to Edge Functions

- Create OpenAI proxy Edge Function
- Remove VITE_OPENAI_API_KEY from frontend
- Update PitchDeckWizard to use proxy endpoint
- Add server-side key validation

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Process

Analyze Changes
```
git diff --staged
```
Identify Type
- New feature? → feat
- Fixing bug? → fix
- Security? → security
- Cleanup? → refactor
Write Subject
- Start with verb (Add, Fix, Update, Remove)
- Keep under 50 characters
- No period at end
Add Body
- Bullet points for key changes
- Explain WHY not just WHAT
- Reference issues if applicable

Usage

Just ask: "Generate commit message" or "What should I commit?"

I'll review staged changes and create a proper message.