「repo」の検索結果

GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific optimization, schema markup, technical SEO, content quality (E-E-A-T), and client-ready GEO report generation. Use when user says "geo", "seo", "audit", "AI search", "AI visibility", "optimize", "citability", "llms.txt", "schema", "brand mentions", "GEO report", or any URL for analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need blast-radius analysis, dependency graphs, cross-repo impact, breaking-change diff, or architectural overview of .NET workspaces. Keywords: blast radius, dependency graph, impact analysis, cross-repo, call graph, endpoint map, EF Core lineage, breaking change, daemon, reindex.

日本語の概要は準備中です。原文の説明を表示しています。

日本語の文章 (Markdown・テキスト) から「AI 臭さ」(LLM の文章に特有の定型句・単調な文のリズム・ 見出しと箇条書きだけの体裁) を検出する CLI。日本語の文章を書いた・直した後の見直し、 AI が書いたような文を自然にしたいとき、推敲・校正・AI っぽさのチェック、改稿の前後の比較 (数字や固有名詞が消えていないか・同じ直しを一律に当てていないか) の場面で発動。コードに書いた 日本語のコメント・静的な文字列・JSX/HTML の表示文言 (コードのファイルも直接検査できる) や、gws で Google ドキュメント・スプレッドシートに書き込む文章の見直し、noslop のフックが指摘を返した・ gws の書き込みを止めたときの対応にも使う。 noslop check --report brief --format toon で直す箇所を少ないトークンで受け取り、 改稿のルールに従って効果の大きい箇所だけを直す。直した後は noslop diff で 1 回だけ確かめる。

Guia completo de desenvolvimento backend para microserviços Node.js/Express/TypeScript. Use ao criar routes, controllers, services, repositories, middleware ou trabalhar com Express APIs, acesso a banco de dados com Prisma, rastreamento de erros com Sentry, validação com Zod, unifiedConfig, injeção de dependências ou padrões assíncronos. Cobre arquitetura em camadas (routes → controllers → services → repositories), padrão BaseController, tratamento de erros, monitoramento de performance, estratégias de testes e migração de padrões legados.

日本語の概要は準備中です。原文の説明を表示しています。

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

日本語の概要は準備中です。原文の説明を表示しています。

Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.

日本語の概要は準備中です。原文の説明を表示しています。

Project-level workflow for turning GitHub repositories, URLs, local product materials, or markdown drafts into WeChat Official Account articles and draft-box submissions. Use when the user asks to write, adapt, illustrate, verify, or publish a WeChat/公众号 article, especially from a GitHub repo or existing technical/product material.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says "research", "investigate", "analyze in depth", "compare X vs Y", "what does the market look like for", or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30-120 seconds. For quick fact-finding, use tavily-search instead.

日本語の概要は準備中です。原文の説明を表示しています。

把多页 HTML 报告(主页 + N 子页 + PNG 资产)合并为单一独立 HTML / PDF / XLSX 三件交付物。 Use when finalizing a disease market sizing report and need shareable deliverables — single-file HTML for email/IM(零依赖,双击浏览器开), optional PDF for print/archive, XLSX for data export. 领域无关、跨疾病通用。 下游 of disease-market-sizing-html-template;上游 of email/IM/print 分发。 Use proactively whenever the user says "做交付物" / "生成 PDF" / "导 Excel" / "合并单文件 HTML"。

日本語の概要は準備中です。原文の説明を表示しています。

Create or refresh original product hero images, interface screenshots, and image-led README sections for GitHub repositories. Use when a user asks to make a GitHub README show the product visually, add screenshots, design a README hero image, or prepare repository-bound visual documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

日本語の概要は準備中です。原文の説明を表示しています。

Use FIRST when user requests any disease market sizing report (e.g. "做 X 市场调研" / "Run market sizing for X"). Elicits 4-6 startup questions (evidence window, geography, international comparison, report depth, user role) and writes .cache/<slug>/contract.json. ALWAYS invoke before disease-market-sizing-orchestration. Validates against schemas/contract.schema.json.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 5 part of disease-market-sizing-orchestration. Injects consulting palette (navy/gold/blue) + base CSS + floating TOC + section dividers into raw report HTML. Validates token coverage ≥60% (warn) and floating TOC li ≥5 (block). Use AFTER content-verification passes, BEFORE report-bundle-builder build_all_deliverables.

日本語の概要は準備中です。原文の説明を表示しています。

Create or refresh screenshot-led product hero images, localized interface captures, and image-led README sections for GitHub repositories. Use whenever a user asks to make a GitHub README show a GUI product visually, add software screenshots, design a README hero image, reproduce a screenshot-collage reference, or prepare repository-bound visual documentation. For GUI applications, default to the deterministic product-proof split hero with real software screenshots unless the user explicitly requests another visual direction.

日本語の概要は準備中です。原文の説明を表示しています。

Build incident response timelines and report packs from event logs. Use for detection-to-recovery reporting, phase tracking, and stakeholder-ready incident summaries.

日本語の概要は準備中です。原文の説明を表示しています。

Aggregate findings and generate multi-format pentest reports with remediation roadmap and risk scoring.

日本語の概要は準備中です。原文の説明を表示しています。

Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.

日本語の概要は準備中です。原文の説明を表示しています。

All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.

日本語の概要は準備中です。原文の説明を表示しています。

Runs macOS upkeep: Homebrew update and upgrade, pulling clean git repositories, and emptying the Trash. Use when asked for Mac cleanup, maintenance, or a refresh of packages and repos.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

日本語の概要は準備中です。原文の説明を表示しています。

Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.

日本語の概要は準備中です。原文の説明を表示しています。

Installs John Papa's ai-ready skill, which makes a repository AI-ready by generating AGENTS.md, copilot-instructions.md, CI workflows, and issue templates. Use when the user asks to make a repo AI-ready or set up AI agent configuration for a project.

日本語の概要は準備中です。原文の説明を表示しています。