Menu
SkillsMP has collected 68 skills from cardinalconseils/lovable-skills. Open a skill to review its source and details.
Showing 40 of 68 collected skills.
Use when the user wants to build an AI agent, voice agent, chat agent, multi-agent system, RAG pipeline, or MCP server. Also use when the user mentions 'AI agent', 'voice agent', 'chat agent', 'RAG', 'retrieval-augmented generation', 'MCP server',…
Use when the user wants to define KPIs, build a metrics framework, identify leading indicators, create a risk register, or set up governance triggers. Also use when the user mentions 'KPIs', 'metrics framework', 'leading indicators', 'lagging indicators',…
Use when the user wants to create product photography, brand imagery, or commercial photos using AI image generation. Also use when the user mentions 'product photography', 'AI photo', 'brand imagery', 'photo direction', 'gpt-image-1', 'image generation…
Use when the user wants to create AI-generated video content, ads, social clips, or product demos using Kling or similar video generation APIs. Also use when the user mentions 'AI video', 'Kling', 'video generation', 'text to video', 'image to video', 'video…
Use when the user wants to understand compliance requirements, identify regulatory triggers, or know what artifacts are required for GDPR, PCI, HIPAA, or SOC 2. Also use when the user mentions 'compliance', 'GDPR', 'PCI DSS', 'HIPAA', 'SOC 2', 'data privacy',…
Use when the user wants to build programmatic SEO pages, template-driven content at scale, location pages, comparison pages, or data-driven landing pages. Also use when the user mentions 'programmatic SEO', 'pSEO', 'template pages', 'location pages',…
Use when the user wants to build or improve their revenue operations, lead scoring, sales funnel, CRM hygiene, or pipeline velocity. Also use when the user mentions 'RevOps', 'MQL', 'SQL', 'lead lifecycle', 'pipeline velocity', 'CRM hygiene', 'attribution',…
Use when the user wants to create sales materials, pitch decks, battle cards, one-pagers, objection handling guides, or demo scripts. Also use when the user mentions 'pitch deck', 'sales deck', 'one-pager', 'battle card', 'objection handling', 'demo script',…
Use when the user wants to add structured data, schema markup, or JSON-LD to their pages for rich results in Google search. Also use when the user mentions 'structured data', 'JSON-LD', 'schema.org', 'rich results', 'rich snippets', 'FAQ schema', 'Product…
Use when the user wants to think through business strategy, validate assumptions, identify risks, define success metrics, or analyze market forces. Also use when the user mentions 'Lean Canvas', 'North Star metric', 'pre-mortem', 'PESTLE', 'Ansoff Matrix',…
Use when the user wants to run an A/B test, design an experiment, set up feature flags for testing, or measure the impact of a change. Also use when the user mentions 'A/B test', 'split test', 'experiment design', 'hypothesis', 'statistical significance',…
Use when the user wants to make their app accessible, fix accessibility issues, meet WCAG standards, or support screen readers and keyboard navigation. Also use when the user mentions 'a11y', 'WCAG', 'screen reader', 'keyboard navigation', 'color contrast',…
Use when the user wants to review code or AI output for common mistakes, bad patterns, or quality issues. Also use when the user mentions 'bad code', 'code smell', 'antipattern', 'cleanup', 'technical debt', 'over-engineering', or 'silent failure'.
Use when the user wants to reduce customer churn, improve retention, design a cancellation flow, or build a win-back strategy. Also use when the user mentions 'churn rate', 'customer health score', 'dunning', 'cancellation flow', 'win-back', or 'voluntary…
Use when the user wants to improve code quality, simplify code, refactor for clarity, apply naming conventions, or enforce engineering discipline. Also use when the user mentions 'clean code', 'refactor', 'simplify', 'naming', 'code review', 'readability', or…
Use when the user wants to improve app speed, fix slow load times, reduce bundle size, optimize database queries, or hit Core Web Vitals targets. Also use when the user mentions 'slow page', 'LCP', 'bundle size', 'N+1 query', 'performance audit', 'Lighthouse…
Authentication and authorization patterns for production applications. Use when: adding user login, signup, password reset, social login, role-based access, session management, JWT tokens, OAuth2, MFA, or any auth-related feature. Also use when reviewing auth…
Caching strategy selection and implementation for production applications. Use when: choosing between write-through and write-behind cache, adding Redis or Memcached, reducing write or read latency, designing cache invalidation, implementing read-through or…
Application monitoring, logging, and observability for production applications. Use when: setting up error tracking, adding logging, creating health endpoints, configuring alerting, preparing for production, or when debugging production issues.
Stripe payment integration expertise. Use when implementing Stripe Checkout, Payment Intents, Stripe Elements, Stripe Billing, subscription billing, idempotency keys, Stripe webhook handling, refunds, chargebacks, PCI DSS compliance, dunning, invoicing, or…
Security hardening and OWASP Top 10 prevention for production applications. Use when: reviewing security, handling user input, managing secrets, configuring authentication, setting up HTTPS, adding CSP headers, auditing dependencies, or preparing for…
Test-driven development discipline and testing strategy for production applications. Use when: writing tests, fixing bugs, implementing features, running test suites, choosing what to test, or when the agent skips testing. Enforces RED-GREEN-REFACTOR cycle…
Use when the user wants to audit UI quality, eliminate visual slop, improve visual design, run the impeccable linter, or apply design verbs to improve a screen. Also use when the user mentions 'impeccable,' 'visual slop,' 'AI-generated design,' 'design…
Use when the user wants to design a system before building it, create a design document, define component boundaries, map data flows, or establish API contracts. Also use when the user mentions 'design.md,' 'system design,' 'architecture document,' 'component…
Use when the user wants to design an API, define endpoint contracts, choose between REST and GraphQL, handle authentication, version an API, or define error responses. Also use when the user mentions 'API design,' 'REST conventions,' 'endpoint naming,' 'API…
Use when the user wants to design a database schema, choose between SQL and NoSQL, decide on normalization, set up indexes, handle migrations, or make data modeling decisions. Also use when the user mentions 'schema design,' 'data model,' 'normalization,'…
Use when the user wants a pragmatic, opinionated answer on how to build, architect, or deploy something. Also use when the user mentions 'how should I build this,' 'what stack should I use,' 'architecture decision,' 'should I use microservices,' 'how do I…
Use when the user has a bug, error, crash, performance issue, or test failure they need to diagnose. Also use when the user mentions 'why is this broken,' 'I have a bug,' 'this isn't working,' 'error in production,' 'performance issue,' 'flaky test,' 'root…
Use when the user wants an opinionated product perspective on what to build, how to prioritize, how a feature should work, or how to make a UX decision. Also use when the user mentions 'what should I build,' 'should I add this feature,' 'how do I prioritize,'…
Use when the user wants to structure a frontend application, choose a state management approach, organize components, design a file structure, or make React/TypeScript architectural decisions. Also use when the user mentions 'component design,' 'folder…
Use when the user wants to plan a product launch, define go-to-market strategy, choose distribution channels, sequence their GTM motion, or figure out how to get their first customers. Also use when the user mentions 'GTM,' 'launch strategy,' 'how do I get…
Use when the user wants to design a user interface, create a user flow, improve usability, design empty states or error states, or make UX decisions about navigation or interaction patterns. Also use when the user mentions 'user flow,' 'wireframe,'…
Use when the user wants to write, review, or improve marketing copy — hero headlines, landing page copy, ad copy, or email body. Also use when the user mentions 'copy,' 'headline,' 'CTA,' 'value prop,' 'messaging,' 'write this for me,' or asks for help with…
Use when the user wants to design the architecture of an AI-powered or agentic application. Also use when the user mentions 'state machine,' 'deterministic vs indeterministic,' 'memory layer,' 'dead letter queue,' 'circuit breaker,' 'agent loop,' 'retry…
Use when the user wants to define the aha moment, reduce time to first value, improve new user onboarding, or increase the percentage of signups who become active users. Also use when the user mentions 'activation,' 'aha moment,' 'time to value,' 'onboarding…
Use when the user wants to optimize their content to appear in AI-generated answers, voice search results, featured snippets, or knowledge panels. Also use when the user mentions 'AEO,' 'answer engine optimization,' 'featured snippets,' 'voice search,'…
Use when the user wants to understand the competitive landscape from a product perspective, build competitive battlecards, analyze competitor product strategy, track competitor moves, or prepare for competitive sales situations. Also use when the user…
Use when the user wants to decide what to build next, rank features, cut scope, or make trade-offs between competing requests. Also use when the user mentions 'what should we build,' 'prioritization,' 'RICE,' 'ICE,' 'backlog grooming,' 'MVP scope,' 'feature…
Use when the user wants their brand, product, or content to be cited by AI systems like ChatGPT, Perplexity, Claude, Gemini, or other LLM-powered tools. Also use when the user mentions 'GEO,' 'generative engine optimization,' 'AI citations,' 'getting…
Use when the user wants to understand why customers buy or use a product, define what job a feature is solving, or design features around customer outcomes rather than feature requests. Also use when the user mentions 'JTBD,' 'jobs to be done,' 'what job does…