「bot」の検索結果

Remove AI-generated patterns from QA reports, bug reports, test summaries, status updates, and quality communications. Detects and rewrites robotic test-result language, template-sounding status updates, inflated severity descriptions, and generic stakeholder reports — without inventing facts. Makes QA writing sound like a real engineer wrote it. Use when: "humanize report," "rewrite QA summary," "fix test report," "make this sound human," "clean up status update." Not for: general prose, blog, or marketing-copy cleanup — use the global humanizer skill. Not for: classifying or routing CI failures — use ai-bug-triage. Related: ai-bug-triage, qa-metrics, qa-dashboard, quality-postmortem.

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

Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.

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

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

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

Summarize a contributor's Git history, a provided work log, or both into a concise, review-friendly self-evaluation for quarterly, semi-annual, or promotion cycles.

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

Run the evidence loop of one long-horizon GPU kernel optimization episode. Use this skill to reconstruct the incumbent, profile and localize a bottleneck, research progressively, plan one coherent direction, implement and repair, validate development correctness and performance, and record every decisive experiment in the episode journal.

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

Create polished HTML slide decks and PDF-ready documents for consulting deliverables. Uses the RRBC design system with warm light mode, dark mode cover pages, Lora/Inter/Roboto Mono typography, and data visualization palette. Trigger on 'deck', 'slides', 'presentation', 'pitch deck', 'keynote', 'report', or 'PDF'.

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

Vulnerability audit and dataflow analysis built on the neug CPG engine. file_audit (default, recommended): first builds a function-level summary graph (tier1) over the entire project, then incrementally builds detailed CPGs (tier2) on demand for chosen functions; both tiers coexist in a single neug database (unified schema, cross-layer refines edges; C/Java/Python/Rust). All capabilities are exposed as CLI tool subcommands (audit/overview/build/query/methods/paths), so an agent can drive the audit step by step via shell; the audit subcommand can also run the built-in LLM loop. The same tooling also supports a dataflow analysis mode (Workflow C): no vulnerability hunting, only variable-level dataflow tracing for functions of interest, producing dataflow_analysis.json. repo_audit: multi-round LLM/Cypher audit over a full-repo CPG. Use when the user asks to audit a codebase/project for vulnerabilities, scan a project with CPG/neug, run repo_audit/file_audit, find source-to-sink taint paths, or analyze dataflow inside a function. Supports C, Java, Python, and Rust.

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

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

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

Dify is an open-source platform for building LLM apps such as chatbots, agents, workflows and RAG knowledge bases, and it exposes every published app as a REST API. Use when a user asks to self-host Dify with Docker Compose, configure Dify environment variables, call a Dify app or workflow API, upload documents to a Dify knowledge base, export or import a Dify DSL file, run a Dify app from the terminal with difyctl, or upgrade and back up a Dify instance.

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

Add live chat and customer support with Crisp. Use when a user asks to add a chat widget, implement live customer support, set up a help desk, create a knowledge base, or add a chatbot to a website.

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

Conform is a React form validation library that progressively enhances native HTML forms: it validates FormData against a Zod, Valibot or Yup schema on the server and, optionally, on the client, so a form works before JavaScript loads. Use when a user asks to build a form with Conform, validate a Next.js Server Action or a React Router / Remix action, share one schema between client and server, add or remove rows in a field list, or move to Conform's future API.

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

Amazon SES (Simple Email Service) sends and receives email through AWS: transactional and marketing mail, templates, bounce and complaint tracking, and inbound mail processing. Use when a user asks to send email with SES, verify a domain or set up DKIM, move an SES account out of the sandbox, create or bulk-send email templates, add an attachment or unsubscribe header, handle bounces and complaints with SNS, manage the suppression list, or store incoming mail in S3 with receipt rules. Covers the SES v2 API (aws sesv2, boto3 sesv2).

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

Optimize mobile app listings for discovery and conversion in Apple App Store and Google Play. Use when tasks involve ASO keyword research, title and subtitle optimization, screenshot and preview video design, A/B testing store listings, review management, localization for international markets, tracking keyword rankings, or improving download conversion rates. Covers both iOS and Android store algorithms and best practices.

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

Integrate Claude AI into applications with the Anthropic SDK. Use when a user asks to add Claude to an app, use Claude for text generation, build a chatbot with Claude, use Claude's long context window, implement tool use with Claude, stream Claude responses, use Claude for code generation, document analysis, or reasoning tasks. Covers Messages API, streaming, tool use, vision, system prompts, extended thinking, and batch processing.

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

The craft of weaving story into interactive systems where the player is both audience and author. This skill covers the unique challenges of game narrative: branching structures that respect player agency, environmental storytelling that rewards exploration, dialogue systems that feel alive, and the delicate balance between authored experience and emergent narrative. Unlike linear media, games don't tell stories TO players - they create the conditions for stories to emerge WITH players. The narrative designer's job is to build the scaffolding that supports infinite player-authored moments while maintaining coherent themes and emotional arcs. This skill synthesizes lessons from Disco Elysium's internal monologue as gameplay, Hades' death-as-narrative-engine, interactive fiction's branching mastery (Inkle, Twine), and procedural narrative pioneers like Dwarf Fortress. It addresses ludonarrative harmony, bark systems, cinematics that respect agency, and the "and therefore" test that separates plot from story. Use when "narrative design, game story, game writing, dialogue system, branching narrative, player choice, environmental storytelling, bark system, quest design, lore delivery, ludonarrative, interactive fiction, inkle, twine, dialogue tree, player agency, cinematic design, voice direction, localization, procedural narrative, narrative, game-writing, dialogue, branching, player-agency, environmental-storytelling, quest-design, voice-acting, localization, interactive-fiction, procedural-narrative, ludonarrative" mentioned.

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

Expert at diagnosing and fixing performance bottlenecks across the stack. Covers Core Web Vitals, database optimization, caching strategies, bundle optimization, and performance monitoring. Knows when to measure vs optimize. Use when "slow page load, performance optimization, core web vitals, bundle size, lighthouse score, database slow, memory leak, optimize performance, speed up, reduce load time, performance, optimization, core-web-vitals, caching, profiling, bundle-size, database" mentioned.

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

A great product that nobody knows about is a failed product. Go-to-market strategy is how you get your product into customers' hands. Not marketing in the abstract - specific motions, channels, and sequences for your specific situation. This skill covers GTM motion selection (product-led, sales-led, community), channel strategy, launch sequencing, early customer acquisition, and the critical transitions between GTM phases. Use when "go to market, GTM, launch strategy, how to get customers, sales vs product-led, channel strategy, market entry, customer acquisition, distribution strategy, product launch, getting first customers, sales motion, bottoms up, top down sales, go-to-market, gtm, launch, product-led-growth, sales, channels, customer-acquisition, distribution, marketing" mentioned.

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

Patterns for FPGA development including RTL design (Verilog/VHDL), timing closure, clock domain crossing, high-level synthesis, and verification. Covers both traditional HDL and modern HLS approaches. Use when ", " mentioned.

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

Patterns for computer-aided drug discovery including virtual screening, molecular docking, ADMET prediction, lead optimization, and integration with AI/ML methods. Covers both structure-based and ligand-based approaches. Use when ", " mentioned.

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

The art and science of creating AI-powered digital presenters, avatars, and synthetic spokespersons. This skill covers HeyGen, Synthesia, D-ID, Tavus, and the emerging landscape of photorealistic AI humans that can speak any script in any language. Digital humans aren't replacing human presenters—they're enabling scale that humans can't achieve. A product demo in 50 languages. Personalized video messages for thousands of customers. 24/7 customer support with a friendly face. Training videos that can be updated without reshoots. The practitioners of this skill understand both the power and the responsibility. They know when digital humans enhance experiences and when they feel uncanny. They navigate the ethics of synthetic media thoughtfully. They create AI presenters that feel helpful, not deceptive. Use when "digital human, AI avatar, AI presenter, HeyGen, Synthesia, D-ID, Tavus, synthetic, talking head AI, AI spokesperson, personalized video, video at scale, multilingual video, AI actor, digital-humans, avatar, ai-presenter, synthesia, heygen, d-id, synthetic-media, personalization, multilingual" mentioned.

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

The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.

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

Expert guidance on authentication implementation including OAuth 2.0/OIDC, JWT tokens, session management, and secure password handling. Covers both implementing auth from scratch and integrating auth providers. Use when "implement authentication, oauth login, jwt tokens, session management, social login, password reset, multi-factor auth, refresh tokens, Working with Auth0, Clerk, NextAuth, Passport.js, authentication, oauth, jwt, session, security, login, password, mfa, oidc" mentioned.

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

The enhancement layer for AI-generated content. This skill covers AI-powered visual effects, compositing, upscaling, restoration, and post-production magic—turning raw AI output into polished, professional content. AI generation gets you 80% of the way. Visual effects get you the remaining 20% that separates "clearly AI" from "how did they do that?" This skill covers ComfyUI workflows, Runway's AI tools, intelligent upscaling, rotoscoping, color grading, and the integration of AI elements into traditional footage. The practitioners of this skill are technical artists who understand both traditional VFX workflows and the new AI-native approaches that are revolutionizing post-production. Use when "AI visual effects, VFX, upscale, upscaling, composite, rotoscope, background removal, color grade, inpaint, outpaint, style transfer, enhance, ComfyUI, post-production AI, vfx, visual-effects, compositing, upscaling, post-production, comfyui, enhancement, color-grading" mentioned.

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

Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.

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