「profile」の検索結果

Dung khi can MO va thiet lap kenh marketing tu con so khong — TikTok Brand, Zalo OA, Fanpage, Instagram Business, Google Business Profile, TikTok Shop, tai khoan email: checklist setup 4 giai doan, thong so ky thuat, lien ket cheo va ke hoach 30 ngay dau. Kich hoat khi user nhac 'thiet lap kenh', 'tao fanpage moi', 'dang ky Zalo OA', 'mo TikTok Shop', 'setup kenh tu dau', 'chua co kenh nao het', 'kenh moi lap nen lam gi truoc', 'mo kenh moi'. Khong dung cho — cau truc tai khoan quang cao thi dung skill 52-account-structure; gan pixel va do chuyen doi thi dung skill 53-tracking-setup; len lich dang bai thi dung skill 01-lich-noi-dung; van hanh email va Zalo broadcast thi dung skill 14-email-marketing.

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

Dung khi doanh nghiep Viet Nam muon ban ra NUOC NGOAI theo duong B2B — ho so nang luc tieng Anh, chon thi truong muc tieu, pitch deck cho buyer, email chao hang quoc te, chuan bi hoi cho thuong mai va kenh Alibaba, Amazon Business. Kich hoat khi user nhac 'xuat khau', 'ban hang nuoc ngoai', 'tim buyer quoc te', 'company profile tieng Anh', 'email chao hang export', 'di hoi cho thuong mai', 'khach nuoc ngoai hoi gia', 'lam sao co don hang xuat khau'. Khong dung cho — tim va nuoi lead B2B trong nuoc thi dung skill 33-b2b-lead-gen; bo tai lieu ban hang va pipeline thi dung skill 71-sales-enablement; chuoi email nuoi duong thi dung skill 14-email-marketing.

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

Use when the user needs to choose and stand up marketing channels and the tech behind them — channel selection scoring, platform-by-platform setup checklists, business account and verification steps, and integrations, with region priorities: US Meta plus Google plus LinkedIn, EU adding Xing, SEA adding TikTok, Shopee, Lazada and LINE, LATAM adding WhatsApp Business and Mercado Libre. Trigger on 'channel setup', 'which platforms should we be on', 'set up Google Business Profile', 'marketing tech stack', 'we are starting from zero on social', 'connect our accounts'. Not for — conversion tracking and pixels, see `53-tracking-setup-global`; ad account hierarchy, see `52-account-structure-global`; the posting plan once channels exist, see `01-content-calendar-global`.

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

Use when paid ad AUDIENCES must be researched and defined before launch — target profile, interest and behavior mapping per platform, audience sizing, cold, warm, and hot tiering, lookalike seeds, exclusions, and ranked targeting hypotheses to test. Trigger on 'audience research', 'who should I target', 'interest targeting', 'Meta audience for this product', 'TikTok targeting ideas', 'my targeting is too broad'. Also use when launch is imminent and the ad set targeting is still empty. Not for — persona and JTBD depth for content, see `09-customer-insight-global`; warm retargeting tiers, see `56-retargeting-plan-global`; where the budget goes, see `54-media-plan-global`; the campaign hierarchy, see `52-account-structure-global`.

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

Use when the user wants SEO growth, AI SEO, GEO/AEO, Google visibility, ChatGPT or Perplexity citations, schema, structured data, llms.txt, programmatic SEO, local SEO, comparison and alternative pages, directory submissions, Product Hunt, G2/Capterra, backlinks, or a site audit. Trigger on 'SEO audit', 'AI search visibility', 'AI citations', 'schema markup', 'pSEO', 'alternative page', 'submit to directories', or 'backlink plan'. Not for first-time Google Business Profile setup, see `11-channel-setup-global`; not for writing the articles themselves, see `36-content-brief-global`.

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

《小红书运营手册 · AI工作台》主页体检和简介改写技能。用于用户想优化主页第一眼、账号简介、昵称、头像描述、置顶笔记、信任感和定位表达时触发。输入可以是主页截图描述、昵称、简介、置顶笔记、账号定位、产品/服务和目标用户。输出主页诊断、问题优先级、简介改写和置顶建议。若用户重点询问内容到私信、购买、预约、体验或成交路径，应使用 xiaohongshu-conversion-path。

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

《小红书运营手册 · AI工作台》成交路径设计技能。用于用户想把小红书内容、主页承接、置顶笔记、评论区、私信和产品/服务转化串起来时触发，重点处理从刷到内容到私信、预约、购买、体验、反馈或成交的路径。适合服务号、产品号、个人 IP、自由职业者和小程序推广。输入可以是账号定位、产品/服务、客单价、用户顾虑、当前内容和转化目标。输出内容分工、信任路径、私信筛选和成交动作。若用户只想改简介、看主页第一眼或优化置顶表达，应使用 xiaohongshu-profile。

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

Optimize React rendering, bundle size, and data flow with profiler-led decisions. Use when reducing re-renders, fixing waterfalls, or deciding whether memoization is warranted in React.

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

Profile and optimize iOS apps with Instruments, memory management, and rendering techniques. Use when profiling iOS apps with Instruments or optimizing memory and rendering.

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

Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.

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

Optimize Android app startup, UI rendering, frame stability, and benchmark performance with Baseline Profiles, Macrobenchmark, and lazy initialization. Use when reducing startup time, diagnosing jank, or measuring rendering; defer Compose state API and test-only questions.

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

Profiles and improves a measured performance bottleneck; retains only verified improvements.

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

Discover the active AWS profile, region, account, and caller identity before SageMaker or AWS work. Use when local AWS context is needed or unspecified; do not use for cloud-agnostic model planning.

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

k6 script templates, load profiles, response time thresholds, SLO validation, and performance testing strategies.

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

Document database implementation for flexible schema applications. Use when building content management, user profiles, catalogs, or event logging. Covers MongoDB (primary), DynamoDB, Firestore, schema design patterns, indexing strategies, and aggregation pipelines.

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

Daily tech product and open-source discovery digest. Fetches today's Product Hunt leaderboard and GitHub Trending top 10, then curates a personalized briefing in the user's preferred language using their memory/profile to highlight items most relevant to them. Use this skill whenever the user says "daily hunt", "今日猎奇", "tech digest", "daily digest", "what's trending", "今天有什么新产品", "PH today", "show me today's launches", "GitHub trending", "今日趋势", "morning briefing", "tech briefing", "daily brief", or any combination asking about Product Hunt + GitHub Trending together. Also trigger when the user asks about new product launches, trending repos, or wants a curated tech news digest. Even casual phrasing like "what's new in tech today" or "有什么好玩的项目" should trigger this skill.

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

Deterministically compact final H3 bodies to the active delivery profile's paragraph budget without deleting prose or changing citation-block order.

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

Use dotnet-diagnostics-mcp for MCP-driven .NET CPU, allocation, GC, and test-host profiling. USE FOR: profiling unit tests or investigating runtime bottlenecks. DO NOT USE FOR: writing test assertions, coverage collection, or precise microbenchmark timing. INVOKES: connect the MCP server, select target processes, collect bounded profiles, and attribute hotspots to source.

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

Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: `jb inspectcode`; `jb cleanupcode`; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally standardizes on another formatter. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Analyze Google Business Profile visibility, geographic grid rankings, local search keywords, and nearby competitors through the standalone Google Maps CLI. Use for local SEO or location-strategy decisions, not ordinary place recommendations.

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

Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit tests in Java code; Write Mockito-first unit tests for Spring Boot services; Avoid unnecessary @SpringBootTest in Spring unit tests; Review Spring Boot slice-free unit test design. Part of Plinth Toolkit

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

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit

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

Use when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. This should trigger for requests such as Review Java code for Quarkus application structure and CDI; Apply best practices for Quarkus configuration and beans; Improve CDI interceptors, events, or programmatic injection in Quarkus; Add virtual-thread configuration or tune CDI lifecycle. ; Review Quarkus CDI bean lifecycle and configuration. Part of Plinth Toolkit

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

Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. This should trigger for requests such as Create DEVELOPER.md; Generate DEVELOPER.md; Maven project documentation; Add Maven documentation; Plugin goals reference. Part of Plinth Toolkit

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