「develop」の検索結果

Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).

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

API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.

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

Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices

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

Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, an

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

Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonn

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

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.

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

Create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms.

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

Orchestrates Android development tasks including project creation, deployment, SDK management, and environment diagnostics using the `android` command-line tool.

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

Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.

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

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

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

AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.

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

Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review,

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

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: positioning, product launch, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget.

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

Master orchestrator for B2B SaaS content creation and the editorial production system behind it. Use this skill to produce blog articles, whitepapers, case studies, video scripts, newsletters and ghostwritten thought leadership, to develop content strategy, and to run the publishing line itself — content briefs, editorial calendars and production capacity, review and approval workflow, subject-matter-expert access, the style guide, an AI-drafting policy, and a content inventory with owners. Also triggers on: blog, article, case study, whitepaper, newsletter, video script, ghostwriting, content calendar, editorial, thought leadership, content strategy, content brief, content operations, content ops, editorial workflow, managing editor, who reviews this, our content pipeline is stuck, content is stuck in review, content audit, content inventory, content governance, style guide, house style, SME interview, expert interview, freelance writers, AI content policy, how much content can we actually produce.

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

Core firmware context for the Megahub ESP32 project. Use when working on PlatformIO configuration, build scripts, library structure, main.cpp, or general ESP32 firmware development. Covers build system, project structure, common pitfalls, and debugging.

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

Frontend development context for the Megahub project. Use when working on the web-based IDE, Vite build system, Blockly visual programming, Web Bluetooth API integration, JavaScript frontend code, CSS/styles, UI components, or anything in the /frontend/ directory.

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

Develop a short scripted micro-drama from an idea or approved script through character sheets, storyboard frames, animated shots, and a reviewable assembly.

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

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

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

Distill an already-built or near-launch product into one incisive brand kernel — the "reveal" already hiding in its name, story, or the product itself — then build the name, voice, visual identity, and a developer-ready handoff kit around it. This is LATE-STAGE branding: use it when there is a real, thought-through product that is about to launch, or already live but not explained in a way people grasp in an instant. Use whenever the user wants to name or rename a product, find a tagline or slogan, create a brand identity / brand kit / style guide / design system, design a logo, wordmark, palette, or type system, mock up a homepage for a launch, or hand brand assets to a coding agent (Claude Code, Codex, Cursor). Trigger even when the user only says their product needs to "land" or "feel like" something, or that they can't explain it simply yet. Do NOT use for half-baked, pre-product ideas with nothing to excavate — this skill extracts a kernel that already exists; it does not invent one from a blank canvas.

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

テスト品質を動作カバレッジの観点から分析し、クリティカルなテストギャップを特定する。テストファイルの追加・変更時に使用。

型設計の品質と不変性を4軸スコアで分析する。interface, type, class の追加・変更時に使用。

Guides test implementation following the test pyramid (75% unit, 20% integration, 5% E2E), Arrange-Act-Assert pattern, and project coverage thresholds (branches 70%, functions 80%, lines 80%, statements 80%). Covers test naming conventions, test independence, mock and stub patterns, test data management with fixtures and builders, and CI integration. Use when writing tests, reviewing test code, or setting up test infrastructure.

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

機能を保持したまま不要な複雑性を排除し、コードの簡潔性と可読性を向上させる。30行超の関数や3段以上のネスト検出時に使用。

プロジェクトガイドラインへの準拠をチェックし、バグ、スタイル違反、コード品質問題を検出する。PRレビュー時に使用。