「tar」の検索結果

Conduct temperament-based health assessment from Hildegard von Bingen's Causae et Curae. Evaluates the four temperaments (sanguine, choleric, melancholic, phlegmatic), elemental correspondences (air, fire, earth, water), and provides dietary and lifestyle recommendations for rebalancing. Use when understanding constitutional type in Hildegardian terms, experiencing imbalance (fatigue, digestive issues, mental fog) needing holistic guidance, seeking dietary recommendations by temperament, or researching medieval humoral medicine.

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

PHPUnit and Pest patterns for any PHP project: test structure, naming, data providers, test doubles (mocks/stubs/fakes), fixtures, and coverage targets. Stack-agnostic — referenced by every PHP plugin in the marketplace. Use this skill to: - Structure unit and integration tests with PHPUnit or Pest consistently. - Drive cases with data providers / datasets instead of copy-pasted test bodies. - Use test doubles with discipline — mock collaborators, not the system under test. - Set up and tear down fixtures cleanly and aim for a meaningful coverage target. Do NOT use this skill for: - PHP language idioms — see php-foundation:php-conventions. - Composer / autoloading — see php-foundation:composer-tooling. - Framework-specific test helpers (Laravel RefreshDatabase/actingAs, Symfony WebTestCase/KernelTestCase) — those are injected by the framework plugin's QA phase.

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

State management and storage choice in React Native. State libs work mostly the same as web (Zustand, Jotai, Redux Toolkit, TanStack Query, Context); storage choice is RN-specific — AsyncStorage, MMKV, SecureStore, Keychain. Hydration patterns, splash screen handling, secrets discipline. Use this skill to: - Pick state management lib (matches web React intuition). - Pick storage by sensitivity (AsyncStorage / MMKV / SecureStore / Keychain). - Hydrate state on app start without UI flicker. - Persist Zustand store across app restarts. - Avoid storing secrets in plaintext storage. Do NOT use this skill for: - General project conventions (see rn-conventions). - Platform-specific code (see rn-platform-specific). - Navigation (see rn-navigation). - Testing state/storage (see rn-testing).

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

Use when writing a GNU ld script for a bare-metal target, placing code in a flash or RAM region, wiring .data and .bss startup, or fixing a region overflowed error. Not for LTO: use linkers-lto.

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

Use when writing CMakeLists.txt, out-of-source builds, target_link_libraries, target properties, find_package/FetchContent, toolchain files, CPack, CMake presets, or cmake configure errors.

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

Resolve a known Odylith anchor after startup, never in parallel with startup.

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

Run the repo-local Odylith startup contract first, before context/search fan out.

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

Use first, before context/search fan out, when a task needs repo-local Odylith startup grounding.

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

Use after startup, never in parallel with startup, when a known Odylith anchor needs local context.

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

应用从 AI for Everyone 蒸馏出的「从小处着手+寻找伙伴 — AI入门的行动原则」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to start-small-find-partner.

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

Compress any conversation into a portable JSON context graph for handoff to a new chat or LLM. Trigger on: "compress this chat", "save context", "new chat", "hand off", "transfer context", "too many tokens", "start fresh", "export conversation", "context graph", "continue in new session". Also trigger proactively when the user mentions starting over in a long session.

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

Evolution CMS JP Editionの開発タスクを実行するためのワークフロー、コマンド(/work, /start-session等)、およびコーディング規約ガイド。開発作業を開始する際に使用します。

Implement masked modal routes in NowStack Mobile web-app. Use for TanStack Start route masks, shareable detail URLs, back-to-close, and refresh-to-page behavior.

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

Find realistic link prospects with SERP and backlink evidence, discover contact paths via web tools, and draft personalized outreach — with targets saved to .seo/backlink-targets.json for off-page-seo campaigns. Use this skill when the user has a linkable asset (study, tool, guide, template, product page) and wants backlinks, resource-page inclusions, or comparison mentions. Triggers: "link prospecting", "find backlink opportunities", "resource page outreach", "get backlinks for", "link building outreach".

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

Launch a product across 56 platforms — generates all copy, tracks submissions, and guides launch day operations. Use this skill whenever someone wants to submit to directories, get backlinks, launch on Product Hunt or Hacker News, run an AppSumo campaign, or needs help getting their product in front of users. Also triggers on: 'I just built something and want people to know', 'how do I get users', 'where can I submit my SaaS', 'get backlinks for my product', 'multi-platform launch', 'directory submissions', 'startup launch playbook', 'submit everywhere', 'launch across platforms'. This is the operational launcher — it does the work. For high-level launch strategy and phased planning, see launch-strategy.

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

Designs cancel flow UX, dunning email sequences, win-back campaigns, and retention triggers. Covers the full churn prevention lifecycle from early warning signals to 90-day win-back. Use when someone mentions 'churn', 'retention', 'cancel flow', 'dunning', 'win-back', 'users leaving', 'reducing churn', 'keep users', 'customers canceling', 'payment failed', 'failed payments', 'losing subscribers', 'customer retention', or wants to prevent customers from leaving. Even if they just say 'people keep canceling' or 'how do I keep users' — this is the skill. Handles both voluntary churn (unhappy users) and involuntary churn (failed payments). Use this whenever subscription retention is the goal.

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

Use when the user wants to train a reusable face-faithful Soul Character identity on Higgsfield. One-time training returns a reference_id passed to Soul models in higgsfield-generate via `--soul-id`. Use this skill whenever: "train soul character", "create my Soul", "train my face", "make my digital twin", "build me an avatar", "create a character of me", "set up identity for video", "I want my face in generated images", "face-faithful character", "reusable character", "brand character training", "build a character from photos", "soul training", "soul-id create". After training, logs the soul_reference_id to `brand/assets.md`. NOT for: one-shot face swaps (use higgsfield-generate with --image), fictional/non-photo avatars (use higgsfield-generate with a prompt). Requires Higgsfield CLI + Basic plan or higher.

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

Use when the user wants professional brand-quality product images via Higgsfield's mode-specific prompt enhancement pipeline. Entry point for any product visual with a specific format or platform target. Use whenever: "product photoshoot", "lifestyle product shots", "Pinterest pin", "hero banner", "ad pack", "virtual try-on", "studio shot", "carousel images", "Meta ads creative", "model wearing product", "levitating product", "splash shot", "CGI style product", "restyle product image", Shopify image, brand campaign visual. 10 modes: product_shot, lifestyle_scene, closeup_product_with_person, moodboard_pin, hero_banner, social_carousel, ad_creative_pack, virtual_model_tryout, conceptual_product, restyle. Backend assembles the prompt — never call gpt_image_2 directly for product shots. NOT for: one-off images without a product (use image-gen), branded video with avatars (use higgsfield-generate), Soul training (use higgsfield-soul-id). Requires Higgsfield CLI and authed account.

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

Cluster keywords by search intent and map each cluster to an existing or proposed page, with cannibalization detection from Search Console. Use this skill when the user has a keyword list (saved set, brand/keyword-plan.md, GSC export, or seed topic) and needs page targets, content briefs, or a site map for SEO pages — especially before seo-content or seo-machine page generation. Triggers: "cluster keywords", "keyword mapping", "map keywords to pages", "keyword cannibalization", "which page should target".

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

Design, write, and grow editorial newsletters with consistent voice and format. Creates newsletter strategy, templates, and growth playbook. Use when someone wants to start a newsletter, improve an existing one, grow subscribers, write a newsletter issue, plan newsletter content, or set up on Substack, Beehiiv, Ghost, or ConvertKit. Triggers on 'newsletter', 'editorial', 'weekly email', 'subscriber growth', 'newsletter template', 'email digest', 'Substack', 'Beehiiv', 'newsletter strategy', 'newsletter issue', 'recurring email', or 'email content'. Even if they just say 'I want to email my audience regularly' or 'start a weekly email', this is the skill. Covers curated, editorial, and hybrid formats with referral programs, platform guidance, and engagement metrics.

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

Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "create avatar for ad", "Seedance", "Kling", "Veo", "Soul gen", "Nano Banana", "Marketing Studio". Chain with higgsfield-soul-id when user wants a reusable face identity. Owns AI-generated "marketing video" / "brand video" / ad creative. NOT for: training a Soul Character (use higgsfield-soul-id), product photoshoots with mode-specific enhancer (use higgsfield-product-photoshoot), text/TTS, screen-recorded product demos (use marketing-demo), slides-to-MP4 assembly (use video-content), Remotion code (use remotion-best-practices). Requires Higgsfield CLI installed and authed.

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

Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.

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

Structured marketing brainstorming when direction is unclear. Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore approaches', 'help me think through this', 'marketing ideas', 'what campaign should I run', 'where do I start with marketing', 'what's our marketing plan', or 'I have no idea how to promote this'. Explores 2-3 approaches and recommends the best path forward with a specific next-skill handoff. Even vague frustration like 'nobody knows about my product' or 'how do I get users' should trigger this when no specific channel or tactic is mentioned.

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

Provision a zero-config, no-signup, temporary Upstash Redis database for an AI agent with a single POST to https://upstash.com/start-redis, with no account, API key, or SDK setup required. Use when an agent needs scratch Redis right now and the user has not provided credentials, for short-term memory across tool calls, conversation history, a sub-agent work queue, ranked recall, or a quick prototype or demo. Covers idempotent creation and re-fetching credentials, calling the database through the body-style REST API or the official SDKs, and telling the user how to claim it. The database lives 3 days unless the user claims it; not for production data, PII, or secrets.

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