「ct」の検索結果

Classify every destructive/gated action an agent body can attempt (git, filesystem, network, shell, github) into block/approve/allow tiers, and audit whether the pre-tool and post-tool governance backing that classification is real: blocked actions proven zero-side-effect by a negative fixture, every denial backed by a receipt and a transcript event, every block-tier denial paired with a safe alternative, and no unmanaged or same-UID body ever marked "contained." Use when building or reviewing Agent Harbor's C5 governance gate (destructive git blocker, approval request/result, denial receipts), gating a new tool surface before it can run destructive commands, or auditing whether an existing "destructive-action blocked" claim actually has evidence behind it. NOT for proving an existing sandbox boundary actually contains an adversary once an action is isolated (use sandboxed-adversarial-test-harness), deciding where in a DAG to place a human review node or designing the approval UX itself (use human-gate-designer), or designing the general work-receipt schema across an entire agent task (use agent-work-receipt-designer).

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

AIエージェントの危険なコマンドを実行前に確認し、ファイル編集を指定ディレクトリ内に制限します。単独または併用のモードで、本番作業や自律実行時の操作を管理します。

• 本番作業で危険なコマンドを確認
• 特定ディレクトリだけ編集したいとき
• 自律実行時に保護を併用したいとき

React 18/19の画面部品を実装・レビューする際に、状態管理やデータ取得、フォーム、読み込み・エラー表示、アクセシビリティの設計を支えるスキル。

• Reactの画面部品をレビューしたいとき
• 共有する状態の置き場所を決めたいとき
• フォームとデータ取得の設計

ReactやNext.jsの画面を実装・レビューするために、部品の組み立て、状態管理、データ取得、表示速度、フォームや操作性の改善パターンを示すスキル。

• Reactの部品を再利用したいとき
• 状態管理とデータ取得の見直し
• 長い一覧の表示を軽くしたいとき

Etsy product detail scraper: given an Etsy listing URL, returns full product detail including listingId, title, priceCurrent, priceOriginal, currency, images (all), description, shopName, shopUrl, rating, reviewCount, favorites, inCartCount, variations (with per-option price ranges), highlights, listedDate, relatedTags. Use when user mentions Etsy product, Etsy listing detail, Etsy item info, Etsy product page, scrape Etsy listing, extract Etsy product data, Etsy price and variations, Etsy product images, Etsy product description, Etsy shop from listing, Etsy favorites count, Etsy sale count, Etsy variations extraction, Etsy listing metadata, single Etsy product scrape, bulk enrich Etsy listing URLs, Etsy product details export. Also applies to competitor product monitoring, price and variation tracking on a specific listing, favorites/wishlist popularity tracking, description mining for SEO analysis, and any per-listing enrichment task.

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

Import contacts (address book entries) into TRES Finance from a CSV or XLSX file. Use this skill whenever the user wants to import, upload, or bulk-add contacts, address labels, or address book entries into TRES — whether from a file they filled in after using the export-3rd-party-contacts skill, or from any CSV/XLSX that maps addresses to names. Trigger phrases include: 'import contacts', 'upload contacts', 'add contacts from file', 'import address book', 'load contacts into TRES', 'bulk label addresses', 'import the contacts file', 'upload the filled contacts sheet'. Also trigger when the user says something like 'I filled in the contacts file, now import it' or 'here is my contacts spreadsheet, please upload it to TRES'. Do NOT trigger for exporting or extracting unidentified addresses — that's the export-3rd-party-contacts skill. Do NOT trigger for viewing or searching the existing address book.

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

Analyze an organization's sub-transaction patterns in TRES Finance, identify groups of repetitive transactions, and propose data-driven rollup rules that consolidate them into one aggregated entry per interval (daily or monthly) for cleaner ERP integration. Also lists and deletes rollup rules. Trigger this skill whenever the user asks about rollup rules, transaction aggregation, consolidating transactions, reducing transaction noise, rolling up gas fees, rolling up staking rewards, rolling up micro-transactions, or collapsing many small ledger entries into fewer summary entries. Also trigger on "create a rollup rule", "suggest rollup rules", "what should I roll up", "show my rollup rules", "delete a rollup rule", "aggregate transactions", "too many transactions", "reduce transaction count", "roll up fees", "daily rollup", "monthly rollup". If a wallet has too many transactions, high-frequency activity, or noisy ledger entries, proactively suggest rollup rules. For computing the EXACT impact of a single already-specified rule or reviewing submitted/pending rules, use the tres-rollup-review skill instead.

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

Use when the user wants to orchestrate defect image generation with NVIDIA Cosmos AnomalyGen (Cosmos-Predict2-derived) on OSMO for PCBA, metal surface, and glass inspection. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint, cosmos defect generation, cosmos-predict2 defect, cosmos-anomalygen, cosmos predict2 finetune.

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

Interactive discovery + implementation workflow that gathers requirements through picker-based questions (intent, scope, constraints, preferences), scans the codebase for what it can already infer, then writes an AWS architectural scaffold and implementation directly into the project. Use when the user wants to build a new app, scaffold a project, or expand/refactor an existing one on AWS — anything that calls for a structured discovery flow followed by code changes, not a one-off lookup. Do not use for: factual lookups about AWS Activate / programs / credits, requests for a single copy-paste prompt, non-AWS architectural work, architecture advice/recommendations without code changes (see architect-for-startups), a new idea centered on an AI agent — runtime selection, agentic architecture, or an agent POC (see agent-advisor), or migrating an existing GCP/Azure/Heroku workload or an LLM SDK rewrite (see gcp-to-aws / azure-to-aws / heroku-to-aws / llm-to-bedrock).

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

Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida Kenji (beautiful structure, time-axis tricks), Miki Satoshi (small-material notebook, theme emerges later), Sono Sion, Omiya Ellie (dialogue from inner monologue), Kakei Masaya ("if + moreover"), Fukuda Yuichi (character = actor + flaw, audience as tsukkomi), Yokohama Satoko, Takahashi Izumi ("pain"), Yukisada Isao (situation-born originals); plus Arai Haruhiko (IP adaptation, "write what you're ashamed of"). Neighbours; sw-korean-french-screenwriting, ozu-screenplay-style. Use when writing an original Japanese-style script or TV drama, working from small material and fragments, choosing between structure-first and character-first methods, building a Japanese 企画書, designing comedy tsukkomi systems, or when Hollywood models feel wrong for a quiet, daily-life, non-goal-driven story.

Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's tools (Jira, Linear, Notion, Figma, GitHub) with AI agents via MCP and CLI. A temporal map of phases, lock points, handoff specs, gate definitions, and QA verification gates. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative direction, design-development handoff, QA gate, agent-driven QA, and when a creative-direction project is starting, mid-flight with broken cadence, or integrating AI agents into PM workflow. Does NOT fire for project scoping (use `creative-brief`), aesthetic direction (use `creative-direction`), or general project management without a creative-direction throughline.

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

Recherche, cartographie et analyse des thèses de doctorat françaises via theses.fr (API ABES) et TEL (HAL). Spécialisée droit avec filtrage par sous-disciplines juridiques. Ouverte sur d'autres domaines universitaires. Capacités : (1) recherche multi-critères — sujet, directeur, jury, établissement, école doctorale, période, statut soutenue/en préparation, discipline ; (2) cartographie académique — qui dirige sur quel sujet, qui siège dans quels jurys, réseaux de co-direction, écoles doctorales productives ; (3) analyses temporelles — évolution d'un sujet, détection de saturation, calendrier des soutenances à venir ; (4) filtrage sous-discipline juridique — droit privé, public, social, affaires, international, etc. Déclencher dès que l'utilisateur mentionne thèse, doctorat, directeur de thèse, jury de thèse, école doctorale, soutenance, doctorant, ou demande une analyse d'écosystème doctoral. Pour articles ou ouvrages de doctrine, utiliser plutôt recherche-doctrine.

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

Writes the character-performance layer of a video prompt as behavior under pressure, not displayed emotion — objective, obstacle, tactics, beats, subtext, listening, body/status/proxemics, and mandatory eye life. Produces a reusable 150–220-word acting master profile per character plus a per-scene rewrite of it, and a locked voice prompt. Use whenever a prompt needs acting, performance, or emotion direction; whenever characters read wooden, dead-eyed, or 'AI'; whenever a character must stay themselves across many shots; or when the user asks for character behavior, mannerisms, tics, a gait, or how someone reacts. Pairs with higgsfield-facs (muscle-level AU codes) and higgsfield-seedance (the prompt the paragraph goes into).

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

Build a single-product deep-dive showcase page as a self-contained HTML file. Triggers on: "build a product showcase page", "deep dive landing page for [product]", "create a product spotlight page", "product feature page", "single product page", "detailed page about [product]", "build a page showing everything about [product]", "create a long-form product page", "build a sales page for [product]", "product deep dive page", "make a feature breakdown page for [product]".

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

Documentation-first project planning that produces implementation-ready blueprints and single-shot coding agent prompts. Generates 4 interconnected docs — SPECIFICATION.md, IMPLEMENTATION.md, TASKS.md, BRANDING.md — plus a self-contained PROMPT.md for autonomous execution by any coding agent. Includes interactive tech stack selection, design pattern recommendations, and architecture decisions with trade-off analysis. Trigger when user wants to: plan a project, create specs, architect a system, break work into tasks, choose a tech stack, get design pattern advice, generate a coding agent prompt, or do documentation-first development. Phrases: "plan my project", "spec this out", "architect", "help me plan", "what stack should I use", "generate a prompt", "break this into tasks", "project docs", "I want to build X".

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

Enforce architectural rules when generating or modifying code, and validate proposed designs before approval (design mode). Defaults to clean architecture; supports any architecture style via the architecture-refiner. Validates layer responsibilities, dependency direction, and structural constraints using the loaded architecture rules. Use when generating code, reviewing architecture, creating new files, or when the user mentions 'architecture', 'layers', 'structure', 'dependency rules', 'hexagonal architecture', 'ports and adapters', 'modular monolith', or 'onion architecture'. Also use when reviewing generated code for structural compliance.

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

When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.

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

🇺🇸 Reddit Marketing & Growth Playbook 2026 — The complete Reddit operations SOP for AI/SaaS founders. Covers account warming (Karma 0→500 in 20 days), shadow ban prevention, multi-account matrix via fingerprint browsers, subreddit selection across 10K+ communities, content templates (90/10 rule), Product Hunt × Reddit flywheel, AMA strategy. Why this matters NOW: Reddit content is 40.11% of ChatGPT/Claude training data — the highest-weighted English UGC source. Battle-tested by AFFiNE Reddit campaigns generating 3-4万有效曝光 with 5-8% GitHub Star conversion, plus 7 case studies (Adobe 3x conversion, Base44 $80M AMA, SenseNova-U1 multi-sub launch, Starterstory 0→3K users). 🇨🇳 Reddit 运营增长实战手册 — AI/SaaS 出海 founder 的 Reddit 完整 SOP。覆盖账号体系(20天养号 Karma 0→500)、影子封禁防御、指纹浏览器矩阵、10万+ subreddits 筛选、内容模板(90/10 法则)、Product Hunt × Reddit 飞轮、AMA 打法。**为什么现在做:Reddit 内容占 ChatGPT/Claude 训练数据 40.11%,是最高权重的英文 UGC 来源**。基于 AFFiNE Reddit 实战 3-4 万曝光 + 5-8% Star 转化,含 7 个完整案例(Adobe 3x 转化、Base44 $80M AMA、SenseNova-U1 多社区联动、Starterstory 0→3K 用户冷启动)。 🇯🇵 Reddit マーケティング＆グロースプレイブック — AI/SaaS創業者向けの完全なReddit運用SOP。アカウント育成（20日でKarma 0→500）、シャドウBAN防止、フィンガープリントブラウザマトリックス、サブレディット選定、コンテンツテンプレート（90/10ルール）、Product Hunt × Redditフライホイール、AMA戦略をカバー。**重要な理由：Reddit コンテンツは ChatGPT/Claude のトレーニングデータの40.11%を占める英語 UGC 最大の情報源**。AFFiNE Redditキャンペーン3-4万インプレッション＋5-8% GitHubスター変換で実証。7つの実例（Adobe 3倍変換、Base44 $80M AMA、SenseNova-U1、Starterstory 0→3Kユーザー）。 🇰🇷 Reddit 마케팅 & 그로스 플레이북 — AI/SaaS 창업자를 위한 완전한 Reddit 운영 SOP. 계정 워밍업(20일 Karma 0→500), Shadow Ban 방지, 핑거프린트 브라우저 매트릭스, 서브레딧 선정, 콘텐츠 템플릿(90/10 룰), Product Hunt × Reddit 플라이휠, AMA 전략을 다룹니다. **지금 해야 하는 이유: Reddit 콘텐츠는 ChatGPT/Claude 학습 데이터의 40.11%를 차지하는 최대 영어 UGC 소스**. AFFiNE Reddit 캠페인 3-4만 노출 + 5-8% GitHub Star 전환으로 검증. 7가지 사례 연구(Adobe 3배 전환, Base44 $80M AMA, SenseNova-U1, Starterstory 0→3K 사용자). Triggers: "reddit marketing" | "reddit growth" | "reddit ads" | "reddit advertising" | "reddit strategy" | "reddit promotion" | "subreddit marketing" | "reddit playbook" | "reddit SOP" | "reddit shadow ban" | "shadow ban prevention" | "reddit karma" | "reddit AMA" | "reddit product launch" | "reddit AI training data" | "reddit GEO" | "AFFiNE reddit case" | "Base44 AMA" | "SenseNova Reddit" | "subreddit selection" | "r/SaaS posting" | "r/MachineLearning self-promotion" | "fingerprint browser matrix" | "AdsPower reddit" | "reddit account farming" | "reddit 90/10 rule" | "reddit content strategy" | "reddit indie founder" | "reddit cold start" | "Reddit 运营" | "Reddit 营销" | "Reddit 防封" | "Reddit 矩阵号" | "Reddit 出海" | "Reddit 引流" | "Reddit 冷启动" | "影子封禁" | "Reddit Karma" | "Reddit 养号" | "Reddit AMA" | "Reddit マーケティング" | "Reddit グロース" | "Reddit 마케팅" | "Reddit 그로스"

🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles. **Defaults to dev tools / OSS / B2B SaaS; for 2C products (education, apps, games) the launch channels & metrics differ — see gingiris-seo-geo/references/2c-adaptation.md.** 🇨🇳 AI 产品 / SaaS 企业出海完整 SOP — 从竞品调研到 Launch 到商业化的全流程操作手册。覆盖 Phase 0-5（市场验证、定位、前100用户、用户访谈、Beta转增长）+ 开源发布、Product Hunt、Reddit、SEO/GEO、转化与组织原则。**默认面向开发者工具/开源/B2B SaaS；2C 产品（教育/应用/游戏）的启动渠道与指标不同，见 gingiris-seo-geo/references/2c-adaptation.md。** 🇯🇵 AI製品/SaaS海外展開フルサイクルSOP — 競合調査からローンチ、マネタイズまで。Phase 0-5（市場検証、ポジショニング、最初の100ユーザー、ユーザーインタビュー、ベータから成長）＋オープンソース、Product Hunt、Reddit、SEO/GEO、コンバージョン、組織原則。 🇰🇷 AI 제품/SaaS 글로벌 진출 완전 SOP — 경쟁사 조사부터 런칭, 수익화까지 전 주기 플레이북. Phase 0-5(시장 검증, 포지셔닝, 첫 100명 사용자, 사용자 인터뷰, 베타→성장) + 오픈소스 런칭, Product Hunt, Reddit, SEO/GEO, 전환, 조직 원칙. Triggers: "go global" | "出海" | "overseas expansion" | "GTM" | "cold start" | "launch strategy" | "international expansion" | "海外增长" | "出海SOP" | "product launch overseas" | "海外进出" | "グローバル展開" | "글로벌 진출" | "go-to-market" | "出海打法"

Build and navigate DSP (Data Structure Protocol) — graph-based long-term structural memory of codebases for LLM agents. Stores entities (modules, functions), their dependencies (imports), public API (shared/exports), and reasons for every connection. Use when: (1) project has a .dsp/ directory, (2) user asks to set up DSP or bootstrap project structure, (3) creating/modifying/deleting code files in a DSP-tracked project, (4) navigating project structure, understanding dependencies, or finding modules, (5) user mentions DSP, dsp-cli, .dsp, or structure mapping.

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

Use whenever the user wants to find, rank, or shortlist directories and listing sites where they can submit an AI product — an AI tool, AI app, AI agent, or agent skill / plugin — to get backlinks, referral traffic, and discovery. Triggers on "where can I list my AI tool", "directories to submit my AI agent", "agent-skills directories", "best AI tool directories for backlinks", "where do I get my GPT/Claude app discovered", or "pull submission details for these AI-directory domains", even when described indirectly (we built an AI agent, where do we get it in front of people). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-mcp-directories for MCP-server listings specifically, and to find-product-directories for general SaaS/software/app launches with no AI angle. Skip finding an AI consultancy/agency to hire (use find-ai-consultancy), comparing AI products ("ChatGPT vs Claude"), building an AI tool (do-the-work), and AI link-building *services*.

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

Audits and scores Claude Projects using a six-dimension Scorecard with anchored 1-5 rubrics and detects seven structural anti-patterns. When global layer info is provided, adds cross-layer alignment findings. Use when user says "audit my project," "review my custom instructions," "score my project," "evaluate my Claude project," "improve my system prompt," "what's wrong with my project," "why is my project underperforming." Also trigger on symptom-phrased: "my project doesn't work right," "Claude is inconsistent in my project," "my Project used to work and now doesn't." Also use when the user pastes Custom Instructions asking why output is poor or generic. Do NOT use when the user's primary request is a global-layer audit (use rootnode-global-audit if available), single-prompt evaluation (use rootnode-prompt-validation if available), or Memory-only optimization (use rootnode-memory-optimization if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

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

Angular 18-21 project structure, standalone components vs NgModule, control flow (@if/@for/@switch + *ngIf/*ngFor legacy), decorators, dependency injection (inject() function), lifecycle hooks, pipes, Angular Universal SSR pointer. Use this skill to: - Detect project style (standalone vs NgModule) and apply matching patterns. - Pick correct decorators and DI approach. - Use modern control flow (@if/@for/@switch) in Angular 17+ projects. - Apply `inject()` function over constructor injection where appropriate. - Wire bootstrap correctly (bootstrapApplication for standalone, AppModule for legacy). Do NOT use this skill for: - State management (see angular-state-and-rx). - Routing (see angular-routing). - Forms (see angular-forms). - Testing (see angular-testing).

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

AI-DLC v3（AI-Driven Development Lifecycle）のオーケストレーター。 define / develop / release / reflect の 4 フェーズコマンドと status / doctor の 補助コマンド、連続実行ラッパ express、旧名エイリアス（inception / construction / operations / retrospective）を統一的にルーティングする。 define / develop（normal / risky 含む）/ release / reflect の各フェーズフローと status / doctor の補助コマンドを実装済み（doctor は shallow scope）。