Add cloud, payment, app store, and design skills with MCP integration

[ydesgagn]

Summary

Expand the plugin with 12 new skills for cloud infrastructure, payments, app stores, observability, deployment, and design review. Add MCP server integration across all existing and new skills with graceful CLI fallbacks, and replace the fix-issue command with a broader work-issue command that supports bugs, features, and tasks with Figma design context.

Key changes:

• Add new skills: appstore, aws, gcloud, heroku, newrelic, paypal, playstore, review-design, stripe, vercel
• Add .mcp.json with bundled MCP server configs (GitHub, Fetch, Context7, PostgreSQL, MySQL, MongoDB, Redis, AWS, App Store Connect, Google Play, gcloud)
• Add MCP tool integration with CLI fallbacks to existing skills (analyze-db, query-db, crashlytics, create-issue, sprint-summary, review-readme, review-architecture, review-user-guide, code-review-deep)
• Replace fix-issue command with work-issue — supports issue type detection (bug/feature/task), MCP tools for GitHub and Jira, and Figma design context extraction
• Add SQLite support to query-db and analyze-db skills
• Expand README with comprehensive setup docs for all integrations (GitHub MCP, Fetch, Context7, Jira, AWS, GCP, App Store Connect, Google Play, databases, remote MCP servers)
• Update plugin.json description and keywords for new capabilities

Types of changes

• Bugfix (fixes an issue)
• New feature (adds functionality)
• Refactoring (improves code without changing functionality)
• Breaking change (incompatible changes)
• Build or security update (updates dependencies, libraries, or security patches)
• Code style or documentation update (formatting, renaming, or documentation changes)
• Other (please describe):

Checklist

• Unit tests added to validate my fix/feature
• I have manually tested my change
• I did not add automation test. Why ?: Plugin skills are tested manually through Claude Code interactions
• Database changes requiring migration with downtime or reprocessing of existing data
• The SOUP file lists the risk Level, requirements and verification reasoning associated with each library
• readme.md includes sections on introduction, installation, usage, and contributing
• docs/architecture.md includes sections on the architecture diagram, software units, software of unknown provenance, critical algorithms and risk controls related to PII and security
• Impact on PII, privacy regulations (CCPA/GDPR/PIPEDA), CIS benchmarks or security (availability/confidentiality/integrity); management must be notified