1,200 件 ・ 関連度順
概要と使いどころ
When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare for App Store review and prevent rejections. Covers App Store review guidelines, app rejection reasons, PrivacyInfo.xcprivacy privacy manifest requirements, required API reason codes, in-app purchase IAP and StoreKit rules, App Store Guidelines compliance, ATT App Tracking Transparency, EU DMA Digital Markets Act, HIG compliance checklist, app submission preparation, review preparation, metadata requirements, entitlements, widgets, and Live Activities review rules. Use when preparing for App Store submission, fixing rejection reasons, auditing privacy manifests, implementing ATT consent flow, configuring StoreKit IAP, or checking HIG compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive code review guidelines for iOS/Swift covering architecture, performance, security, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Create a company-specific job application package from a JD, resume.md, cover letter drafts, HR review, and optional company values input. Use when the user wants 지원 패키지, submission checklist, application folder structure, final answer snippets, email draft support, or safe pre-submission preparation without automatic final submission.
日本語の概要は準備中です。原文の説明を表示しています。
Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code. Use when reviewing code that touches user data, PII, or access control.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
日本語の概要は準備中です。原文の説明を表示しています。
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
日本語の概要は準備中です。原文の説明を表示しています。
「これから組織として生成 AI 導入を検討する委員会で何を議論すべきか」 「AI 利用ガイドライン策定の優先順位を決めたい」「執行部に上程する導入検討資料を作りたい」 「自学の AI 導入成熟度はどの段階か診断したい」「学長説明用 1 ページ要旨を作りたい」 場面で使う、大学組織としての AI 導入検討支援スキル。 3 カテゴリ × 2 ステップ × 2 主体のチェックリストと 5 段階成熟度モデルで合意形成を支援する。
「大学広報としてプレスリリースを生成 AI で効率化したい」「学長メッセージや挨拶文の原案を作りたい」 「オープンキャンパス告知の SNS 投稿を複数パターン生成したい」「同窓会報の原稿を AI で下書きたい」 場面で使う広報職員向けスキル。広報文面に求められる 7 点チェックと大学特有の品位を構造化し、 AI 下書きから配信承認までのフローを標準化する。
アプリを公開・リリースする前のセキュリティ/運用監査。「公開して」「リリースして」「本番に出したい」「ローンチしたい」「URLをみんなに共有したい」「これって公開して大丈夫？」といった依頼・質問があったら、デプロイ作業に入る前に必ずこのスキルを実行する。社外・不特定多数がアクセスできる状態にする変更（公開設定の変更、認証の撤廃、外部公開のデプロイ等）を頼まれた場合も同様。エンジニアが常駐しないチームでは、公開の重大さを判断できる人がいない前提で、リスクレベルの判定と「人間の専門家レビューが必要かどうか」の判断までこのスキルが担う。
Review the current changes for the CWE classes Peephole enforces, as a checklist including the absence-of-guard classes regexes cannot catch. Use when the user says /sec-review or asks for a security review of recent code before committing.
日本語の概要は準備中です。原文の説明を表示しています。
SEO + GEO (AI-search) + brand-entity desk (Busabase App-in-Skill) — wired to Google Search Console for a dashboard over search analytics and an agent-prepared SEO opportunities review queue, plus an AI-visibility tracker (are we cited in ChatGPT / Perplexity / Gemini / Claude / Copilot answers), a GEO content-optimization queue gated by geo-qa, and an entity / knowledge-panel readiness checklist. Use when the user invokes $kelly-seo or /kelly-seo, mentions SEO, Google Search Console, GSC, search analytics, search performance, queries, keywords, rankings, positions, impressions, clicks, CTR, striking-distance queries, title/meta rewrites, content briefs, internal links, SEO opportunities review, GEO, generative engine optimization, AI search, AI visibility, being cited by AI answer engines, ChatGPT/Perplexity/Gemini/Claude/Copilot citations, brand entity, knowledge panel, Wikidata, schema.org, or entity readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Short-drama and product-video development skill for planning drama projects through a bundled Busabase App-in-Skill UI, with each project linked to a specified HyperFrame project and each episode linked to a HyperFrame composition for final motion/video tuning. Use when the user asks to create, edit, organize, or review short-drama scripts, product explainer episodes, character consistency cards, series bibles, episode beat sheets, storyboard shots, HyperFrame project/composition links, production checklists, or a drama planning workbench.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-Entity Disclosure Tracker App-in-Skill — a Busabase review workspace that helps a compliance/IR team assemble and track a standardized disclosure package per financing vehicle (fund/SPV), across a generic onshore origination entity, an offshore fund-manager entity, and a listing/exchange venue. Use when the user invokes $kelly-disclosure-tracker or /kelly-disclosure-tracker, wants to review disclosure checklists, vehicle readiness, cross-entity reconciliation flags, or reviewer notes across multiple financing vehicles. Review workspace only — it never files anything or calls any external system.
日本語の概要は準備中です。原文の説明を表示しています。
Legal matter-strategy App-in-Skill (Busabase-backed) desk for new-case strategy, issue trees, evidence checklists, risk analysis, pleading outlines, and approval-gated drafting packs grounded in internal precedents. Use when the user invokes $kelly-legal-matter-strategy, mentions 案件策略, 办案辅助, 证据清单, 争议焦点, 文书生成辅助, litigation strategy, arbitration strategy, pleading outline, or wants a Busabase-backed desk where responsible lawyers review agent-prepared strategy before use.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a structured ransomware incident response playbook aligned with the CISA StopRansomware Guide and NIST Cybersecurity Framework. Covers preparation, detection, containment, eradication, recovery, and post-incident phases with actionable checklists. Activates for requests involving ransomware response planning, CISA compliance, incident response playbook creation, or ransomware preparedness assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous methodology for evaluating ML models on established benchmarks. Covers proper train/val/test splits, baseline verification from original papers, exact metric formula discrepancies, data-leak detection checklist, multi-seed robustness, and honest reporting templates. Use when claiming to beat published baselines, writing methods papers, or auditing existing results.
日本語の概要は準備中です。原文の説明を表示しています。
Generate the success criteria for a task or question, then review work against them. Given a task, goal, or open-ended question, decompose it into scenarios, evaluation perspectives, and fine-grained weighted YES/NO criteria using the Recursive Expansion Tree (RET) method; if work is supplied, score it criterion-by-criterion and surface what is missing or could be better. Use when asked to self-review or check your own work, judge whether a task is done well or completely, build a definition-of-done or completeness checklist, create an evaluation rubric or grading criteria, score or grade answers to a question, set up an LLM-as-judge rubric, or when the user mentions self-review, completeness check, success criteria, evaluation criteria, scoring rubric, Qworld, or the RET algorithm.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a change affects user-visible behavior at docs.chronote.gg and needs public documentation. Covers where docs live (apps/docs-site vs docs/), authoring checklist, yarn docs:check, and Algolia config. Trigger when the user mentions docs, release notes, what's-new, or user-facing PR changes.
日本語の概要は準備中です。原文の説明を表示しています。
Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
日本語の概要は準備中です。原文の説明を表示しています。
Create ADA accessibility compliance checklists. TRIGGERS - Use when user needs help with accessibility-compliance related tasks.
日本語の概要は準備中です。原文の説明を表示しています。