「eac」の検索結果

Run Claude Code, Codex CLI, Gemini CLI, or OpenCode through bounded H100 post-training tasks and compare how well each agent improves a base LLM.

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

AutoGen is Microsoft's open-source framework for building multi-agent systems where AI agents converse with each other and humans to solve tasks, with support for tool use and human-in-the-loop workflows.

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

Astro is a modern web framework for building content-driven websites. It ships zero JavaScript by default, supports multiple UI frameworks (React, Vue, Svelte, Solid), and provides islands architecture for optimal performance.

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

Use Cloudsplaining when an agent needs to flag privilege-escalation paths and overbroad IAM permissions before an AWS policy change reaches production.

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

Validates Ansible playbooks in check mode using ansible-playbook --check --diff and the Ansible Python API. Detects idempotency issues, undefined variables, and unreachable hosts before production runs.

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

Decide what to borrow, adapt, or write before building something. Use when the user describes an app, tool, CLI, or feature they want to build and needs to know which parts already exist as open-source GitHub repos (BORROW), which are worth reading and adapting (KITBASH), and which to just write (WRITE). Every repository named is checked against the live GitHub API, so invented ones never reach the user.

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

Expert sales operations and analytics guidance for revenue teams. Use when designing CRM workflows, building sales dashboards, optimizing pipeline analytics, creating lead routing rules, designing territories, calculating commissions, managing data quality, building forecasting models, or integrating sales tech stack. Covers Salesforce, HubSpot, Outreach, Gong, and RevOps best practices.

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

Expert PR and media relations guidance for earned media, press coverage, and reputation building. Use when writing press releases, crafting media pitches, developing journalist relationships, planning embargo strategies, managing crisis communication, placing thought leadership, building analyst relations, submitting award applications, or measuring PR coverage. Use for media outreach, press kits, speaking opportunities, and earned media strategy.

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

Survey one surface of tdmcp (artist controls, library/packaging, CLI/DX, AI/LLM, or TouchDesigner depth) for candidate NEW features — inventory what exists, cross-check the roadmap, apply the gap-finding lenses, vet each idea, and emit a structured, novelty- and confidence-labelled candidate list to _workspace/discovery/. Use when a td-surveyor agent is scouting a surface during the feature-discovery harness.

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

Consolidate the td-trend-scout reports under `_workspace/hype-scout/` into one prioritized HYPE_TOOL_BACKLOG.md — dedupe trends across surfaces, vet each candidate against the real tdmcp codebase (layer fit, operator coverage, bridge work), rank by Hype × Build-Ease, and emit a 'Ready for tdmcp-pipeline' top-5. Use when a td-hype-synthesizer agent is consolidating scouts at the end of the tdmcp-hype-scout harness.

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

Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.

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

Quality-assure integrated tdmcp features: run the four PR gates + recipe/bridge tests, cross-boundary coherence checks (tool schema↔CLI↔docs↔registry, operator↔createable, bridge↔client), and live TouchDesigner validation (preview + post-cook error check) when the bridge is reachable. Use when validating/QA-ing/testing tdmcp tools, checking a feature actually cooks in TD, verifying CLI matches a tool, or gating a release.

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

Look at real hardware, screens, panels, and wiring on a desk or workbench through a camera, so Claude can SEE physical output that no unit test, log, or API can. Use whenever the user says "are you seeing this?", "olha isso", "look at this", "watch this", "can you see...", "check the camera", "look at the screen" / "look at the display", "is this wired right?", or "what's this part?"; asks to visually verify a rendered display, LCD, LED, or panel; wants a wiring, polarity, or voltage-rail check before power-on; or needs to confirm a font, layout, clipping, or on-screen value renders correctly instead of trusting green tests. Grabs the current camera frame(s) and reads them; supports a watch mode for an action in progress. Needs a snapshot-capable camera reachable over HTTP (Android IP Webcam app, Raspberry Pi camera-streamer, or any snapshot URL) set via CCE_CAM_URL.

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

Use to run a dynamic, goal-driven workflow — orchestrate a multi-step goal by composing skills, tools, and MCPs, with a quality gate and verification at each step. Trigger on "/workflow", "run the <name> workflow", "orchestrate X", or a multi-step recurring goal ("draft the investor update", "give me my morning brief"). Follows references/sops/dynamic-workflows.md and the wf-*.md cards. Respects the autonomy/cadence gate (auto on reversible/internal, draft-then-approve on external/regulated).

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

Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a full /structure brief or a /decide call. Trigger on "/triage", "triage this", "process my inbox", "sort these asks", "clear my backlog", "what do I do with all this".

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

Use when the user says 'send this to my client', 'get feedback on this page', 'send a review link', 'what did the client say', or 'work through the review notes'. Sends a Murmur review link, reads the notes reviewers pin to the page, replies, applies each change on a duplicate, and resolves every note with the snapshot of the change.

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

Use when the user says 'fix my catalog for ai', 'improve my ai readiness score', 'get my catalog to 90', or 'my products keep getting rejected by google'. Runs an ordered fixlist that writes the missing alt text, descriptions, brands, GTINs, and category mappings, snapshotting before each change.

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

Use when the user says 'migrate beaver builder to bricks', 'convert bb to bricks', or 'replace beaver builder with bricks'. Reads the Beaver Builder flat node map, maps each module to its Bricks element, and creates draft duplicates for review.

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

Use when the user says 'migrate elementor to bricks', 'convert elementor to bricks', or 'move my site from elementor to bricks'. Reads the Elementor JSON widget data, maps each widget to its Bricks equivalent, and creates draft duplicates with clean Bricks JSON.

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

Remove the AI tells readers react to in a Threads post: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity. Also --mode audit (500-char fit, hook, hashtag cap), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the numbers, turning points and stories posts are made of). Not for writing from scratch (use threads-post-writer). Keywords: humanize, de-AI Threads post, interview me, audit before posting.

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

Build UI interactions whose motion comes from a physical model instead of durations and easing curves. Turn a feel described in words ("a toggle that feels heavy", "a drawer with a magnetic snap", "a card you throw into a corner", "a knob with heavy detents", "a sticky slider") into a production component driven by mass, stiffness, damping and force fields (magnets, friction, walls), on a line, in a plane or around a dial, plus a test rig that plots position, velocity and the force field, overlays the model's prediction on the measured motion, and exports the same spring to Framer Motion, react-spring, SwiftUI, Compose or CSS linear(). Use this whenever someone asks for an animation, transition, spring, gesture, drag, flick, snap points, bottom sheet, toggle, slider, carousel or any micro-interaction that should "feel" a certain way, or wants to tune or explain a spring, even if they never say "physics".

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

Use for frontend code and UI fixes. Triggers: CSS, responsive, animation, React, Vue, Svelte, Tailwind, redesign, anti-slop, 프론트엔드, UI 작업, 반응형, 디자인 수정.

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

Create or update a Wardley Map of how any domain delivers value. Maps the needs it serves, the capabilities involved, how each is evolving (genesis to commodity), and strategic plays. Applies to any domain, not only software.

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

Record findings from completed offline human tasks (interviews, observations, outreach) back into the canvas. The re-entry point after /mycelium:handoff.

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