513 件 ・ 関連度順
概要と使いどころ
Performs fast first-pass triage of an unknown file to decide depth of analysis: file type identification, hashing, reputation lookup, packing/entropy check, and string review. Activates for requests to triage, classify, or do initial assessment of an unknown or suspicious file.
日本語の概要は準備中です。原文の説明を表示しています。
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Drilling and Boring Machine Tool Setter, Operator, or Tender — deciding whether a hole's depth-to-diameter ratio requires peck drilling, establishing a straight hole start before wander compounds, reducing cutting parameters for a long-reach boring setup versus a short-reach one, or diagnosing whether a dimensional drift traces to tool wear rather than assuming the tool still looks sharp.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Etcher/Engraver — compensating a resist pattern for expected undercut before etching fine detail, calculating etch time from a known etch rate rather than judging completion visually, verifying a functional engraving's line width/depth against its actual accuracy requirement, or re-validating process parameters on a new material batch before production.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a construction laborer — determining which OSHA-mandated protective system (sloping, benching, shoring, or shielding) a trench needs given its soil classification and depth, working as spotter/signal person on a crane or heavy-equipment lift, staging material and equipment on an active multi-trade site, or reading which hazard zone (excavation, crane swing, electrical rough-in) is live as work moves across the site.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Continuous Mining Machine Operator in underground coal — reading a methane monitor trend and deciding whether to de-energize, judging whether cumulative unbolted advance has hit the roof control plan's cut-depth limit, deciding whether a permissibility defect requires immediate shutdown in a gassy heading, diagnosing whether a shift's production shortfall traces to cutting rate or shuttle-car haulage, or deciding whether a "drummy" roof sound stops the cut.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and protect deep work: scheduling focus blocks, task selection, shutdown rituals, and measuring depth. Use when important work never gets sustained attention or days fill with shallow tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a workplace safety incident tracking system for incident classification accuracy, root cause analysis depth, OSHA 300 log recordkeeping compliance, trend analysis capabilities, and leading indicator identification..
日本語の概要は準備中です。原文の説明を表示しています。
Analyze game design documents and implementations for core gameplay loop clarity and depth, XP leveling curves and unlock pacing, difficulty curve spikes and plateaus, skill tree viability, player motivation via Self-Determination Theory.
日本語の概要は準備中です。原文の説明を表示しています。
Create QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what should we test", "prioritize testing", "risk-based testing", "test coverage plan", "QA approach for this project", "coverage matrix", "test scope", "how should we approach testing this quarter", "where are our coverage gaps", or any request to define the strategic plan for testing - not the execution of it. Also trigger at project kickoff when a QA lead asks "how do we approach quality on this?"
日本語の概要は準備中です。原文の説明を表示しています。
**WORKFLOW SKILL** — Risk awareness before action. USE FOR: assessing risks (security, data integrity, compatibility, operational, reversibility) of any task at variable depth. Accepts weight: Light (quick scan), Standard (dimensional analysis), Deep (full Risk Radar with evidence). Can be invoked multiple times in the same flow with increasing weight. DO NOT USE FOR: penetration testing, compliance audits, static security analysis tools.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).
日本語の概要は準備中です。原文の説明を表示しています。
Requirements for a Salesforce Enterprise Territory Management (ETM) territory design: alignment criteria, coverage model selection, assignment rule logic, hierarchy depth and breadth, and user-to-territory ratios. Trigger keywords: territory design, territory alignment, territory model requirements, sales coverage model, territory criteria, geographic territory, named account territory, overlay territory. NOT for ETM setup steps — use admin/enterprise-territory-management. NOT for loading territory assignment data — use data/territory-data-alignment. Trigger keywords: territory design questionnaire, territory requirements document, assignment rule matrix, territory type priority, realignment plan, territory access level decision, accountAccessLevel, opportunityAccessLevel, ObjectTerritory2Association, UserTerritory2Association, Planning state model, territory acceptance tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to define and validate the requirements for a Salesforce Partner Relationship Management (PRM) implementation: deal registration flows, lead distribution models, partner tier hierarchies, MDF budget tracking, and co-marketing content entitlement. Trigger keywords: partner community requirements, PRM deal registration setup, channel partner portal requirements, lead distribution partner, partner tier management, MDF tracking, co-marketing entitlement. NOT for implementing the partner sharing model — use data/partner-data-access-patterns. NOT for building the portal in Experience Builder — use admin/experience-cloud-site-setup. More trigger keywords: partner portal design worksheet, partner tier licence and role depth, PartnerAccountId blank on opportunity, portal role Executive Manager User, sharing set does not support Lead, enable partner user greyed out, offboard a partner firm, PartnerMarketingBudget PartnerFundRequest PartnerFundClaim, ChannelProgramLevel partner tier, deal registration acceptance step.
日本語の概要は準備中です。原文の説明を表示しています。
Designing Lookup vs Master-Detail vs Hierarchical vs External relationships: cascade delete, roll-up summaries, ownership, sharing implications, polymorphic lookups, junction objects, relationship depth limits. NOT for restricting which records a lookup can pick — use admin/lookup-filter-cross-object-patterns. NOT for a roll-up across a plain lookup — use data/roll-up-summary-alternatives.
日本語の概要は準備中です。原文の説明を表示しています。
Education Cloud (EDA — Education Data Architecture) setup: student success hub, advisor workflows, enrollment management, academic data model. NOT for the EDA object model in depth (Affiliations, Course_Connection__c) — use data/eda-data-model-and-patterns. NOT for SIS enrollment sync — use integration/sis-integration-patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Search the web with LLM-optimized results via the Tavily CLI. Use this skill when the user wants to search the web, find articles, look up information, get recent news, discover sources, or says "search for", "find me", "look up", "what's the latest on", "find articles about", or needs current information from the internet. Returns relevant results with content snippets, relevance scores, and metadata optimized for LLM consumption. Supports domain filtering, time ranges, and multiple search depths.
日本語の概要は準備中です。原文の説明を表示しています。
Author and own ONE system's design document (the A–K SYSTEM GDD) at .unikit/gamedesign/systems/SYS-<slug>.md — the depth layer of the GDD, single-system scope. Create the skeleton and walk the collaborative section-cycle to write its parameters, rules, formulas, and acceptance criteria ("detail the combat system", "write the GDD for the inventory system", "fill in the rest of this system doc", "spec out the parameters of X"), AND revise it after approval under the delta discipline ("raise the damage by 10%", "tune the economy", "rework the status system", "nerf X", "change this rule") — a number change is Tuning, a small rule a Tweak, restructuring a Rework; each bumps the version and logs the delta. To add a NEW system or restructure the system map use /unikit-gd-spec; to edit GAME.md content use /unikit-gd-spec; the moment an edit also touches a second system, a content type, a flow, or GAME.md (two or more zones) use /unikit-gd-apply; to invent a brand-new game concept use /unikit-gd-brainstorm.
日本語の概要は準備中です。原文の説明を表示しています。
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.
日本語の概要は準備中です。原文の説明を表示しています。
Ground GEODE design and evaluation work in Stanford CS329A Parts 2 and 5. Use for test-time compute, planning, multi-step reasoning, deep research, LATS, independent subplans, best-of-N, repair depth, measurement replication, verifier authority, and GEODE/Eco²/SIL/Crucible comparisons.
日本語の概要は準備中です。原文の説明を表示しています。
Fast parallel codebase scouting. Spawns multiple Explore subagents to search directories simultaneously, returning a consolidated file map with architecture fingerprint, complexity estimates, and routing suggestions. Use before planning, debugging, or any task spanning multiple directories. NOT for reading a single known file in depth (use Read directly); NOT for semantic find-usages or go-to-definition.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in Jungian analytical psychology, depth psychology, shadow work, archetypal analysis, dream interpretation, active imagination, addiction/recovery through Jungian lens, and the individuation process - grounded in primary sources and clinical frameworks. Activate on 'Jung', 'Jungian', 'shadow work', 'archetypes', 'dream interpretation', 'active imagination', 'individuation', 'anima', 'animus', 'collective unconscious', 'addiction', 'recovery', 'spiritus contra spiritum'. NOT for therapy or diagnosis (only licensed analysts diagnose), active psychosis, severe dissociation, or replacing the relational container of actual Jungian analysis.
日本語の概要は準備中です。原文の説明を表示しています。