3,449 件 ・ 関連度順
概要と使いどころ
Document-code change notification system: traceable doc-code binding via git tree hash, git-diff-driven reconciliation plans with confidence/risk metadata, and idempotent execution. Use when maintaining documentation freshness, detecting stale docs, or binding docs to source code.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Japanese PowerPoint presentations using python-pptx with proper fonts (游ゴシック/Meiryo), business layouts, and Japanese color schemes. Triggers on requests for プレゼン資料, パワーポイント, スライド作成, PowerPoint, PPTX, 発表資料.
Generate Japanese PDFs using reportlab or fpdf2 with CJK font embedding, vertical text, business document templates, and inkan image placement. Triggers on requests to create 日本語PDF, 請求書PDF, 領収書PDF, PDF帳票, 縦書きPDF.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Japanese Word documents (.docx) using python-docx with proper Japanese fonts, vertical writing (縦書き), ruby text (ふりがな), and business templates. Triggers on requests to create Word文書, 見積書docx, 請求書docx, 日本語Word, 縦書き文書, ビジネス文書Word.
Generate Japanese Excel files (.xlsx) using openpyxl with Japanese fonts, currency formatting (¥), Japanese era calendar (和暦), tax calculation, and business templates. Triggers on requests to create Excel帳票, 見積書Excel, 請求書xlsx, 勤怠管理表, 日本語スプレッドシート.
16:9スライドのワイヤーフレームをHTMLで作るときに使う。表紙・目次・中見出し・会社概要・社長挨拶・ミッション・メンバー紹介・サービス紹介・課題提起・組織図・フロー・料金・導入企業実績・お客様の声・メディア掲載・よくある質問・お問い合わせの17カテゴリ249種のレイアウト型を持つ。「スライドのワイヤーを作って」「表紙のレイアウト案がほしい」「目次ページの構成を」「会社概要スライドを」などの依頼で必ず使うこと。複数の型をつないで1本のデッキに組む手順（fキーでの全画面プレゼン、PDF書き出し、崩れの検査）も持つ。明示的に「スキル」と言われなくても、プレゼン資料・会社紹介資料・サービス紹介資料のページ構成をHTMLで組む場面では積極的に発火させる。
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Generate optimized Apple App Store metadata recommendations with ASO best practices. Use this skill when analyzing app listings, optimizing metadata (title, subtitle, description, keywords), performing competitive analysis, or validating App Store listing requirements. Triggers on queries about App Store optimization, metadata review, or screenshot strategy.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track App Store chart rank changes, find top gainers and losers, detect breakout apps entering the top 100, or identify apps dropping out of charts. Also use when the user mentions "chart movers", "rank changes", "who's rising", "who's falling", "new chart entries", "top gainers", or "market shifts". For broader market overview, see market-pulse. For competitive keyword analysis, see competitor-analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Implement iOS authentication patterns including Sign in with Apple (ASAuthorizationAppleIDProvider, ASAuthorizationController, ASAuthorizationAppleIDCredential), credential state checking, identity token validation, ASWebAuthenticationSession for OAuth and third-party auth flows, ASAuthorizationPasswordProvider for AutoFill credential suggestions, and biometric authentication with LAContext. Use when implementing Sign in with Apple, handling Apple ID credentials, building OAuth login flows, integrating Password AutoFill, checking credential revocation state, or validating identity tokens server-side.
日本語の概要は準備中です。原文の説明を表示しています。
Writes in ASD-STE100 simplified technical English — short sentences, plain words, active voice. Use when the user wants terse technical prose, names this skill, or asks for STE100.
日本語の概要は準備中です。原文の説明を表示しています。
Cuts fluff and leads with what matters. Applies Parkinson's Law, Pareto, and Goodhart's Law so every word earns its place. Use when the user wants terse output, names this skill, or signals that responses are too padded.
日本語の概要は準備中です。原文の説明を表示しています。
Strips AI fingerprints from written text by enforcing banned vocabulary, forbidden sentence structures, and authentic prose patterns. Use when writing articles, documentation, social content, emails, or any text that should read as human-authored rather than AI-generated.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze an optional company talent, values, culture, or recruitment page and turn it into cover letter positioning guidance. Use when the user provides a company values URL/text, asks to match a cover letter to company culture, or wants talent-profile keywords connected to resume.md evidence. 한국어 요청도 포함합니다 - 인재상 분석, 기업 가치관, 회사 문화, 채용 홈페이지 분석, 기업 분석, 인재상에 맞춰서, 회사가 원하는 인재.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a job description, hiring post, or recruitment page for role requirements, evaluation criteria, keywords, risks, and resume or cover letter angles. Use when the user provides a JD URL/text, asks what a company is looking for, wants JD-resume gap analysis, or needs inputs for a tailored cover letter. 한국어 요청도 포함합니다 - 채용공고 분석, 공고 분석, JD 분석, 직무기술서 분석, 자격요건, 우대사항, 이 공고 뭘 원하는지, 공고랑 내 경력 비교.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when writing aggregation pipelines, grouping, joining collections, or optimizing slow MongoDB queries. Trigger words: 集計, aggregate, パイプライン, $group, $lookup, $match, 結合, グループ化, 遅いクエリ, explain.
Use this skill when implementing sign-in, sessions, authorization checks, or protecting routes and Server Actions. Trigger words: 認証, ログイン, サインイン, セッション, 認可, 権限チェック, Better Auth, Auth.js, 保護, ミドルウェア, getSession.
Use this skill when writing a pull request description, change summary, or release notes in Japanese for this project. Trigger words: PR 説明, プルリク, 変更サマリ, リリースノート, PR 文章, レビュー依頼, 日本語で説明, pull request.
Use this skill when starting a new session, opening this project for the first time, or when you need to recall the project's tech stack, hard rules, and which other skills exist. Trigger words: セッション開始, このプロジェクト, 全体像, どのスキル, 何から, getting started, overview.