1,584 件 ・ 関連度順
概要と使いどころ
Aider is an open-source AI pair programming tool that runs in your terminal, letting you collaborate with LLMs to edit code across your entire codebase. With 42k+ GitHub stars and 15 billion tokens processed weekly, it features deep git integration, repo-wide code mapping, and support for 100+ programming languages.
日本語の概要は準備中です。原文の説明を表示しています。
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic product leadership guidance for SaaS and technology companies. Covers product strategy, roadmap planning, product discovery, user research, growth product management, platform strategy, product analytics, and product launches. Use when defining product vision, prioritizing features, conducting discovery, analyzing metrics, or launching products. Use for "product strategy", "roadmap planning", "feature prioritization", "product discovery", "product metrics", "PRD writing".
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates the tdmcp feature team end-to-end: design/wireframe → build → integrate → QA → release. Use whenever the user wants to build, implement, develop, ship, or add one or more tdmcp features/tools/effects/controls/AI-prompts for TouchDesigner, or to run them through a coordinated design→develop→QA→deploy pipeline. Also use for follow-ups: re-run, continue, update, fix, or improve a feature/batch, ship the next version, or rebuild just one part of a previous run. Single feature or a whole batch.
日本語の概要は準備中です。原文の説明を表示しています。
Implement ONE tdmcp tool from a spec — the canonical file pattern (Zod schema + …Impl + register… ToolRegistrar), a bridge Python payload via buildPayloadScript, and an offline msw unit test — touching only new files, never shared registries. Use when coding/implementing/writing a tdmcp tool, generator, effect, control, CHOP/TOP/SOP builder, or Python bridge work, especially when several features are built in parallel.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Updates tdmcp docs and roadmap for newly shipped or newly merged capabilities. Use when asked to update docs, update the roadmap, reconcile release docs, document new features, sync docs with CHANGELOG/package release, refresh cookbook examples after a feature wave, re-run/continue/fix a docs-roadmap pass, or check whether docs/ROADMAP.md is current. Runs a sub-agent workflow: release audit -> roadmap/docs edit + cookbook sync -> QA.
日本語の概要は準備中です。原文の説明を表示しています。
Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows / experiments features. Trigger on "/setup", "set me up", "get started", "onboard me", or a fresh clone where CLAUDE.md still has {{placeholders}}.
日本語の概要は準備中です。原文の説明を表示しています。
Designs implementation blueprints for features using exploration findings and architectural best practices (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Feature development workflow with exploration, architecture, implementation, and review phases. Use for implementing new features or significant changes.
日本語の概要は準備中です。原文の説明を表示しています。
Provides language-specific patterns for TypeScript, Python, and React including idioms, best practices, and common patterns. Use when implementing features in these languages.
日本語の概要は準備中です。原文の説明を表示しています。
Guides discovery and application of project-specific conventions including code patterns, naming, structure, and team practices. Use when exploring a codebase or implementing features to match existing patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Validates adapter files against live platform documentation to detect stale mappings,missing features, and outdated version information
日本語の概要は準備中です。原文の説明を表示しています。
Use when asking whether something in imp is actually finished - hunting stubs, placeholders, request fields that are parsed and then ignored, code paths or kernels that never run, gate-based features that silently no-op, tests that assert nothing. Triggers on "is this implemented", "unfinished", "stub", "placeholder", "dead path", "does this flag do anything", "accepted but ignored", "kernel never launched", "test asserts nothing", "neutral A/B on a gated feature". Do NOT use for structural debt / god files / duplication (codebase-audit) or for who-calls-what (code-graph).
日本語の概要は準備中です。原文の説明を表示しています。
Write modern, version-aware C# for .NET repositories. Use when choosing language features across C# versions, especially C# 13 and C# 14, while staying compatible with the repo's target framework and `LangVersion`.
日本語の概要は準備中です。原文の説明を表示しています。
Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.
日本語の概要は準備中です。原文の説明を表示しています。
Strictly adheres to specified user flow and game rules, making sure to follow documented features.
日本語の概要は準備中です。原文の説明を表示しています。
React ecosystem expert including hooks, state management, component patterns, React 19 features, Shadcn UI, and Radix primitives
日本語の概要は準備中です。原文の説明を表示しています。
Intent-to-command mappings for fullstack-typescript tech pack features.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt vulnerabilities in LLM-powered applications — direct/indirect prompt injection, system prompt extraction, ASCII smuggling, RCE via code tools, agentic AI exploits (ASI01-ASI10), data exfiltration via response channels, IDOR in chat history, jailbreak chains, RAG poisoning. Use when target has a chatbot, AI assistant, copilot, or agentic AI features.
日本語の概要は準備中です。原文の説明を表示しています。
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
日本語の概要は準備中です。原文の説明を表示しています。