「sca」の検索結果

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

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

Builds security testing pipelines for SAST, DAST, SCA, secrets, containers. Use when wiring scanners into CI or regression gates.

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

Sizes models and token budgets using Kaplan/Chinchilla scaling laws. Use when reasoning about compute-optimal N and D, tokens-per-parameter ratios, or over-training tradeoffs.

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

Audit a .glb or .gltf and make it small, correct, and fast to load in a browser, with a measured before/after report. Use when a model is "too big" or "slow to load", when the user asks to "optimize this GLB", "compress this glTF", or "export for web", or when they mention Draco, meshopt, gltfpack, KTX2, Basis, texture VRAM, draw calls, or a Blender / CAD / photogrammetry / Pascal export headed for Three.js, React Three Fiber (drei useGLTF), Babylon.js, or model-viewer. Covers inspection, spec validation, geometry and texture compression, scene-graph cleanup, and the correctness checks (metres, Y-up, node names, animations, PBR fidelity, alpha modes, vertex colors) that must not regress. Not for editing or modelling geometry, authoring or laying out a scene, generating 3D from text or images, converting from FBX/OBJ/CAD, or debugging a runtime frame rate that has nothing to do with asset size.

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

Scanning and eradicating supply-chain malware (Shai-Hulud/S1ngularity npm/PyPI worms): IoC scan, OS/IDE persistence, safe credential rotation. Not for SAST (Sentinel) or skill/MCP audit (Chain).

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

Analyse text complexity across quantitative, qualitative, and reader-task dimensions with scaffolding recommendations. Use when selecting texts, assessing readability, or planning reading support.

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

Provide graduated assistance from abstract conceptual nudge to concrete procedural step, with reflection required before each escalation. Teaches help-seeking as a skill and prevents direct-answer shortcuts.

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

Generate a scaffolded sequence of practice problems with graduated difficulty and strategic variability. Use when creating worksheets, homework sets, or independent practice materials.

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

Scaffold an emergent project from observed children's interests using Reggio-inspired approaches. Use when following children's fascinations into deeper inquiry in early years or primary settings.

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

Generate scaffolds that gradually increase student choice, voice, and ownership within a learning task. Use when students depend heavily on teacher direction and need to develop autonomy.

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

Generate tiered sentence frames for academic tasks that scaffold language production across proficiency levels. Use when EAL students need structured language support for classroom discourse.

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

When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.

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

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

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

Root cause analysis for bugs and unexpected behavior. Traces errors through code, uses structured reasoning, and hands off to fix when cause is found. Core of the debug↔fix mesh. When the diagnosed cause is a memory leak in a long-running process, escalates to perf for cost-impact framing (leaks drive OOM-restart → cold-start → autoscaler spend, often 20-40% bill inflation).

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

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

🇺🇸 ASO & Mobile App Growth Playbook 2026 — Complete App Store Optimization guide. ASO keyword ranking, App Store & Google Play listing optimization, app cold start, UGC creator operations, TikTok/Instagram/YouTube Shorts marketing, AI-matrix content scaling, mobile user acquisition. 🇨🇳 ASO 增长与 App 冷启动权威指南 — 从应用商店优化到 UGC 运营、多平台内容策略、AI 辅助内容创作的完整实操手册。 🇯🇵 ASO＆アプリコールドスタート成長ガイド — App Store最適化からUGC運営、マルチプラットフォーム戦略、AIマトリックスまで。 🇰🇷 ASO 및 앱 콜드 스타트 성장 플레이북 — 앱스토어 최적화부터 UGC 운영, 멀티플랫폼 전략, AI 매트릭스까지. Triggers: "ASO" | "App Store Optimization" | "ASO keywords" | "App Store ranking" | "Google Play optimization" | "app cold start" | "app launch" | "mobile app growth" | "user acquisition" | "UA" | "UGC creator" | "TikTok marketing" | "Instagram Reels" | "YouTube Shorts" | "creator matrix" | "app growth" | "应用商店优化" | "App冷启动" | "UGC运营" | "矩阵号"

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. What's inside: • Pre-launch readiness checklist (6 conditions that must be true before starting) • 6-step community setup SOP (platform selection → rules → admin standards → monitoring → wiki → metrics) • Ambassador recruitment system (A+B qualification, application form design, scoring rubric) • 4-tier progression system (Bronze → Silver → Gold → Platinum with point thresholds) • 5-pillar incentive framework (Product quality → Beta access → Founder access → KOL path → Full engagement) • Churn early-warning system + retention playbook • Event operations SOP (6 event types × full lifecycle) • Health metrics dashboard (6 core KPIs + 5 ambassador-specific indicators) • Governance & risk control (behavior code, escalation matrix) • Real templates: recruitment post, welcome email, annual calendar 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

🇺🇸 UGC Matrix Growth Playbook — Scale user-generated content with AI + real creators. Complete SOP for UGC flywheel, creator recruitment, incentive design, multi-platform publishing. Proven at CPM $0.5, $10M ARR in 60 days with 70M impressions. Includes a full anonymized client case study. 🇨🇳 UGC矩阵号增长实操手册 — AI+真人创作者规模化用户生成内容。完整的UGC飞轮SOP、创作者招募、激励机制设计、多平台分发策略。已验证CPM $0.5，60天$1000万ARR，7000万曝光。含完整客户案例拆解（已脱敏）。 🇯🇵 UGCマトリックス成長プレイブック — AI＋リアルクリエイターでUGCをスケール。フライホイールSOP、クリエイター採用、インセンティブ設計、マルチプラットフォーム配信。CPM $0.5、60日で$10M ARR、7000万インプレッション実証済み。匿名化クライアント事例付き。 🇰🇷 UGC 매트릭스 성장 플레이북 — AI + 실제 크리에이터로 UGC 스케일링. 플라이휠 SOP, 크리에이터 모집, 인센티브 설계, 멀티플랫폼 배포. CPM $0.5, 60일 $10M ARR, 7000만 노출 검증 완료. 익명화된 클라이언트 사례 포함. Triggers: "UGC" | "UGC matrix" | "user generated content" | "creator program" | "creator economy" | "AI UGC" | "matrix accounts" | "矩阵号" | "UGC运营" | "创作者招募" | "UGC Program" | "content matrix" | "TikTok UGC" | "Instagram UGC"

Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers (=========), class organization, naming conventions (services, queue jobs, records, events, enums), defineRules() and validation, beforePrepare() and addSelect(), MemoizableArray, DateTimeHelper vs Carbon, strict_types/declare(strict_types=1), short nullable notation (?string), typed properties, void returns, control flow (early returns, match over switch), CP Twig template conventions, form macros, translations (Craft::t), ECS/PHPStan config, scaffolding commands, and the verification checklist.

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

Use when the user wants a cited, structured read of local documents and project knowledge. Triggers on: "analyze these docs", "scan my project for context", "read the docs folder", "summarize what's in .beagle/concepts/", "extract context from docs/", "what's in this folder", "go read everything in X and tell me what's there". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), web research (use web-research), LLM-as-judge evaluation (use llm-judge), or document editing (use humanize-beagle). Produces a written scan plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.

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

Reference for the diagnostics pipeline (ripdpi-monitor-engine/ripdpi-diagnostics-* and core/diagnostics). Use when changing ScanRequest/ScanReport, ProbeTask families, probe scheduling, the catalog, or the wire contract. Techniques: desync-engine.

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

getterの濫用を防ぐための命名規約スキル。ドメインモデルでgetterが必要な場合（永続化、JSON変換など）に `breachEncapsulationOf` プレフィックスを付与することで、カプセル化を破っていることを明示する。 これにより、Tell Don't Ask原則の違反を未然に防ぎ、getterの意図しない使用を抑制する。 コードレビュー、新規実装、リファクタリング時にgetter設計が必要な場合に使用。 対象言語: Java, Kotlin, Scala, TypeScript, Python, Go, Rust。 トリガー：「getterの命名規約」「カプセル化を破るgetter」「永続化用のgetter」 「breachEncapsulation」「getterを作りたいが濫用を防ぎたい」といったgetter命名関連リクエストで起動。

デメテルの法則（最小知識の原則）に基づくコードレビューと設計支援。オブジェクトの連鎖呼び出し （Train Wreck）を検出し、直接の友人とのみ会話する設計へ変換する。結合度の低減と 変更容易性の向上を促進する。コードレビュー、新規実装、リファクタリング時に オブジェクト間の結合が深い場合に使用。 対象言語: Java, Kotlin, Scala, TypeScript, Python, Ruby, Go, Rust。 トリガー：「デメテルの法則」「連鎖呼び出しを減らしたい」「Train Wreckを直して」 「結合度を下げたい」「ドット連鎖が多い」「最小知識の原則」「Law of Demeter」 といったオブジェクト間結合関連リクエストで起動。

Domain PrimitivesとAlways-Valid Domain Modelの設計原則に基づき、ドメインモデルの型安全性と不変条件を 保証する設計・実装を支援する。プリミティブ型の濫用を防ぎ、構築時検証・不変性・自己完結性を備えた ドメイン固有の型を設計する。コードレビュー、新規実装、リファクタリング時に使用。 対象言語: Rust, TypeScript, Java。他の言語（Kotlin, Scala, Go, Python等）にも応用可能。 トリガー：「ドメインプリミティブを作りたい」「Always-Validなモデルを設計」「プリミティブ型をラップしたい」 「構築時に検証したい」「無効な状態を型で防ぎたい」「Smart Constructorパターン」等のリクエストで起動。