「perf」の検索結果

Scan social platforms for top-performing content by engagement before you create anything. Use this skill when the user wants to see what content is winning in a niche, find viral content patterns, research what's working on YouTube/TikTok/X/Reddit, benchmark engagement, discover content gaps, or says "what content is working for [topic]", "show me top performing content about [keyword]", "what's trending in [niche]", "find viral content about [product]", "content research for [keyword]", "what gets views in [niche]", "engagement analysis for [topic]", "scout the competition", "what videos are getting the most views about [keyword]", "social listening for [topic]", "trending content in [niche]", "top content analysis", "what hooks work for [keyword]", "content intelligence", "find winning formats".

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

Performs comprehensive codebase analysis covering architecture, code quality, security, performance, testing, and maintainability. Use when user wants to audit code quality, identify technical debt, find security issues, assess test coverage, or get a codebase health check.

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

Dung khi can danh gia CON NGUOI trong team marketing dua tren du lieu — KPI scorecard theo tung vai tro writer, designer, media buyer; diem manh co vi du that; diem can cai thien; development plan 30-90 ngay; rubric cham 1-5. Kich hoat khi user nhac 'danh gia nhan vien', 'performance review', 'review nhan su', '1:1 review thang', 'nguoi nay lam duoc khong', 'co nen tang luong khong', 'feedback cho team member'. Khong dung cho — tong ket mot campaign thay vi con nguoi thi dung skill 63-campaign-retrospective; duyet chat luong mot output cu the thi dung skill 62-marketing-review; giao viec va dat deadline thi dung skill 64-team-brief.

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

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`.

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

Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.

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

Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see `15-social-listening-global`; diagnosing weak performance numbers, see `03-performance-eval-global`; the routine post-campaign review, see `63-campaign-retrospective-global`.

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

Use when published content has to be audited — pull channel data, classify winners and losers by percentile across pillar, format, and hook, find the pattern behind performance, and decide what to keep, kill, or scale. Trigger on 'content audit', 'which posts are working', 'content performance review', 'why did that one go viral', 'our reach is dropping', 'evaluate what we posted last month'. Also use when the user only says content does not seem to work anymore. Not for — the plan for next period built on these findings, see `40-next-content-plan-global`; paid ad account review, see `21-ads-audit-global`; the stakeholder report, see `07-marketing-report-global`.

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

Use when marketing numbers look bad and the user needs to know WHY — layered root-cause diagnosis across tracking, delivery, creative, landing page, offer, and audience quality, 5-Whys, regional benchmarks for US, EU, SEA, and LATAM, and a 48-hour action plan. Covers dropshipping ROAS and BE-ROAS. Trigger on 'why is CPA so high', 'my ads are not converting', 'ROAS dropped', 'we are burning budget', 'performance is bad this month', 'diagnose the funnel'. Also use when the user pastes a screenshot of numbers with no question attached. Not for — auditing account configuration and scoring health, see `21-ads-audit-global`; writing a report someone else reads, see `07-marketing-report-global`; turning a raw export into insight, see `13-data-analysis-global`.

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

Use when a WINNING ad has to be scaled without breaking it — readiness checks, vertical scaling at plus 20 to 30 percent per step, horizontal scaling into new audiences, creatives, and channels, learning-phase reset risk, how Advantage+ and Performance Max behave when scaled, creative refresh cadence, and the signals that mean stop. Trigger on 'scale ads', 'increase the ad budget', 'scale a winner', 'CPA went up after I scaled', 'how fast can I scale', 'it worked at 50 a day and broke at 200'. Not for — fixing an account that is not working yet, see `03-performance-eval-global`; warm audience plans, see `56-retargeting-plan-global`; proving the winner first, see `19-ab-test-setup-global`.

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

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.

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

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

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

Use when the user asks for a slideshow, presentation, pitch deck, or interactive deck, or to convert an existing page into a deck. Authors a HyperFrames deck with fragments, branching and presenter mode; unclear -> /hyperframes.

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

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

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

Clone any website into a pixel-perfect single-file HTML prototype. Extracts design tokens, assets, CSS computed styles, interaction patterns, and content via Playwright. Outputs a self-contained HTML file with real data injection. Use when the user wants to clone, replicate, reverse-engineer, or create a pixel-perfect copy of any website or web app. Provide one or more target URLs as arguments.

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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

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

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

Optimize React Native rendering for smooth 60fps mobile experiences. Use when optimizing React Native app performance, reducing re-renders, or fixing frame drops.

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

Enforce universal standards for high-performance development. Use when profiling bottlenecks, reducing latency, fixing memory leaks, improving throughput, or optimizing algorithm complexity in any language.

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

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.

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

Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements. Use when the user asks about analytics, website metrics, traffic analysis, conversion rates, user behavior, or performance optimization.

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

Optimize SQL query performance through EXPLAIN analysis, indexing strategies, and query rewriting for PostgreSQL, MySQL, and SQL Server. Use when debugging slow queries, analyzing execution plans, or improving database performance.

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

Manage Linux systems covering systemd services, process management, filesystems, networking, performance tuning, and troubleshooting. Use when deploying applications, optimizing server performance, diagnosing production issues, or managing users and security on Linux servers.

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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