「eth」の検索結果

Apply consistent photo adjustments across a set of images so they look like they were edited together. Use this skill whenever the user says "make my photos look cohesive", "give all these the same style", "apply a warm and golden feel to all of these", "make this cinematic", "match the look across my photos", "edit all my travel photos the same way", "batch edit these", "make these consistent", "fix my phone photos", or uploads a folder of photos and wants a unified, polished result. Also triggers for requests like "apply a preset to all of these", "make these look professional", or "they were shot in mixed lighting — can you fix them all". Outputs direct final image URLs plus an in-chat preview grid and optional Firefly Board link. Access: 🔐 Signed-In required | Gen AI: ❌

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

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.

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

Create any visual design using Adobe Express templates — including flyers, posters, banners, social media posts (Instagram stories, Facebook posts, LinkedIn graphics), business cards, invitations, greeting cards, resumes, cover letters, brochures, newsletters, certificates, presentations, YouTube thumbnails, email headers, logos, menus, labels, and more. Use this skill whenever the user wants to make, design, create, or build any visual — even if they just say "make me a flyer", "design a poster", "I need something for Instagram", "create an event invite", "make a business card", or any similar request. Also handles requests to find or browse templates, edit text/copy, change background colors, or animate a design. Access: 🔐 Signed-In required | Gen AI: ❌

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

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

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

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

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

Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.

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

Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.

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

COMPLETE BUG INVESTIGATION WORKFLOW — Combines screenshot + log reading into a full triage pipeline. USE FOR: any bug report that has both visual symptoms AND runtime errors, especially CompositePanel / ChildPanel mount failures, screen spec wiring breaks, or battle scene UI crashes. This is the master debugging workflow that orchestrates cocos-screenshot and cocos-log-reader together.

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

Reduce an oversized SKILL.md by checking whether an existing skill already covers the excess sub-workflow before creating a new child skill only when none fits. Load when a skill exceeds 200 lines and compress-skill determines excess content is genuinely CORE, when the same sub-workflow appears in multiple skills, or when universal-skill-creator or improve-skills identifies a coherent sub-capability. Also triggers on "split this skill", "extract a sub-skill", "this skill is doing too much", or "make this skill reusable". Always checks for an existing home before creating a new skill.

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

Break a stuck or complex problem into the smallest sub-question that, if answered, unlocks the next step — then answer it and repeat until the path forward is clear. Load when a problem feels genuinely stuck, when reasoning keeps circling, or when deep-thinking diagnoses a Socratic frame. Also triggers on "I keep going in circles", "what is the real question here", "help me reason through this step by step", "unstick my thinking", "recursive questioning", "what is the root question". Based on the recursive Socratic questioning method (EMNLP 2023) which outperforms CoT and Tree-of-Thought on complex reasoning tasks.

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

Match a user request to the right skill using trigger matching, project context, and conversation history. Score ambiguity 1–10 and resolve it using context signals or a single clarifying question. Load when project-orchestrator needs to route a request, or when multiple skills could match and the right one is unclear. Also triggers on "which skill should handle this", "route this request", "I'm not sure which skill to use", "disambiguate this", "skill routing". Called by project-orchestrator for request routing. For finding whether a skill exists for a capability, use skill-finder instead.

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

Run a pre-mortem — imagine the project has already failed one year from now and work backward to find the root causes before they happen. Load when the user asks for a pre-mortem, wants to imagine failure before committing, asks "what could go wrong before we start", "assume this fails — why", "risk analysis before launch", "what kills this project", "what could go wrong", or when deep-thinking diagnoses a pre-mortem frame. Based on Gary Klein's prospective hindsight method, which surfaces failure causes more effectively than forward risk analysis. Most useful right before a major commitment.

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

Route user requests to the right skill, decompose complex work into parallel subagents, and manage project phase transitions. Load when the user asks "what should I do next", "which skill should I use", "orchestrate this", "run the full workflow", "split this into parallel tasks", or when a complex request spans multiple skills. Also triggers on "coordinate agents", "parallel execution", "task decomposition", "agent workflow", "what phase am I in", or when the user gives a broad instruction that requires multiple skills in sequence. This is the project's brain — it decides what runs, when, and whether to parallelise.

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

Flip a problem, goal, or decision 180 degrees to find what forward thinking misses. Asks what would guarantee failure, then works backward to what must be avoided or changed. Load when the user says "invert this", "flip this problem", "what would guarantee failure", "think backward", "reverse engineer the goal", "think about it backwards", or when deep-thinking diagnoses an inversion frame. Also triggers on "what's the opposite of success here", "how would we sabotage this". Two methods: Failure Inversion and Opposite Goal. Max 2 clarifying questions before inverting. Always returns forward actions. For broader analysis, deep-thinking calls this.

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

Orchestrator for the experimentation skill suite — turn assumptions and product questions into rigorous, well-instrumented experiments and decision-grade readouts. Routes through backlog → spec → runbook → readout based on user need and existing artefacts. Platform-agnostic with PostHog as the primary binding. Load when the user asks to design an experiment, A/B test something, set up an experiment, run a holdout, test a hypothesis, decide what to test next, read out experiment results, analyse a test, or says "should we A/B test this", "experiment on the landing page", "is this lift real", "ship or kill this test", "what should we test next", "build an experiment backlog", "test the pricing page", "validate this with an experiment".

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

Quickly understand an unfamiliar codebase or project by mapping its architecture, identifying key components and data flows, and surfacing complexity hotspots. Load when the user asks to understand a repo, explain how something works, map the architecture, onboard to a codebase, or explore how components connect. Also triggers on "walk me through this codebase", "how does this project work", "explain the architecture", "what does this repo do", "show me the structure", "onboard me", or any request to build a mental model of a codebase before making changes.

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

Review a built frontend against its chosen direction, catch drift back to generic AI defaults, enforce state coverage, ethical patterns, UX heuristics, and polish, and check contrast with APCA (not the legacy WCAG ratio). Produces specific, prioritized fixes — never vibes-based feedback. Works with pasted screenshots or Playwright MCP automated capture. Load when the user asks to review a UI, audit a design, check if a frontend looks generic or vibecoded, evaluate visual quality or polish, says "review this UI", "is this design good", "audit my frontend", "does this feel like [product]", "design QA", or when frontend-design routes here. Sub-skill of frontend-design.

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

Map symbol dependencies, callers, and blast radius before editing code. Load when the user asks what depends on a symbol, what breaks if they change something, blast radius of a change, reverse dependencies, or which tests cover a function. Also triggers on "who calls this", "impact of changing", "dependency map", "what uses this", "find callers", or before any non-trivial edit when safe-change is not yet active. Pairs with codebase-understanding for broad architecture; this skill is symbol-scoped and edit-gated.

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

Turn assumptions, funnel opportunities, and product questions into a prioritised, feasibility-checked experiment backlog. Filters by traffic reality, metric latency, and method feasibility — not just ICE/RICE scoring. Maintains a living portfolio with status (idea → designed → running → readout → archived). Load when the user says "what should we test next", "build an experiment backlog", "prioritise our tests", "where should we experiment", "what's worth testing", or when the experimentation orchestrator routes here.

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

Turn a rough idea into a fully approved design before any code is written. Load when the user wants to brainstorm, explore ideas, design a feature, think through approaches, plan a new capability, or figure out what to build. Also triggers on "let's think through", "help me design", "explore options", "what's the best approach for", "I have an idea for", "before we build", or any request to design something before implementation. Enforces a hard gate: no code, no implementation until user approves a design. For executable feature specs (FRs, NFRs, ACs as Given/When/Then), route to `feature-spec` instead — brainstorming owns approach and architecture, not machine-readable requirements.

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

Surface every assumption embedded in a plan, strategy, or document, assess how critical and how validated each one is, and identify which ones to test first. Load when the user asks to map assumptions, surface hidden beliefs, find what must be true for this to work, run an assumption audit, or when deep-thinking diagnoses an assumption frame. Also triggers on "what are we assuming", "what must be true for this to work", or "find the untested beliefs". Based on David Bland and Alex Osterwalder's assumption mapping method from Testing Business Ideas.

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

Write a rigorous, decision-grade experiment spec — falsifiable hypothesis, primary metric, guardrails, randomisation unit, exposure definition, method (A/B, holdout, switchback, quasi-experiment, MAB), MDE/duration plan, peek policy, validity threats, and pre-committed decision rule. Platform-agnostic. Load when the user has a candidate experiment and needs to spec it before launch, or says "spec this experiment", "write the test plan", "design this A/B test", "what's the hypothesis", "how big a sample do we need", "how long should we run this", "define the metrics for this test", or when the experimentation orchestrator routes here.

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

Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".

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