'checklist' 검색 결과

Use when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and Google stop double-counting"; builds and fixes the measurement plumbing — conversion-event firing, UTM hygiene, cross-platform dedup rules, attribution-window alignment, and offline/iOS-ATT modeled-gap flags — as a pre-flight checklist plus a UTM/event-spec builder. Not for scoring R1/R2 — that is a scored veto in ad-account-auditor; not for account structure — use campaign-architect. 付费广告转化追踪QA/UTM规范/跨平台去重

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when planning or building a SaaS MVP from scratch. Provides a structured roadmap covering tech stack, architecture, auth, payments, and launch 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a...

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate recommender system quality for the CSX4207 Vinyl Record Store. Use whenever you must compute or report recommender metrics (Precision@k, Recall@k, HitRate@k, MRR, MAP@k, NDCG@k, coverage, diversity, novelty, serendipity, personalization), design an evaluation protocol/split, run a baseline comparison, or write the evaluation section of a course deliverable. Covers formulas, JavaScript reference implementations, and the reporting checklist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematic design quality evaluation. Hierarchy, type, color, space, craft, system. Use when evaluating whether a design is ready to ship, running quality audits, or setting quality standards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive security auditing, diff analysis, defensive checklists, and vulnerability testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.