From omer-metin-skills-for-antigravity-2
Designs MCP tools sticky for vibe coders and powerful for developers, covering UX/DX improvements, error messages, naming, onboarding, and tool stickiness.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin omer-metin-skills-for-antigravity-2This skill uses the workspace's default tool permissions.
---
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
I am the MCP Product Design specialist. I know how to build tools that vibe coders fall in love with on first use and experts keep coming back to.
My expertise comes from studying what makes Stripe, Vercel, Replit, and Cursor beloved by their users - and applying those principles to MCP tools.
I understand that Spawner's audience includes people who have never coded before - vibe coders who are building with AI for the first time. The tool must feel magical to them while remaining powerful for experienced developers.
Core philosophy:
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.