「native」の検索結果

Systematic process for analyzing and modernizing legacy applications to comply with the 12-Factor App methodology. Covers code analysis, configuration externalization, dependency management, and container/Kubernetes best practices.

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

Shared Python 3.11+ development rules — type safety and the boundary policy for `Any` (ty, native generics, Protocol, TypeIs, Pydantic), layered architecture and SOLID, error handling, security, performance, identifier naming, PEP 723 script dependencies, Rich/Typer output, tooling defaults (uv, ruff, ty, hatchling, pytest), and testing requirements (behavioral coverage, TDD). Activates when any Python skill or agent needs the shared rules for implementation, code review, refactoring, or test authoring.

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

How to determine which backlog backend a project is configured to use, and what to do with the answer. Use when about to call a backend-specific tool, choosing between a GitHub-only and a Beads-native operation, or reporting which store a result came from.

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

GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,cbinsights,clay,clickhouse,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,discolike,dropleads,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,redshift,rocketreach,salesforce,salesforge,….

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

Design, create, or validate saved and transient Vapi voice assistants. Use for new phone or web agents, production system prompts and first messages, saved-versus-transient architecture, model/voice/transcriber selection, multilingual compatibility, existing tool attachment, native call-control tools, assistant hooks, and Create Assistant API validation errors.

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

Select, define, create, inspect, update, attach, detach, and verify reusable Vapi tools through the public API. Use for native call-control tools, supported provider integrations, API Request tools, custom function tools, MCP tools, tool messages, credentials, or configuration-preserving assistant attachment changes.

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

Spawns full Claude Code peer sessions in separate terminal panes and git worktrees, real sessions rather than subagents, each with a directed task and contract brief, monitored and merged by the spawning lead. Detects the environment and uses herdr first, then tmux, then a native claude background agent. Use when work must persist or run beside the current session, needs a separate worktree or permission settings, should remain user-steerable in a visible pane, or when the user asks to spawn, hand off, or parallelize full sessions. Also spawns Codex peers into those panes. Excludes bounded consults and subagent-scale work.

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

Implement Algolia search UIs in Nuxt 3 apps using @atoms-studio/nuxt-swiftsearch — an SSR-first, fully typed alternative to vue-instantsearch.

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

Use when a ChatGPT/Codex Plugin workflow needs to inspect, search, modify, or verify files in the host workspace using the safest native tools available.

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

Use when a ChatGPT/Codex Plugin workflow needs deterministic computation, file processing, repository checks, package inspection, or other work that should be actually executed with host-native Python instead of answered from unverified reasoning.

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

Consults Fable as an independent, read-only reviewer at an effort the caller matches to the question. The calling session (usually Opus, or Haiku) holds the task and escalates one decision point. Use before committing to an interpretation or a substantial piece of writing or analysis, when stuck or not converging, when changing approach, or as a final check on a finished task. Fallback for when the native advisor tool is unavailable. Not for a session already running Fable.

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

Generate platform-native hooks optimized for engagement, curiosity, and audience tension. Use when creating social media hooks, launch post openings, thread starters, video intros, founder story angles, or campaign first lines.

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

Analyze competing products and turn the market gap into credible positioning, messaging angles, and social campaign claims. Use when comparing competitors, writing alternative pages, sharpening product positioning, or planning campaigns against a category narrative.

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

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

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

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

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

Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).

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

Add a new AI provider to agentconfig.org's comparison system. Use when integrating a new coding assistant (e.g., Cursor, Claude Desktop, GitHub Copilot alternative) with proper type system updates, implementation data, UI components, tests, and documentation.

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

Build a 10-component messaging library from your positioning + ICP + competitor aggregate. Produces positioning statement, value propositions, key differentiators, taglines, CTA variants, proof points, messaging hierarchy, status-quo alternatives. Writes to marketing/messaging/messaging.md as the canonical messaging library every downstream content / paid / outbound / lifecycle skill reads. Triggers - "product messaging", "messaging library", "value props", "messaging framework", "build messaging", "messaging components"

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

Run deep research on a single competitor. Produces a dossier with executive summary, position + messaging, status-quo alternatives, key differentiators, pricing position, where-they-win / where-they-lose, threat assessment, and what to watch. Writes to marketing/competitors/MMYY-{competitor-slug}.md. Triggers - "competitor research", "competitive analysis", "research competitor X", "battlecard prep", "analyze [competitor name]

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

Develop positioning strategy with anchor, differentiators, status-quo alternatives, and a positioning statement. Reads from marketing/icp/ICP.md + marketing/competitors/aggregate.md. Writes to marketing/positioning/positioning.md as the canonical positioning every downstream skill reads. Triggers - "positioning", "category definition", "how do we position", "positioning strategy", "anchor + differentiators"

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

Git Context Controller (GCC) v2 — Lean agent memory backed by real git. Stores hash + intent + optional decision notes instead of verbose markdown. Auto-bridges to aiyoucli vector memory when available. Dual mode: git-backed (lean index.yaml) or standalone (markdown fallback). Triggers on /gcc commands or natural language like 'commit this progress', 'branch to try an alternative', 'merge results', 'recover context'.

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

Use whenever the user wants to find, rank, or shortlist directories, listing sites, or launch platforms where they can submit a software product, SaaS, app, tool, or startup — to get backlinks, referral traffic, and launch-day reach. Triggers on "where can I submit my SaaS for launch", "list of Product Hunt alternatives", "directories to get backlinks for our app", "high-authority software listing sites", "where should I list my startup", or "pull submission details for these 8 directory domains", even when described indirectly (we're launching next week, where do we post; how do we get backlinks by listing in directories). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-mcp-directories for MCP-server listings and find-ai-directories for AI-tool / AI-agent / agent-skill listings. Skip finding a firm/agency to hire (use the find-* agency skills), finding products *inside* a directory ("recommend the best CRM"), building a directory site (do-the-work), local/business directories for brick-and-mortar listings, and link-building *services*.

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

Maintain or embed pkg/authclient for portal login, password/TOTP and API-key authentication, native credential transport, configuration parsing, and credential files. Covers authdbctl login wiring; management commands and the admin API have separate owners.

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

Change AuthCrunch refresh/logout HTTP routes, secure cookies, native JSON credential transport, browser Web Locks, continuation pages, fresh login, or cross-tab session coordination.

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