4,145 件 ・ 関連度順
概要と使いどころ
kpopper Hub: optional experimental application for exploring the project record. Use when the user explicitly requests kpopper Hub or its record page, its graph, layout or verification, or has a standing preference for this application. Do not render automatically after mapping or recording. Install the HTML runtime before use. Not for ordinary HTML documents or a text answer from the record. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically find and fix performance problems in applications, frontend and backend, by measuring first. Use this skill whenever the user reports slow endpoints, high latency, poor throughput, memory leaks, large bundles, or slow page loads; wants to profile with cProfile, py-spy, Chrome DevTools, Node --cpu-prof, or perf; run load tests with locust or k6; set performance budgets or SLOs; optimize database queries (EXPLAIN, indexes, N+1); add caching (Redis); improve frontend performance (code splitting, lazy loading, image optimization, memoization, virtualization); or tune the network (CDNs, gzip/br, HTTP/2/3). Also trigger for p50/p95/p99 latency, throughput, error rate, connection pooling, async vs threads, GIL, and memory leak investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Opinionated constraints for building better web interfaces with coding agents. Use this skill whenever the user asks you to build, review, or fix a UI — landing pages, dashboards, components, or any frontend code — and whenever you write Tailwind CSS, motion/react animations, accessible component primitives (Base UI, React Aria, Radix), or review agent-generated interface code for quality, accessibility, and performance. Also trigger for "make the UI better", "review my interface", "clean up this component", or any frontend work in React, Next.js, or plain HTML/CSS.
日本語の概要は準備中です。原文の説明を表示しています。
Create and publish a recurring client-facing deliverable — SEO or analytics monthly, project status report, audit results — as a branded live page with view tracking. Use when the user says "client report", "monthly report for", "status update for the client", "send this to my client". Not for one-off research shares (use report-publisher) or proposals (use proposal-tracker).
日本語の概要は準備中です。原文の説明を表示しています。
Polish an existing report, deck, or HTML page to the ReportRoom design bar — visual hierarchy, typography, charts, dark mode, OG/social link preview. Use when the user says "make it beautiful", "improve the design", "it looks plain", "fix the layout" about something already written or published. Not for creating content from scratch (use report-publisher or deck-publisher).
日本語の概要は準備中です。原文の説明を表示しています。
Turn research, analysis, or any markdown the agent just produced into a live, beautifully designed web report with a shareable tracked URL via ReportRoom. Use when the user says "publish this", "make this shareable", "turn this into a report", "put this on a page", or wants findings to live beyond the chat. Not for recurring client deliverables (use client-reporter), slide decks (use deck-publisher), or proposals that need view alerts (use proposal-tracker).
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a Playwright suite — locator strategy, Page Object boundaries, fixture composition, flake-prevention architecture, CI-vs-local split — even on 'design our E2E tests'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a Livewire component before code — full-page vs partial, parent/child split, event flow, state-vs-props boundary, hydration cost — even on 'add this Livewire component'.
日本語の概要は準備中です。原文の説明を表示しています。
Implante aplicações e infraestrutura na Cloudflare usando Workers, Pages e serviços relacionados da plataforma. Use quando o usuário pedir para implantar, hospedar, publicar ou configurar um projeto na Cloudflare.
日本語の概要は準備中です。原文の説明を表示しています。
Crie designs de websites premium com qualidade Awwwards como componentes React (.jsx) que pareçam ter sido construídos por uma agência de primeira linha cobrando R$250k+ por projeto. Use esta skill sempre que o usuário pedir um website, landing page, portfólio, ou componente web que deve parecer caro, premium, luxo, editorial, high-end, ou de qualidade agência. Também dispare quando o usuário mencionar Awwwards, FWA, design premiado, ou referenciar marcas como Apple, Aesop, Bottega Veneta, Stripe, ou qualquer marca luxury/fashion/design-forward. Dispare quando o usuário disser coisas como "faça parecer profissional", "faça parecer caro", "quero que fique realmente bom", "design de alta qualidade", "não genérico", ou expressar insatisfação com aesthetics típicos de websites gerados por IA. NÃO dispare para dashboards, admin panels, ferramentas internas, ou UI funcional onde aesthetics são secundárias à utilidade — a skill padrão frontend-design cuida disso.
日本語の概要は準備中です。原文の説明を表示しています。
Inteligência de design UI/UX. 50 estilos, 21 paletas, 50 combinações de fontes, 20 gráficos, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Ações: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projetos: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elementos: button, modal, navbar, sidebar, card, table, form, chart. Estilos: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Tópicos: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrações: shadcn/ui MCP para busca de componentes e exemplos.
日本語の概要は準備中です。原文の説明を表示しています。
Criar interfaces frontend distintas e de qualidade produtiva com alto padrão de design. Use essa habilidade quando o usuário pedir para construir componentes web, páginas, artefatos, pôsteres ou aplicações (exemplos incluem websites, landing pages, dashboards, componentes React, layouts HTML/CSS, ou ao estilizar/embelezar qualquer UI web). Gera código criativo e polido com UI design que evita estéticas genéricas de IA.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer auditar, revisar ou diagnosticar problemas de SEO no seu site. Também use quando o usuário menciona "auditoria de SEO," "SEO técnico," "por que não estou ranqueando," "problemas de SEO," "SEO on-page," "revisão de meta tags," ou "verificação de saúde de SEO." Para construir páginas em escala visando palavras-chave, veja programmatic-seo. Para adicionar dados estruturados, veja schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
Especialista em Otimização para Mecanismos de Busca para estratégia de conteúdo, SEO técnico, pesquisa de palavras-chave e melhorias de ranqueamento. Use ao otimizar conteúdo do site, melhorar ranqueamentos de busca, realizar análise de palavras-chave ou implementar melhores práticas de SEO. Especialista em SEO on-page, meta tags, schema markup e Core Web Vitals.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário deseja criar ou otimizar popups, modais, overlays, slide-ins ou banners para fins de conversão. Use também quando o usuário menciona "exit intent," "conversões de popup," "otimização de modal," "popup de captura de leads," "popup de email," "banner de anúncio" ou "overlay." Para formulários fora de popups, consulte form-cro. Para otimização geral de conversão de página, consulte page-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer criar ou otimizar paywalls in-app, telas de upgrade, modais de upsell ou feature gates. Use também quando o usuário mencionar "paywall", "tela de upgrade", "modal de upgrade", "upsell", "feature gate", "converter free para paid", "conversão freemium", "tela de expiração de trial", "tela de limite atingido", "prompt de upgrade de plano" ou "preço in-app". Distinto de páginas de preço públicas (veja page-cro) — esta skill foca em momentos de upgrade in-product onde o usuário já experimentou valor.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer criar páginas de comparação com concorrentes ou alternativas para SEO e ativação de vendas. Use também quando o usuário menciona 'página de alternativas', 'página vs', 'comparação com concorrentes', 'página de comparação', '[Produto] vs [Produto]', '[Produto] alternativa', ou 'landing pages competitivas'. Cobre quatro formatos: alternativa singular, alternativas plurais, você vs concorrente, e concorrente vs concorrente. Enfatiza pesquisa profunda, arquitetura de conteúdo modular e tipos de seção variados além de tabelas de recursos.
日本語の概要は準備中です。原文の説明を表示しています。
Framework para construir aplicações com LLM usando agentes, chains e RAG. Suporta múltiplos provedores (OpenAI, Anthropic, Google), 500+ integrações, agentes ReAct, tool calling, gerenciamento de memória e recuperação de vector stores. Use para construir chatbots, sistemas de perguntas e respostas, agentes autônomos ou aplicações RAG. Ideal para prototipagem rápida e deployments em produção.
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
日本語の概要は準備中です。原文の説明を表示しています。
Use this Canvas-owned clean-room skill for creating, reading, editing, reviewing, redlining, commenting, or repairing Word `.docx` documents. Trigger for Word documents, DOCX files, memos, reports, letters, templates, tracked changes, comments, table of contents, headers, footers, page numbers, and Google Docs-targeted documents that should be authored as DOCX first.
日本語の概要は準備中です。原文の説明を表示しています。
Use this Canvas-owned clean-room skill for PDF work where layout, extraction, generation, forms, page operations, or visual verification matter. Trigger for reading PDFs beyond plain text, creating PDFs, merging, splitting, rotating, watermarking, extracting tables or images, filling forms, OCR handoff, and final PDF QA.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill when writing, reviewing, or interpreting behavioral accessibility automation — tests that manipulate a rendered page (resizing the viewport, pressing real keys, capturing and comparing screenshots) rather than only inspecting static markup or a single computed accessibility tree. Covers Reflow risk (SC 1.4.10) and Focus Visible risk (SC 2.4.7) checks. Absolutely always report indicator results separately from confirmed failures. Under no circumstances treat a clean behavioral scan as WCAG conformance, or collapse `cantTell`/test-error/indicator outcomes into a single pass/fail signal.
日本語の概要は準備中です。原文の説明を表示しています。