4,327 件 ・ 関連度順
概要と使いどころ
Use when working with Unreal's Gameplay Ability System - when GAS is worth it, where the AbilitySystemComponent lives and how it is initialised on server and client, AttributeSets with correct clamping and replication, GameplayEffects and execution calculations as data, abilities with commit/end, gameplay tags, prediction, and testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a case needs data, a user/role, or a third-party dependency - seeding through the product first, test credentials, namespacing on shared environments, and stubbing an external HTTP service by hand
日本語の概要は準備中です。原文の説明を表示しています。
Use when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approval
日本語の概要は準備中です。原文の説明を表示しています。
Use when you add or change an endpoint, an auth check, a query by id, an outbound call to a user-supplied URL, file handling, or anything touching credentials — the OWASP API Top 10 (2023) as concrete Go and Java checks
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to initialize a repo, create AGENTS.md, generate contributor guidelines, or set up agent-oriented documentation for a codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze startups with Paul Graham mindset (pressure, founder-market fit, brutal validation), Dan Koe discipline (monetization, offer, distribution, sales), and Seth Godin principles (differentiation, narrative, smallest viable audience). Triggers on startup idea, business validation, MVP, first customers, revenue model, GTM, product-market fit, "I have an idea".
日本語の概要は準備中です。原文の説明を表示しています。
Revenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling"), pricing/monetization ("how should I price this"), checkout/forms ("dropdowns kill conversion", "annotated checkout"), dashboards/data viz ("cognitive load", "KPI shortlists"), positioning/ICP/go-to-market, feature scope, A/B-test rigor, or AI-era differentiation — or asks for the behavioral-science mechanism behind a design choice. Also use when another skill needs the principle or evidence behind a conversion/retention/pricing/checkout move. Never apply to gambling, betting, or casino products.
日本語の概要は準備中です。原文の説明を表示しています。
Write and edit Brazilian Portuguese prose with natural rhythm and the author's voice while preserving facts, meaning, and intent. Use for PT-BR requests to humanizar, tirar cara de IA, remover AI slop, reescrever com voz, simplify language, or write a post, email, article, or bio. Also use the author's notes or transcripts and ask targeted questions when essential facts are missing. For English text, use the bundled human-ai skill.
日本語の概要は準備中です。原文の説明を表示しています。
Compress PDF files with ComPDF while balancing file size and readable visual quality. Use for PDF optimization, resolution control, compression strategies, and removal of non-essential document content.
日本語の概要は準備中です。原文の説明を表示しています。
Tmux skill for running background tasks. Use this skill when: 1. Before any tasks that can potentially run for more than 2 minutes (e.g.: package install, many tests, model training) 2. Before any tasks that are expected to run indefinitely in background (e.g.: web servers, port forwarding) 3. Bash tool reports `timeout after 120000ms` 4. User request to run tasks in background
日本語の概要は準備中です。原文の説明を表示しています。
Audit a website against the Forter Agentic Readiness Guide. Loads the 25 weighted rubrics in `audit/`, probes the target site (and optional source code), scores each guideline Pass/Partial/Fail/N/A with sub-check granularity, and produces a prioritized fix report. Use when a user asks "score my site against the agentic readiness guide", "audit https://… for agent readiness", or "what do I need to fix to be agent-ready".
日本語の概要は準備中です。原文の説明を表示しています。
The judgment layer: when AutoCode acts on its own and when it stops and asks, and how it speaks about decisions and money. iLang v5.0: perception sets the 11 dimensions, the frozen reference function f_v5 sets the mode, the user sees one plain line. Runs before every consequential action.
日本語の概要は準備中です。原文の説明を表示しています。
Start a new prospect's intake, with or without their files in hand — a request naming a new prospect and attaching no documents is a normal starting point, because Step 1 searches the connected tools or asks the advisor to upload. Cleans and normalizes their account files (statements, exports, screenshots) into a consolidated view, then hands back a plain-English prospect summary, a detailed analyst handoff the full proposal gets built from, and a friendly "what to expect" memo, offered as a Gmail draft on approval. Does not produce the proposal, recommend an allocation, or quote fees. Triggers on "prospect intake", "/prospect-intake", "new prospect intake", "clean up [prospect]'s statements", "process [prospect]'s files", "what to expect note for [prospect]" — and on how an advisor raises a new prospect before any file exists: "I met with a potential client/customer", "[name] is interested in becoming a client", "I have a new prospect", "how should I proceed with [name]".
日本語の概要は準備中です。原文の説明を表示しています。
The methods a financial-ML result has to survive before it is evidence — purged cross-validation with an embargo, triple-barrier labelling, sample uniqueness under overlapping labels, fractional differentiation, meta-labelling, and multiple-testing correction. Written because the invariants were required of quant-researcher and nothing in the project explained how to satisfy them: a rule without a method produces either an invention or a block. Applied whenever a backtest, a feature or a label is being designed or judged.
日本語の概要は準備中です。原文の説明を表示しています。
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure textures and decals cover all visible surfaces of a closed or extruded Blender asset, especially front/back caps and sidewalls, instead of relying on partial projected planes, curves, or linework overlays. Use when back textures do not fill the model, side textures are missing, spin/turntable views expose plain sidewalls, or a model needs separate UV treatment for caps and side surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Turn multiview fit reports into a sequential or parallel repair queue for aligning Blender products to source-of-truth templates. Use after validation shows disalignment, when the agent must iteratively fix wireframe, texture, lighting, or projection mismatches, and when skill gaps should trigger self-refinement before another rebuild.
日本語の概要は準備中です。原文の説明を表示しています。
First-run onboarding — guides new users through Genesis setup on their first CC session. Configures user profile, essential API keys, Telegram, GitHub backup, and service verification. Triggered automatically while the install is not yet FUNCTIONAL (the setup floor — Claude Code login + an LLM key + an embedding key — is unmet), not merely while ~/.genesis/setup-complete is absent. Re-runnable by asking Genesis to "run setup" or "reconfigure [section]".
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-driven web and open-source research for questions that require multiple sources, factual verification, comparisons, or an adopt/adapt/build decision. Use for substantial research in foreground sessions, the genesis-researcher subagent, and research-profile background sessions. Skip for a single stable fact or a known URL that only needs fetching.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.
日本語の概要は準備中です。原文の説明を表示しています。
Writes a detailed, executable implementation plan from an approved design or multi-step requirement, including exact files, interfaces, tests, commands, checkpoints, and rollback considerations. Use before touching code for a substantial feature, migration, refactor, or cross-cutting change. Not for a one-file bounded fix or for executing a plan that already exists.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
日本語の概要は準備中です。原文の説明を表示しています。
When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Text trademark detection and infringement risk analysis for e-commerce product listings. Trigger when users mention trademark detection, trademark risk check, brand infringement screening, product title trademark scan, text trademark search, listing compliance check, intellectual property risk assessment, text trademark detection, trademark infringement, brand infringement screening, listing compliance, intellectual property risk, Ruiguan. Even if the user does not explicitly say "trademark", trigger this skill whenever their need involves checking whether product text (titles, descriptions, bullet points) contains potentially infringing trademarks.
日本語の概要は準備中です。原文の説明を表示しています。