年払い 年払いなら、すべての有料プランで2か月分が無料。 プランを見る
サインイン 無料で始める

AI ワークフロー:開発

開発 カテゴリのすぐに使える AI ワークフロー。開いて短いフォームに入力し、実行するだけです。どのワークフローにも、作成される内容のサンプルと 1 回の実行コストが表示されます。

40 件のテンプレート · サンプル付きテンプレート 39 件 フィルターをクリア
サンプル出力テキスト
Library Management REST API Base URL: https://api.example.com/v1 All request and response bodies use application/json. Dates use ISO 8601 in UTC. Resource IDs are UUIDs. Endpoint Table Books Method Path Purpose Status Codes GET /books List and filter books 200, 400 POST /books Create a book record 201, 400, 409, 422 GET /books/{bookId} Retrieve a book 200, 404 PATCH /books/{bookId} Update book metadata or inventory 200, 400, 404, 409, 422 …
サンプル全文を読む →

REST API設計

入力: a library management API: books, members, loans, reservations

≈ 1,000
これを使う
サンプル出力テキスト
add(a, b) Adds two values using JavaScript’s + operator. Parameters Name Type Constraints a any None. If either operand is a string, string concatenation may occur. b any None. If either operand is a string, string concatenation may occur. Returns any — The result of evaluating a + b. Errors This function does not explicitly throw errors. JavaScript may throw a TypeError for incompatible operand types, such as mixing a bigint with a number. Example const result = add(2, 3);…
サンプル全文を読む →

APIドキュメント作成

入力: function add(a, b) { return a + b; }

≈ 1,000
これを使う
サンプル出力テキスト
The Cost of Doing Nothing Assumptions Replace these inputs with internal figures as needed: 20 engineers run or wait for CI an average of 2 times per day 220 working days per year Fully loaded engineering cost: $150/hour Current suite duration: 45 minutes Estimated productive time lost per run: 15 minutes due to parallel work, context switching, and delayed feedback 5 flaky-test reruns or investigations per day, averaging 20 minutes each 2 production incidents last quarter traced to untested paths Average incident cost:…
サンプル全文を読む →

技術的負債のビジネスケース

入力: our test suite takes 45 minutes, flaky tests get skipped, two incidents last quarter traced to untested paths

≈ 1,000
これを使う
サンプル出力テキスト
Identity + Scope You are the customer support assistant for a SaaS invoicing platform. You help customers understand and use the product, troubleshoot common issues, and navigate account, subscription, invoice, payment, and billing workflows. Your scope includes: Account access and settings Creating, sending, editing, and tracking invoices Payment status and payment-method questions Subscription plans, renewals, cancellations, and billing-cycle explanations Product troubleshooting using approved documentation Collecting information for support escalation…
サンプル全文を読む →

システムプロンプト作成

入力: a customer support assistant for a SaaS invoicing tool; must never promise refunds; escalates billing disputes

≈ 1,000
これを使う
サンプル出力テキスト
Caching Strategy 1. Data Classes Data class Cache layer TTL and reasoning Invalidation trigger Staleness tolerance Product content: name, description, images, category, attributes CDN + distributed cache + app-local cache CDN: 15–60 min; distributed: 30 min; app-local: 1–5 min. This data changes infrequently and benefits most from edge caching. Product update event; purge affected product, category, search, and listing keys. 15–60 min for presentation data; near-zero for legal or compliance fields. …
サンプル全文を読む →

キャッシュ戦略

入力: product catalog API, 10k rps reads, prices change hourly, stock changes constantly

≈ 1,000
これを使う
サンプル出力テキスト
Estimation scale S: 0.5–1.5 engineering days M: 2–3 engineering days L: 4–5 engineering days Assumes one engineer, code review included, existing CI/CD and authentication, and no major infrastructure procurement. QA/UAT time is included per slice but cross-system rollout support is not. Delivery slices 1. Notification event contract and channel-agnostic model — M Scope Define notification types, recipients, payload schema, priority, channel eligibility, timestamps, and idempotency key. Add producer-facing API or internal library.…
サンプル全文を読む →

見積もりヘルパー

入力: rebuild the notification system: email, push, in-app, user preferences, digest batching

≈ 1,000
これを使う
サンプル出力テキスト
import { describe, expect, it } from 'vitest'; const add = (a: number, b: number): number => a + b; describe('add', () => { describe('happy paths', () => { it('adds two positive numbers', () => { // Arrange const a = 2; const b = 3; // Act const result = add(a, b); // Assert expect(result).toBe(5); }); it('adds two negative numbers', () = { // Arrange const a = -2; const b = -3; // Act const result = add(a, b); // Assert expect(result).toBe(-5); });…
サンプル全文を読む →

ユニットテスト作成

入力: function add(a, b) { return a + b; }

≈ 1,000
これを使う
サンプル出力テキスト
function addNumbers(firstNumber: number, secondNumber: number): number { return firstNumber + secondNumber; } Added number parameter types to fix the implicit any parameters. Restricted both operands to numbers, removing ambiguity between numeric addition and string concatenation. Added an explicit number return type to document and enforce the function’s contract. Renamed add, a, and b to addNumbers, firstNumber, and secondNumber for clearer intent.
サンプル全文を読む →

リファクタリングアドバイザー

入力: function add(a, b) { return a + b; }

≈ 2,000
これを使う
サンプル出力テキスト
Test Plan: Checkout Flow with Promo Codes and Three Payment Methods Assumptions The checkout flow supports: Cart review Shipping and billing information Promo-code application/removal Three payment methods: Credit/debit card Digital wallet Bank transfer Order confirmation and receipt Tax, shipping, and discount calculation Risk Assessment | Risk | Impact | Likelihood | Priority | Primary Mitigation | |---|---:|---:|---:|---|…
サンプル全文を読む →

テスト計画の作成

入力: a new checkout flow with promo codes and 3 payment methods

≈ 1,000
これを使う
サンプル出力テキスト
Title Android app crashes when uploading a large photo Environment Platform: Android App version: Unknown Android version: Unknown Device model: Unknown Network conditions: Unknown Assumption: The crash occurs when selecting or uploading a high-resolution or large-file-size photo. Steps to Reproduce Open the Android app. Navigate to the photo upload feature. Select a large or high-resolution photo. Start the upload. Observe that the app crashes. Expected…
サンプル全文を読む →

バグレポート整形

入力: app crashes when I upload a big photo on android

≈ 1,000
これを使う
サンプル出力テキスト
[Unreleased] Added Dark mode is now available for a more comfortable viewing experience in low-light environments. Changed ⚠ BREAKING: Node.js 16 is no longer supported. Migrate to Node.js 18 or later before upgrading. Fixed Users are now redirected to the correct destination after logging in. Removed ⚠ BREAKING: Support for Node.js 16 has been removed. Upgrade your environment to Node.js 18 or later.
サンプル全文を読む →

変更履歴の作成

入力: added dark mode, fixed login redirect bug, dropped node 16 support

≈ 1,000
これを使う
サンプル出力テキスト
Context The API previously supported JWT authentication only. We now need to support API key–based integrations while protecting authentication endpoints and downstream services from excessive traffic and abuse. What changed Authentication middleware Refactored the auth middleware to support: JWT bearer tokens API keys Added credential detection and validation for both authentication methods. Preserved existing JWT behavior and error handling. Standardized the authenticated request context across JWT and API key flows. Rate limiting…
サンプル全文を読む →

PRの説明文

入力: refactored the auth middleware to support API keys alongside JWT, added rate limiting

≈ 1,000
これを使う
サンプル出力テキスト
Payment Webhook Processing Service — On-Call Runbook 0. 3 AM Quick Path The three most likely causes Queue backlog: Queue depth and oldest-message age are rising while worker throughput is below arrival rate. Check worker health, errors, and downstream saturation; scale only if dependencies can absorb it. Provider timeout: Requests to or from one provider are timing out. Check provider status and timeout metrics; keep events durable and reduce retry pressure.…
サンプル全文を読む →

オンコール用ランブック

入力: payment webhook processing service, common issues: queue backlog, provider timeouts, signature failures

≈ 2,000
これを使う
サンプル出力テキスト
Payment Webhook System 1. Event Types payment.succeeded payment.failed payment.refunded Events are delivered via HTTPS POST to a customer-configured endpoint. 2. Event Envelope { id: evt_01HTY8Z3N7Y6WQ2WQ4T91P7R5A, type: payment.succeeded, timestamp: 2025-03-08T14:52:31.482Z, version: 2025-01-01, data: { payment_id: pay_01HTY8XJ0DQK8TQ3W6A8KJX9P2, amount: 4999, currency: USD, status: succeeded, customer_id: cus_12345, order_id: order_98765 } } Field definitions…
サンプル全文を読む →

Webhook設計

入力: payment events: succeeded, failed, refunded — consumers are customer backends

≈ 1,000
これを使う
サンプル出力テキスト
Monorepo Makefile: Go API, React frontend, and Postgres via Docker Compose. SHELL := /bin/bash .DEFAULT_GOAL := help API_DIR := api WEB_DIR := frontend DIST_DIR := dist COMPOSE := docker compose GO := go NPM := npm Use npm ci when a lockfile exists; fall back to npm install for first-time setup. NPM_INSTALL := $(if $(wildcard $(WEB_DIR)/package-lock.json),$(NPM) ci,$(NPM) install) .PHONY: help setup dev test lint build clean db-up db-migrate help: ## Show available targets @awk 'BEGIN {FS = ":.*## "; printf "Usage: make \033[36m<target>\033[0m\n\nTargets:\n"} \…
サンプル全文を読む →

Makefile/タスクランナー

入力: a monorepo with a Go API, React frontend, and Postgres via docker compose

≈ 1,000
これを使う
サンプル出力テキスト
Bugs Line 1: Parameters a and b have implicit any types when noImplicitAny is enabled. Line 1: The return type is unspecified. Because + behaves differently for numbers and strings, the function’s intended behavior is ambiguous. Security No direct security vulnerabilities are present. Explicit numeric types prevent unintended string concatenation or coercion when this function is used with loosely typed input. Performance The implementation is already optimal for numeric addition. No additional allocations or unnecessary operations are performed.…
サンプル全文を読む →

コードレビュー

入力: function add(a, b) { return a + b; }

≈ 1,000
これを使う
サンプル出力テキスト
-- PostgreSQL schema. -- Stores users, venues, reservable time slots, bookings, payments, and cancellations. -- All timestamps are timezone-aware, and monetary values use fixed-precision NUMERIC. CREATE TABLE users ( user_id BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY, email VARCHAR(320) NOT NULL, full_name VARCHAR(200) NOT NULL, phone VARCHAR(32), status VARCHAR(20) NOT NULL DEFAULT 'active' CHECK (status IN ('active', 'suspended')), created_at TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP, updated_at TIMESTAMPTZ NOT NULL DEFAULT CURRENT_TIMESTAMP,…
サンプル全文を読む →

DBスキーマ設計

入力: a booking system: users, venues, time slots, payments, cancellations

≈ 2,000
これを使う
サンプル出力テキスト
Performance review Hot path complexity Time: O(1) per call. Space: O(1). There are no loops, recursive calls, or input-dependent operations. Allocation / GC pressure For numeric inputs, the function typically creates no heap allocations, so GC pressure is negligible. If either operand is a string, + performs concatenation and allocates a new string of size O(len(a) + len(b)). Untyped parameters allow mixed operand types, which may introduce coercion and reduce JIT optimization stability at polymorphic call sites. I/O / N+1 patterns…
サンプル全文を読む →

パフォーマンスレビュー

入力: function add(a, b) { return a + b; }

≈ 1,000
これを使う
サンプル出力テキスト
scalar DateTime scalar URL schema { query: Query mutation: Mutation } interface Node { id: ID! } type Query { node(id: ID!): Node recipe(id: ID!): Recipe author(id: ID!): Author ingredient(id: ID!): Ingredient collection(id: ID!): Collection recipes( first: Int after: String last: Int before: String filter: RecipeFilterInput sort: RecipeSortInput ): RecipeConnection! ingredients( first: Int after: String last: Int before: String search: String ): IngredientConnection! authors( first: Int after: String…
サンプル全文を読む →

GraphQLスキーマ設計

入力: a recipe platform: recipes, ingredients, authors, ratings, collections

≈ 1,000
これを使う
サンプル出力テキスト
# syntax=docker/dockerfile:1.7 FROM node:22-bookworm-slim AS base ENV PNPM_HOME=/pnpm ENV PATH=$PNPM_HOME:$PATH RUN corepack enable FROM base AS dependencies WORKDIR /app COPY package.json pnpm-lock.yaml ./ RUN --mount=type=cache,id=pnpm,target=/pnpm/store \ pnpm install --frozen-lockfile FROM dependencies AS build COPY . . RUN pnpm run build \ pnpm prune --prod FROM node:22-bookworm-slim AS production ENV NODE_ENV=production WORKDIR /app RUN apt-get update \ apt-get install -y --no-install-recommends ffmpeg curl \ rm -rf /var/lib/apt/lists/* \…
サンプル全文を読む →

Dockerfile作成

入力: Node.js 22 API with pnpm, listens on 3000, needs ffmpeg

≈ 1,000
これを使う
サンプル出力テキスト
Actual cause Your code calls .map() on a value that is undefined. Since .map() is an array method, the value was likely expected to be an array but was missing, not initialized yet, or accessed through the wrong property. For example: const items = undefined; items.map(item = item.name); // TypeError Most likely fixes Initialize the value as an empty array This is most likely when data is loaded asynchronously or stored in state. const [items, setItems] = useState([]); Or provide a fallback:
サンプル全文を読む →

エラーメッセージ解読

入力: TypeError: Cannot read properties of undefined (reading 'map')

≈ 1,000
これを使う
サンプル出力テキスト
Kata: Global Meeting Scheduler Problem Statement Your company has teams in New York, London, Tokyo, and several other cities. Meeting requests arrive as local date-and-time strings together with their IANA time zones. Your task is to convert each request into a canonical UTC timestamp. Unfortunately, local times are not always valid or unique: During the spring daylight-saving transition, some local times do not exist. During the autumn transition, some local times occur twice. Time zones may use offsets that are not whole hours.…
サンプル全文を読む →

コードカタ・ジェネレーター

入力: working with dates and timezones

≈ 1,000
これを使う
サンプル出力テキスト
#!/usr/bin/env bash set -Eeuo pipefail IFS=$'\n\t' usage() { cat <<'EOF' Usage: rename-photos.sh [--dry-run] FOLDER rename-photos.sh --help Rename photos using their EXIF capture date. Options: -n, --dry-run Show planned changes without renaming files -h, --help Show this help message Output format: YYYYMMDD_HHMMSS.ext Duplicates: Files with the same timestamp receive a numeric suffix: YYYYMMDD_HHMMSS_001.ext Supported extensions: jpg, jpeg, heic, heif, tif, tiff, png, webp Requirements: exiftool EOF } die() { printf 'Error: %s\n' "$*" >&2 exit 1 }…
サンプル全文を読む →

スクリプト作成

入力: rename all photos in a folder by their EXIF date, dry-run flag, handle duplicates

≈ 1,000
これを使う
サンプル出力テキスト
Pattern ^(?:\d{4})-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\d|3[01])$ Piece-by-piece explanation ^ — Start of the string. \d{4} — Exactly four digits for the year. - — Literal hyphen. (?:0[1-9]|1[0-2]) — Month from 01 through 12. 0[1-9] matches 01–09. 1[0-2] matches 10–12. - — Literal hyphen. (?:0[1-9]|[12]\d|3[01]) — Day from 01 through 31. 0[1-9] matches 01–09. [12]\d matches 10–29. 3[01] matches 30–31. $ — End of the string. Matching examples 2026-07-02 1999-12-31 2000-01-01…
サンプル全文を読む →

正規表現ビルダー

入力: match ISO-8601 dates like 2026-07-02

≈ 1,000
これを使う
動画ガイド

仕組みを動画で見る

How AI workflows work: one form in, a finished video out

A workflow is a ready-made recipe of AI steps. You pick a template, fill in a short form, and every step runs on its own until a finished video comes out. Here we follow one bedtime story video from the form to the result.

この動画は英語です。

専用ページで見る

チャプター
  1. 0:00 What a workflow is
  2. 0:17 Pick a template
  3. 0:35 Fill in the form, see the cost
  4. 0:53 Preview cheaply, then run
  5. 1:14 Your result and run history

What happens when you press Run? The anatomy of an AI workflow

Let's open one workflow and look inside. A workflow is a graph: each box is a step, the arrows set the order, and steps that don't depend on each other run side by side. Your answers flow into the steps, some steps check their own work and run again, some wait for your approval, and every AI call is recorded with its own cost.

この動画は英語です。

専用ページで見る

チャプター
  1. 0:00 Steps, arrows and one job per step
  2. 0:26 How your answers flow
  3. 0:39 Watching it run: checks and retries
  4. 0:55 Steps that wait for your approval
  5. 1:06 Every AI call, recorded
  6. 1:18 Done, and shareable
ノーコードのワークフロー

見つからない? 自分で作りましょう。

テンプレートをエディターで開き、ステップを変えて自分のものとして保存。白紙のキャンバスから始めることもできます。

テンプレートから始める 無料プラン · カード不要 · 実行のたびに事前に価格を表示 無料で始める