「direction」の検索結果

Use when the user runs /web-design-review with a URL to visually audit and fix a live UI. Not for design direction: use design. Not for variant galleries: use design-variants.

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

Use when asked to design a module interface, seam, or testable boundary. Not for UI direction picking: use design. No source or remote-system changes.

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

Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.

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

Delegate an approved finite batch of independent engineering or research responsibilities using the operator's existing worker channel. Use for broad repository discovery, multiple search directions, repeated checks and substantial dirty work; keep coupled single tasks with one worker and explicit solo work in the main session.

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

Create or redesign product UI in an existing codebase, including a wireframe, substantive visual variations, and an interactive prototype. Use for requests about UI layout, visual direction, screens, flows, components, a landing page, dashboard, or making an interface feel polished. Do not use for backend work, system architecture, decks, or logic-only UI fixes.

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

Food photography audit — reviews existing photos, identifies missing item photos, provides specific shot list with angles, lighting, and styling direction

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

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

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

Apply StyleKit visual styles and public assets when building, restyling, or reviewing UI. Use for named StyleKit styles, visual direction, mobile interface patterns, and component-library selection; preserve the target platform and existing product behavior.

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

On-brand visual marketing content using Paper MCP and parallel agent teams. Reads the project's brand/ directory to build a design system, then spawns designer agents in parallel — each creating a unique artboard with a different on-brand layout interpretation. Intelligently adapts agent count and approach based on user goals via AskUserQuestion interrogation. Produces Instagram carousels, TikTok slideshows, social posts, story slides, and visual assets. When used with content spec YAMLs from /slideshow-script, each agent gets a unique script AND unique design direction. Make sure to use this skill whenever the user wants visual marketing content designed in Paper — carousels, slideshows, social posts, story slides, or any visual asset. Even if they just say "design something" or "make slides" or "create visual content", this is the skill. Also triggers on "paper marketing", "instagram design", "TikTok design", "slideshow design", "create carousel", or "social graphics".

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

Structured marketing brainstorming when direction is unclear. Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore approaches', 'help me think through this', 'marketing ideas', 'what campaign should I run', 'where do I start with marketing', 'what's our marketing plan', or 'I have no idea how to promote this'. Explores 2-3 approaches and recommends the best path forward with a specific next-skill handoff. Even vague frustration like 'nobody knows about my product' or 'how do I get users' should trigger this when no specific channel or tactic is mentioned.

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

Generate visual asset briefs, ad copy variants, AI image prompts, video scripts, and storyboards. Full creative production system with 5 specialized modes: product photos, product video, social graphics, talking heads, and ad creative. Make sure to use this skill whenever the user mentions any visual or creative marketing need — ad creative, image prompts, video scripts, thumbnails, banners, social graphics, product photography, storyboards, or marketing visuals of any kind. Even if they just say 'I need images for my campaign' or 'make something visual', this is the skill. Owns thumbnail and banner briefs plus the creative direction. Includes platform-specific dimensions, AI anti-slop techniques, and Remotion composition templates. For rendering the actual image file, see /image-gen; for AI-generated marketing/brand videos, see /higgsfield-generate; for stitching slides into an MP4, see /video-content.

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

Run cross-experiment competition strategy synthesis. Invokes the competition-strategist agent which loads daily_reports/* + all SESSION_NOTES.md / claudeSummary.md / submit/SUBMISSIONS.md / KAGGLE_DIRECTION.md in parallel and proposes next moves. Use weekly or at inflection points.

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

Invoke only when the user explicitly asks to review code through the "single level of abstraction / layered error handling" lens — a function does only its own layer's business logic while errors are handled above or below. The agent reports detections, raw-count measurements, and move directions. Apply only when the user explicitly requests this lens.

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

Inventory all founder resources across 8 categories for a one-person company. Use when Codex needs to systematically confirm what resources the founder has — experience, network, skills, relationships, channels, assets, time/money constraints, hard limits — by first doing a broad scan of each category, then drilling into specifics (distribution, usable portions, how to use, cost of use), and producing a confirmed detailed resource inventory written to `opc-doc/`. Does NOT analyze directions, preferences, suitability, or risk tolerance — those belong to downstream skills.

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

Chinese journal matcher — performs L3 6-dimensional matching (keywords, cited direction, trend, solicitation, institution, cross-discipline), calculates conditional acceptance probability with review cycle estimation, and outputs tiered submission strategy (aspiration-stable-safety) using 4-layer weighted ranking.

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

Use when the user asks about the CTI Hyperloop framework, the intelligence lifecycle as a high-tempo loop, or how to map intelligence work across strategic / operational / tactical levels with bidirectional feedback. Liberty91's operational doctrine.

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

Assume the role of Galyarder CEO (Chief Executive Officer). Apex Instance of the Intelligence Layer protocol. Deconstruct intent into departmental mandates, optimize strategic direction, and audit operational bandwidth.

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

Use when a research project needs normal project memory updated from human intent, sources, evidence pressure, experiment results, or direction changes; strict graph review is optional advanced mode.

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

Use when the user wants a related-work survey, technical lineage, task timeline, or paper-map around a baseline paper, research task, benchmark, or project direction.

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

Design and audit PFC 5.0 asphalt dynamic loading and stress-wave studies with damping, timestep, rate, dispersion, source direction, boundary reflection, histories, and wheel-load handoff checks.

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

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

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

"Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.".

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

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. Use when building landing pages, portfolios, redesigns, or frontend interfaces that need strong visual taste.

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

Break the spell of local productivity. Ask whether completing all open beads actually closes the gap to the project goal. Use at milestones or when busy agents feel directionally off.

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