「hands」の検索結果

Check a Framer project's Server API connection: verify the per-project API key with the official handshake. Trigger phrases: framer, framer api, framer project.

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

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, mid-build deviations from the plan need capturing, or a finished change needs buy-in or verified understanding before merge. Pairs with [write-spec](../write-spec/SKILL.md) — walk the quadrants to burn off fog before slicing, and feed the finished map into the spec.

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

Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each example input, grade the artifact against the expected outcome, and let the gaps drive the edits. Use when the user wants to test/eval/improve/harden a skill, says "this skill keeps producing X / keeps missing Y", or hands a skill plus example input→expected-output pairs. Pairs with [write-skills](../write-skills/SKILL.md) (the authoring principles every fix obeys).

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

Records visual proof while testing UI behavior — the agent tests the app hands-on via computer use while a screen recording with structured test/assertion annotations captures the session — then posts the video and a results summary to the PR and tracker issue. Use whenever a change needs verifiable evidence that it works, instead of prose claims — including headless environments (scripted screenshots and probes) and non-UI changes (measured numbers, output pairs).

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

Maintain a brand kit — the canonical brand context an ad or content pipeline reads (positioning, audience, voice, standing instructions, brand-type, value-props, colors), plus manage the product list and attach product photos. Use when someone says "update my brand kit", "set my brand voice/audience", "add a product to my brand", or hands you a folder of product shots to attach. Platform-agnostic: it teaches the field model, partial-update/clear semantics, override behavior, caps and validation, and the hero-image and product-matching rules — independent of any specific backend.

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

Assemble a wordless macro-tabletop food-product sizzle ad from a config — normalize fps and SAR across ~4 photorealistic macro clips (hands tearing, flat lay, bite, box hero), concat them, apply a global anti-AI grain pass (eq plus hqdn3d plus noise), composite the audio (a non-diegetic instrumental music bed plus a couple of short diegetic SFX like a snap and a tear placed at measured cue points, loudnorm), composite a STATIC end card entirely in PIL (real logo PNG plus real product PNG plus a serif heritage headline plus a CTA — never AI-rendered text), and burn optional serif stat-callout pills at beats. This is the FREE deterministic assembly stage (normalized concat plus grain plus music and SFX mix plus PIL end card plus callouts); the macro keyframes, i2v clips, and music bed come from create-image-fal, create-video-fal, and create-music-elevenlabs. Use for the food-product-sizzle format.

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

Use when SLCI code inspection has failed due to compatibility issues and you need to diagnose the incompatibilities. Traces inspection failures back to root-cause incompatibility settings or known limitations by matching failed code lines against known incorrect code generation patterns and documented limitation scenarios. Hands off to slci-compatibility-analysis for fixes. Trigger keywords: inspect, inspection failed, trace inspection errors, why did inspection fail, SLCI verification failures, limitation.

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

Build and maintain one coherent company story across employees, investors, customers, candidates, and partners. Use when preparing all-hands meetings, investor updates, board presentations, recruiting narratives, or crisis communications.

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

Detects prompt injection hidden in documents from the other side (pleadings, skeletons, bundles, served evidence, opponents' emails and attachments) before an AI reads them, so the model is not turned against your client. Checks word by word that the text an extractor hands the model was visibly drawn on the page: white, near-white, covered, clipped, off-page, tiny, transparent and invisible-mode text in PDF (ink test plus OCR); Word formatting resolved as Word does (styles, shading, theme colours, scaling, off-page frames, fallbacks, unused headers); HTML/CSS, RTF, email with attachments and zips, xlsx/pptx and legacy formats. Flags Unicode smuggling, text addressed to an AI and authorities found only in hidden text. Fails closed. Optional Read-tool hook. Use BEFORE any AI summary or analysis of an opposing or third-party document. Triggers: 'scan for injection', 'is this document safe', 'check the other side's skeleton', 'injection guard'.

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

Adversarially stress-tests a legal text — a contract, statute, regulation, or judicial opinion — for interpretive ambiguity: it finds the seams where the people governed by it will later disagree about what it means and turns each into a concrete dispute scenario with both sides' arguments, the likely outcome, and a fix. Use it whenever someone wants to pressure-test, red-team, audit, or find weak spots, loopholes, gaps, ambiguities, or drafting problems in a legal document; whenever a drafter wants to tighten a contract, statute, regulation, or opinion before it issues; whenever a litigator wants to mine an opinion or contract for arguments; or whenever someone hands over a legal text and asks where it will be fought over or for issue-spotting. Trigger it for contract review, statutory-ambiguity analysis, judicial-opinion scope analysis, and drafting QA — even if the user never says "stress-test" or "ambiguity."

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

Design a Montessori three-period lesson for introducing concepts through concrete materials and naming. Use when teaching vocabulary, classifications, or concepts through hands-on materials.

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

Designing for visionOS — spatial layout and ergonomics (60pt eye targets, field-of-view placement, dynamic scale), eyes-and-hands input with hover rules, motion and visual comfort (the 0.2 Hz rule, vection, depth-cue agreement), immersion strategy, spatial sound, and the video-format decision guide. Use when designing or reviewing any visionOS app, window, volume, or immersive experience.

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

visionOS skills — spatial design (layout ergonomics, eyes-and-hands input, motion comfort, immersion, environments) and widget patterns (mounting styles, glass/paper textures, proximity-aware layouts). Use when designing, building, or reviewing anything for visionOS.

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

Publish an article to a site you own — with a searched-for title, a real author, a licensed cover image, linked sources, and (optionally) one planned backlink. Use when the user says "publish an article", "put this on our blog", "publish this draft", "add a backlink", or hands over finished copy to ship. Covers the pre-publish gates that decide whether a published page earns anything.

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

Use when a designer needs hands-on production direction inside a tool — Canva, Figma, or Adobe Express: which template to start from, the operating order, element-by-element mapping, grid and spacing, brand kit colors and fonts, export checklist, and the dos and do-nots. Trigger on 'Canva brief', 'Figma brief', 'production direction', 'how do I build this in Canva', 'layout direction for the designer', 'the junior designer needs step by step'. Not for — the creative concept for a static, see `42-image-brief-global`; the concept for a slide sequence, see `43-carousel-brief-global`; the brand rules being applied, see `46-brand-guideline-global`; adapting one master into every size, see `50-asset-resize-global`.

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

Weekdays, light browser lane. The one routine in this kit with an outward surface. Takes the slots that are due today, whose drafts were written yesterday and passed the copy check, whose hold box is not ticked, and whose destination the member wrote into the publish allow list themselves, and hands each one to the channel the member configured. It records a receipt the instant each slot lands. It never drives a browser control to publish, never replies, sends only where you released the channel a message, spends only where you released it, and never touches a credential.

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

Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes /atlas, or wants task-driven development.

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

Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

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

Use for authorized wireless security assessment including Wi-Fi capture, WPA handshake analysis, rogue AP detection research, and lab-only deauth testing.

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

Use when you know what you want but not which /gsd-* command to run. Routes freeform text to the best matching GSD command, confirms the match, then hands off without doing the work itself.

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

Use when the user says run the rest autonomously, overnight, or hands-off through the remaining phases. Runs discuss, plan, execute per phase, pausing only for user decisions, then milestone audit, complete, and cleanup.

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

Decision protocol for wiring a verify-then-fix loop around a code-editing LLM agent. The agent edits → runs lint/test → reads the output → fixes → re-runs, bounded by an iteration cap and an escalation rule. Activates whenever a coder agent has a verifiable success criterion (exit code, type-checker output, failing assertion) and the user wants the agent to converge to "green" on its own. Framework-agnostic — wraps Aider's `--auto-lint`/`--auto-test`, an OpenHands SWE-Bench loop, a manual LangGraph cycle, or Claude Code's bash tool just the same.

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

Rewrite an exec update, memo, strategy doc, deck outline, Slack post or talk so it lands with senior people, and get a graded score plus the top 3 fixes. Use when you say 'rewrite this for my VP', 'exec update', 'how do I present to the CEO', 'my memo is too long', 'prep me for this review', 'all-hands talk' or 'I get nervous presenting'. Draws on 296 insights from 90 Lenny's Podcast guests incl. Wes Kao, Nancy Duarte and Matt Abrahams.

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

Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does it actually work". Not a unit test runner.

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