8,862 件 ・ 関連度順
概要と使いどころ
Aumenta resolução e qualidade de imagem via Freepik/Magnific, ou orienta o processo manual quando não há chave. Use quando o usuário disser "upscale", "melhorar a resolução", "a imagem está pixelada", "Magnific", "Freepik", "aumentar a imagem", "imagem pequena demais". Gasta crédito — exige confirmação.
日本語の概要は準備中です。原文の説明を表示しています。
Design traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Enable, record, query, summarize, or verify the opt-in PWDEV Flow semantic audit trail. Use when the user asks what Flow actions occurred, wants audit integrity checked, or needs a portable JSONL record of workflow gates and artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Identifica padrões entre muitas peças de copy — quais ganchos, ângulos, formatos, temas e horários rendem mais. Use quando o usuário disser "o que funciona melhor", "qual padrão", "por que uns posts vão bem e outros não", "analisar histórico", "o que devo fazer mais", "tendência do conteúdo". Exige volume: abaixo de 20 peças, o resultado é observação, não padrão.
日本語の概要は準備中です。原文の説明を表示しています。
Define, documenta e aplica a voz da marca — formalidade, personalidade, vocabulário preferido, palavras proibidas e tratamento do leitor. Use quando o usuário disser "voz da marca", "tom de voz", "brand voice", "guia de estilo", "padronizar o tom", "não parece nossa marca", "manual de redação", ou quando precisar auditar se um texto está aderente. Extrai a voz de amostras reais em vez de inventar adjetivos, e grava o resultado na seção 5 de .claude/pwdev-copy-context.md para todas as demais skills consumirem.
日本語の概要は準備中です。原文の説明を表示しています。
Escreve ou reescreve copy de páginas de marketing — home, landing page, página de preço, de produto, de funcionalidade, institucional. Use quando o usuário disser "escrever copy", "criar landing page", "reescrever essa página", "preciso de headline", "melhorar o CTA", "copy do site", "texto da home". Para e-mail use copy-email; para anúncio use copy-ads; para revisar texto pronto use copy-review.
日本語の概要は準備中です。原文の説明を表示しています。
Escreve microcopy de interface — mensagens de erro, estados vazios, tooltips, rótulos de botão, onboarding e notificações. Use quando o usuário disser "UX writing", "microcopy", "mensagem de erro", "empty state", "texto do botão", "texto da interface", "onboarding do sistema".
日本語の概要は準備中です。原文の説明を表示しています。
Gera e testa ganchos — primeira linha de post, abertura de e-mail, headline de anúncio, texto de miniatura, título de vídeo. Use quando o usuário disser "gancho", "hook", "primeira linha", "abertura", "como começar o post", "ninguém passa da primeira linha", "chamada", "título que prenda", ou quando pedir variações de abertura. Trabalha por biblioteca de 9 padrões nomeados, não por inspiração. Para o texto completo, ver copy-social, copy-email ou copy-ads.
日本語の概要は準備中です。原文の説明を表示しています。
Quality gates determinísticos para PostgreSQL. Use quando o usuário pedir "quality gate PostgreSQL", "quality gate Postgres", migrations ou schema drift PostgreSQL, constraints ou índices PostgreSQL, EXPLAIN, plano de consulta ou baseline para PostgreSQL.
日本語の概要は準備中です。原文の説明を表示しています。
Wire up GSettings: schema authoring, key naming, settings binding to widgets, window state persistence. Use when persisting app settings or window size/state in a GNOME app.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a minimal GNOME-compliant GTK4/libadwaita app from scratch — window, header bar, ViewSwitcher, adaptive breakpoint, menu, preferences, GSettings schema, desktop entry, meson. Use when starting a new GNOME app or when the user asks for a GNOME app template.
日本語の概要は準備中です。原文の説明を表示しています。
Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring techniques like extracting functions, removing duplication, simplifying conditionals, and applying design patterns. Use when reducing technical debt, extracting functions or classes, removing code duplication, simplifying complex conditionals, renaming for clarity, applying design patterns, improving code organization, reducing coupling, increasing cohesion, or maintaining test coverage during structural improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems.
日本語の概要は準備中です。原文の説明を表示しています。
Organize, categorize, rename, and manage files systematically using automated rules, naming conventions, and folder structures for efficient file management. Use when organizing uploaded files, implementing file naming conventions, categorizing files by type or metadata, creating folder structures, cleaning up messy directories, automating file movements, implementing media libraries, or building file management systems.
日本語の概要は準備中です。原文の説明を表示しています。
Build real-time, reactive backend applications with Convex using TypeScript queries, mutations, and actions with automatic reactivity and optimistic updates. Use when building real-time collaborative applications, implementing reactive data synchronization, writing serverless backend functions, creating queries that auto-update, implementing mutations with transactional guarantees, handling file uploads with Convex storage, implementing authentication with Convex Auth, designing reactive database schemas, or building applications requiring instant data synchronization.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically review pull requests, feature implementations, and code changes to ensure quality, maintainability, security, and adherence to best practices. Use when reviewing code before merging, conducting peer reviews, performing self-reviews, auditing code quality, checking for security vulnerabilities, ensuring consistent coding standards, verifying test coverage, assessing performance implications, evaluating architectural decisions, or providing constructive feedback to improve team code quality.
日本語の概要は準備中です。原文の説明を表示しています。
Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute database migrations, data transformations, and system migrations safely with rollback strategies and data integrity validation. Use when migrating databases, transforming data schemas, moving between database systems, implementing versioned migrations, handling data transformations, ensuring data integrity, or planning zero-downtime migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.
日本語の概要は準備中です。原文の説明を表示しています。
Roslyn-powered semantic query CLI for C# solutions. Use when you need to find references, callers, implementations, dependencies, members, or trace call chains in a C# codebase — replaces multi-round grep/read cycles with single precise queries.
日本語の概要は準備中です。原文の説明を表示しています。
Scrap and regenerate the in-flight EF migrations on the current branch as one consolidated migration. Use when migrations have accumulated mid-development cruft (added/removed columns, stacked add-column-to-existing-table fixes, hand-edited SQL that needs to come out, schema changes that should have been one migration but ended up as five), or when the branch has merged main and its migrations are now stuck mid-chain so `dotnet ef migrations remove` is unsafe. Triggers on phrases like 'regen the migrations', 'redo these migrations', 'scrap and regen migrations', 'consolidate the in-flight migrations', 'redo the migration stack', or any time an agent hits the mid-chain situation in `memory/architecture/migration-regen-after-rebase.md`.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
日本語の概要は準備中です。原文の説明を表示しています。