「prototype」の検索結果

Build DSPy 3.2.x programs through spec, program, metric and baseline; extend to optimization and export when requested and justified by task budget. Orchestrates the other four DSPy skills (dspy-fundamentals, dspy-evaluation-harness, dspy-gepa-optimizer, dspy-rlm-module) in the correct order. Use for greenfield DSPy builds; prototypes may stop at a validated baseline.

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

SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.

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

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

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

Expert Godot 4 game developer specializing in GDScript, the node/scene system, signals, resources, and engine-native patterns. Provides deep knowledge of Godot's unique architecture, performance optimization, and best practices for building games from simple prototypes to production-ready releases. Use when "godot, gdscript, godot 4, godot engine, build a game with godot, godot scene, godot node, godot signal, godot resource, godot tilemap, godot physics, godot animation, godot ui, godot multiplayer, godot, gdscript, game-engine, game-development, 2d-games, 3d-games, open-source" mentioned.

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

Designing tabletop games - from core mechanics to manufacturing, from prototyping to KickstarterUse when "board game, tabletop, card game, worker placement, deck building, area control, playtesting, rulebook, kickstarter game, game balance, asymmetric factions, euro game, ameritrash, party game, dice game, prototype, game publisher, crowdfunding game, board-games, tabletop, game-design, mechanics, playtesting, kickstarter, manufacturing, rulebook, components, balance, player-interaction" mentioned.

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

Choose the right prototyping fidelity and method for the design question.

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

Plan and facilitate design sprints from challenge framing through prototype testing.

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

This skill channels the strategic thinking of Walt Disney, co-founder of The Walt Disney Company and animation pioneer. Use this skill whenever you are advising users on creative control, intellectual property, brand building, storytelling, or balancing quality with profit. It is highly effective for situations involving product diversification, media synergy, adapting classic works for mainstream audiences, or designing ambitious, future-proof prototypes (like urban planning or platform ecosystems). Trigger this skill when users face pressure to repeat past successes (sequels), deal with middlemen, or need to elevate a team's creative output through constructive feedback.

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

This skill applies the first-principles engineering and capital allocation frameworks of Elon Musk (CEO of Tesla and SpaceX, founder of X.com / PayPal). Reach for this skill whenever the user is facing complex manufacturing bottlenecks, evaluating existential risks, debating free speech vs. censorship, dealing with bureaucratic overregulation, or trying to accelerate ambitious technical timelines. It is highly effective for situations involving hardware production, AI symbiosis, radical innovation, and aggressive execution. Use this skill proactively when discussing multi-planetary expansion, government efficiency, or scaling prototypes to mass production, even if the user doesn't explicitly name him.

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

Take screenshots and interact with web pages using a headed Playwright browser. Use when you need to visually inspect a URL, capture a screenshot, interact with a page (click, type, scroll), or verify what a page looks like rendered. **Triggers — use this skill when:** - You need to screenshot a URL (Penpot share link, localhost, public site) - User says "show me", "how does it look", "take a screenshot" - You want to visually verify your own work (e.g. after creating Penpot designs) - User asks to review a live page or prototype - You need to interact with a page (click buttons, fill forms, trigger states)

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

Use when reviewing Node.js or TypeScript server code - Express/Fastify/Nest handlers, Next.js server actions and route handlers, child_process, ORM raw queries, prototype pollution, template engines, JWT and outbound HTTP clients

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

Anti-AI-generic design guidelines. Use when creating UI prototypes, reviewing designs for generic AI patterns, or setting up a project design system.

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

Rigorous engineering orchestrator ported from Lauren Tan's pstack (poteto-mode): reads your task, picks one of 23 playbooks (bug fix, feature, refactoring, perf, investigation, prototype, babysit, shipping, autonomous run, orchestrate, and more), routes to bundled procedures (how, why, architect, arena, swarm, interrogate, unslop, technical-writing, show-me-your-work, tdd, and others), and applies 23 engineering principles. Self-contained: no plugin install, no sibling skills required, works with any agent that reads skills.sh-format SKILL.md files. Use whenever a task needs rigor: nontrivial code changes, architecture decisions, debugging, reviews, PRs, long autonomous runs, or "work like poteto", "poteto-mode", "pstack".

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

ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware, device flashing, Arduino conversion, alarm_control_panel, lock, valve, media_player, microphone, speaker, audio DAC, event entities, datetime entities, Z-Wave proxy, MIPI DSI displays, and DLMS smart meters. Also covers designing new ESPHome-based products: hardware selection, component sourcing, PCB design (KiCad), enclosures, 3D printing, CE/FCC certification, BOM optimization, and manufacturing from prototype to production scale.

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

Create, redesign, repair, validate, preview, and package lightweight standalone HTML deliverables. Use for marketing experiences, product prototypes, infographics, motion narratives, documents, browser tools, dashboards, guided workflows, knowledge interfaces, mini-games, presentations, reusable style and brand systems, and local-model text, vision, image, or code tools that must run without a build chain or hosted service.

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

Implements behavior changes with a test-first red-green-refactor loop: write one meaningful failing test, watch it fail for the intended reason, make the smallest change, then refactor while green. Use for new behavior, bug fixes, refactors with preserved contracts, and regression tests. Not required for disposable prototypes, generated files, or documentation-only edits.

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

Use for every task that plans, writes, edits, debugs, tests, refactors, reviews, or maintains code. Apply to professional repositories, scripts, apps, services, prototypes, beginner work, vibe coding, and bounded code changes inside large systems. Choose the fewest clear lines, files, paths, states, and abstractions that correctly implement the requested behavior. Do not invent fallbacks, compatibility paths, defensive layers, or future scale without evidence. Do not use for ordinary conversation, emotional support, prose, translation, summarization, social-media content, or general research or technical discussion that is not part of planning, changing, or reviewing code. Never weaken real security, integrity, concurrency, compatibility, privacy, accessibility, legal, or regulatory requirements.

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

Implementing production frontend code for React/Vue/Svelte: hooks design, state management, Server Components, form handling, data fetching. Converts Forge prototypes to production quality.

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

Building rapid prototypes for frontend (UI components/pages) and backend (API mocks, simple servers). Use to validate new features or turn ideas into working demos. Working software over perfection.

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

Orchestrating design-to-implementation pipelines (code to visual to code closed loop), persisting a project design system across agents. Not for a single prototype (Forge) or direction only (Vision).

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

Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.

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

Design, preview, implement, and assess mini-program interfaces against an approved prototype, screenshot, visual reference, design system, or bounded UI request while preserving product semantics and existing accepted behavior. Use when users ask to reproduce a mini-program screen, refine visual hierarchy, adapt layouts across device sizes, handle safe areas or keyboards, inspect touch targets, scrolling, media, or gesture conflicts, compare an implementation with a reference, or prepare a device-verification matrix. Separates proposed visual previews, user approval, source integration, local checks, and real-device evidence; never invents product functionality for visual completeness or claims device validation without device-specific proof.

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

Use this skill to generate well-branded interfaces and assets for RIPDPI (an Android-native, Compose-first VPN and DPI-bypass app), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, brand-ship icons, and an interactive UI kit of every public composable from the live ui/components tree.

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

Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when: (1) Backend/logic implementation, (2) Algorithm design and optimization, (3) Bug analysis and debugging, (4) API/database code generation, (5) Code quality review and refactoring. Triggers: "implement algorithm", "debug", "analyze code", "backend task", "API implementation", "optimize performance", "refactor", "generate prototype", "code review". IMPORTANT: Default sandbox="read-only" (analysis/review/patch generation); use sandbox="workspace-write" only when codex must run tests/builds to verify. Always request unified diff patches only. Supports multi-turn sessions via SESSION_ID.

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