Loading...
Loading...
Found 12,175 Skills
Draw **container-based layered diagrams** with D2 (d2lang.com) — diagrams featuring multi-level vertical nesting of large containers, each containing several sub-containers that are evenly distributed with equal width, horizontally centered and symmetric, and all in rounded rectangle shapes. Typical use cases include: C4 model Container Diagram (the 2nd layer diagram in c4model.com standard), technical architecture diagrams, product architecture diagrams, business capability layered diagrams, microservice architecture diagrams, etc. **Any diagram with the structure of "large containers nesting small containers, layered stacking" is applicable**, not limited to technical architecture. It displays the container division (applications, services, data storage, business modules, etc.) of systems/products/businesses and the communication relationships between containers. Rendered via Markdown embedded ```d2 code blocks. Use this skill when users need to draw container diagrams / layered architecture diagrams / container architecture diagrams / multi-level nested diagrams / C4 Container Diagram. **Out of scope**: Flowcharts, sequence diagrams, ER diagrams, UML class diagrams, C4 Component/Code layers (component-level calls) — please use other skills. ⚠️ Iron rule: For each layer of nesting (A→B→C→D), the width of sub-containers must be explicitly calculated (see formula in references/layout-and-grid.md; **the only exception: single-column vertical bars do not require setting width**, let ELK automatically wrap and center them). ⚠️ Multi-board diagrams (layers/scenarios/steps) are prohibited.
Creates useful Mermaid diagrams for SWE, DevOps, and Platform Engineering work — PRs, ADRs, RFCs, runbooks, incident reviews, roadmaps, system architecture, and more. Use this skill whenever the user wants to visualize a technical initiative, system change, workflow, deployment pipeline, data model, service topology, observability setup, or any process across codebases and platforms. Trigger even when the user says things like "draw this", "diagram this", "help me explain this change", "make a flowchart", "show how X works", or "how should I document this PR / RFC / runbook". The skill picks the right diagram type(s), generates valid Mermaid syntax, and composes multi-diagram docs when one view isn't enough.
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. Inside: 4-step research framework (website → social → traffic → ad spend) · 3-version Wayback evolution analysis · X/Twitter propagation-chain mapping · growth-flywheel 6-stage scoring · KOL identification · content-effectiveness ranking · ICP + freemium pricing teardown · self-check checklist. New in 1.2: time-machine competitor archaeology — Google date-range search back to pre-fame years, star-history launch-day reconstruction (AppFlowy ~40-channel zero-budget launch teardown), competitor funding news as a launch-timing signal, and the "open source alternative" positioning play. Sourced from first-hand founder interviews (AFFiNE co-founder, 2026-04, self-reported figures marked). 🇨🇳 Your competitor just blew up. You have no idea how they did it. Should you tear down their website? Monitor their social media? Map their growth flywheel? This SOP provides you with a complete methodology from Wayback Machine snapshots to X/Twitter propagation chain reconstruction to 6-stage growth flywheel scoring. Built from 150+ AI startup competitive analysis practices, including the full Lovable case study. 🇯🇵 Your competitor suddenly went viral. You have no idea how they grew. This SOP provides a complete competitive research framework from Wayback snapshots to Twitter propagation chain analysis to 6-stage flywheel scoring. Built from analysis of over 150 AI startups. 🇰🇷 Your competitor has suddenly grown explosively. You don't know how they grew so fast. This SOP provides a complete competitor research framework from Wayback snapshots to X/Twitter propagation chain analysis to 6-stage flywheel scoring. Built from analysis of over 150 AI startups. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "competitor research" | "competitive analysis" | "growth flywheel" | "propagation chain" | "competitive analysis" | "competitor analysis" | "social media teardown" | "Twitter propagation" | "content strategy analysis"
This skill should be used when the user designs a "message queue", reaches for "Kafka", "RabbitMQ", "SQS", "Kinesis", "pub/sub", or "event-driven" architecture, asks about "async processing", "background jobs", "stream processing", or wrestles with "exactly-once vs at-least-once", "delivery guarantees", "message ordering", "duplicate handling / dedup", "dead letter queue", "backpressure", "saga orchestration", or "durable workflow". Use it whenever a slow or spiky operation should move off the request path, or two services must be decoupled, even if the user doesn't say "queue".
Perform a security-focused code review — map trust boundaries, audit input paths and auth flows, and use vulnerability-class-driven checklists instead of line-by-line skimming. Use on any PR or codebase with security implications.
Debug Flutter applications systematically with this comprehensive troubleshooting skill. Covers RenderFlex overflow errors, setState() after dispose() issues, null check operator failures, platform channel problems, build context errors, and hot reload failures. Provides structured four-phase debugging methodology with Flutter DevTools, widget inspector, performance profiling, and platform-specific debugging for Android, iOS, and web targets.
Create new skills for the lovstudio/skills repo. Fork of the official skill-creator with lovstudio conventions: lovstudio: name prefix, skills/lovstudio-<name>/ directory structure, mandatory README.md per skill, SKILL.md with AskUserQuestion interactive flow, standalone Python CLI scripts, CJK text handling, and auto-update of root README + CLAUDE.md. Use when the user wants to create a new skill, add a skill to this repo, scaffold a skill, or mentions "新建skill", "创建skill", "new skill", "add skill", "生成skill".
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Baidu E-commerce skill for cross-platform price comparison, review analysis, and purchase knowledge. Complete workflow from product discovery to purchase decision. Use when user wants to compare prices, read reviews, or make purchase decisions.
Create and format WeChat Official Account (公众号) articles with proper Markdown-to-WeChat HTML conversion, rich formatting, cover image guidance, and both API and manual publishing workflows.
Create professional presentations using the Pyramid Principle methodology. Supports PPTX generation, Marp/Reveal.js Markdown slides, chart creation, speaker notes, and self-evaluation rubrics. Minimal intake form to rapid output workflow.
Miaoda App Builder - create web apps, WeChat mini-programs, games, AI tools, SaaS products, and dashboards through natural language conversations. Full workflow from code generation to deployment.