1,602 件 ・ 関連度順
概要と使いどころ
Animate a number counting up to its target as it scrolls into view, once. Use for stat/metric blocks to draw the eye to an impressive figure. Honors prefers-reduced-motion (final value shown instantly). Avoid for precise values the user must read while animating, or many counters at once.
日本語の概要は準備中です。原文の説明を表示しています。
Expert patterns for Godot 2D physics including collision layers/masks, Area2D triggers, raycasting, and PhysicsDirectSpaceState2D queries. Use when implementing collision detection, trigger zones, line-of-sight systems, or manual physics queries. Trigger keywords: CollisionShape2D, CollisionPolygon2D, collision_layer, collision_mask, set_collision_layer_value, set_collision_mask_value, Area2D, body_entered, body_exited, RayCast2D, force_raycast_update, PhysicsPointQueryParameters2D, PhysicsShapeQueryParameters2D, direct_space_state, move_and_collide, move_and_slide.
日本語の概要は準備中です。原文の説明を表示しています。
Net asset value (NAV) reconciliation and tie-out for Chinese funds and investment portfolios. Adapts the original nav-tieout skill for A-share holdings, Chinese fund accounting standards, and domestic custody arrangements. Triggers on "A股净值核对", "NAV计算", "NAV tie-out China", "基金净值", "net asset value [fund]", or "portfolio valuation [date]".
日本語の概要は準備中です。原文の説明を表示しています。
Implements a variety of methods for combining p-values in differential analyses of genome-scale datasets. Functions can combine p-values across different tests in the same analysis (e.g., genomic windows in ChIP-seq, exons in RNA-seq) or fo
日本語の概要は準備中です。原文の説明を表示しています。
Privacy-preserving ad measurement with AdAttributionKit (SKAdNetwork's successor) — install and re-engagement attribution, conversion-value strategy under crowd anonymity, and end-to-end postback testing. Use when running paid acquisition beyond Apple Ads, measuring re-engagement campaigns, designing conversion values, or migrating from SKAdNetwork.
日本語の概要は準備中です。原文の説明を表示しています。
Build a brand's messaging hierarchy — taglines, value propositions, key messages, and proof points for each audience. Use when the user says "brand messaging", "messaging framework", "value proposition", "tagline", "brand tagline", "key messages", "messaging hierarchy", "what should we say about our brand", "brand copy foundation", "messaging architecture", "elevator pitch", "one-liner", "brand statement", or needs consistent language across all communications. Also use when messaging feels inconsistent across channels or teams.
日本語の概要は準備中です。原文の説明を表示しています。
Tests whether a scene is structurally worth generating before any shot is prompted — a five-element engine of Goal, Obstacle, Tactic, Reversal, and Value Shift. Use when the user has a scene, sequence, beat outline, or script and wants it audited or strengthened; when a sequence generates cleanly but lands flat and nobody can say why; when shots look good individually but the run of them does not build; or when the user asks 'is this scene working', 'what's weak here', or 'why doesn't this land'. Upstream of prompting — it decides WHICH shots deserve the credits, not how to write them. Pairs with higgsfield-character-design (who the characters are) and higgsfield-shotlist-director (turning the settled scene into shots).
日本語の概要は準備中です。原文の説明を表示しています。
Design irresistible affiliate offers using the Hormozi Grand Slam framework. Triggers on: "create an offer for", "design my offer", "grand slam offer", "make an irresistible offer", "why should someone buy through my link", "offer framework", "value proposition for", "Hormozi offer", "offer stack", "make my offer irresistible", "craft an offer", "what makes my offer different", "offer design", "increase perceived value".
日本語の概要は準備中です。原文の説明を表示しています。
Catalog of high-value award redemptions where points dramatically outvalue cash. Tiered by legendary/excellent/good with current rates, devaluation history, and booking caveats. Includes Oceania and South Pacific plays (Australia, New Zealand, Tahiti, Fiji) and transatlantic business-class sweet spots.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi goi ban chua du hap dan va can dong goi lai — value stack, bonus, bao hanh va dao nguoc rui ro, ly do gap rut co that, cau truc upsell va downsell, dong goi dich vu thanh san pham ban duoc. Kich hoat khi user nhac 'thiet ke offer', 'offer khong convert', 'value stack', 'bonus stack', 'guarantee', 'risk reversal', 'upsell downsell', 'goi coaching', 'khach thay dat qua', 'ban gi thi khach moi mua'. Khong dung cho — chon con so gia va bac goi thi dung skill 17-pricing-strategy; offer MIEN PHI de doi thong tin lien he thi dung skill 70-lead-magnet; viet copy ban offer da chot thi dung skill 05-copy-quang-cao.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the WHAT being sold needs work, not the price and not the copy — core promise, value stack, bonuses, guarantee and risk reversal, honest scarcity and urgency, tier packaging, upsell and downsell paths, and high-ticket or productized service structures. Trigger on 'design an offer', 'irresistible offer', 'value stack', 'add a guarantee', 'my offer is not converting', 'people say it is too expensive'. Also use when traffic and copy are fine and nobody is buying anyway. Not for — the number on the price tag, see `17-pricing-strategy-global`; the ad text selling it, see `05-ad-copy-global`; the page it sits on, see `12-landing-page-brief-global`; the launch sequence, see `59-go-to-market-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a price has to be set or changed — value-based pricing, anchoring, charm pricing, decoy tiers, good-better-best packaging, discount policy, and margin math, with currency psychology for US, EU, SEA, and LATAM plus dropshipping markup and BE-ROAS. Trigger on 'pricing strategy', 'how much should I charge', 'should I raise prices', 'price tiers', 'customers say it is too expensive', 'dropshipping markup'. Also use when the product is not selling and the user suspects price is the reason. Not for — bonuses, guarantee, and value stack around the price, see `31-offer-design-global`; persuasion beyond price, see `16-marketing-psychology-global`; ad budget math, see `10-reverse-kpi-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, on a Friday, read only everywhere. Scores the week from the daily metrics ledger alone, with the screen and the date range beside every number, then writes the ranked paste ready list of what to change in the account next week. Each line names one change, the exact screen, the current value, the proposed value, and the evidence row it came from. It proposes no change it cannot source, it names no action it took because it takes none, and it spends only where you released it.
日本語の概要は準備中です。原文の説明を表示しています。
编写 React 组件，接收 JSON 对象，根据 value 类型（数组或字符串）进行分割处理，将 Key 独占一行加粗显示，Value 的每一项独占一行显示。
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix concrete MSBuild property defects in projects and existing shared-file hierarchies. USE FOR: conditions, defaults, append versus overwrite, last-write-wins values, OS/TFM checks, portable paths, normalization, and reviews centered on those property defects. Property defects in Directory.Build.* remain in scope, including overwritten values across parent/child imports and conditions that run before TargetFramework is set, even when the fix changes import order or moves a property group to .targets. DO NOT USE FOR: placement-only or import-only requests with no concrete property defect, such as discovering shared files or choosing which file owns a target or customization (use directory-build-organization); item operations; target structure; broad reviews without a concrete property defect; non-MSBuild work.
日本語の概要は準備中です。原文の説明を表示しています。
Applies cross-parameter default rules when creating .NET projects with dotnet new, filling gaps consistently without overriding values the user set explicitly. USE FOR: choosing which target framework to pair with native AOT, deciding whether to keep HTTPS when authentication is enabled, recognizing that controllers and minimal-API flags are mutually exclusive, filling unset related parameters during project creation, explaining why a default was applied and ensuring an explicit user value is never overridden. DO NOT USE FOR: creating the project itself (use template-instantiation), finding or comparing templates (use template-discovery and template-comparison), authoring or validating custom templates (use template-authoring and template-validation).
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions, eliminating primitive obsession with domain-specific value objects, leveraging generic type parameters, creating type-safe wrappers, designing fluent interfaces, ensuring precision-appropriate numeric types (BigDecimal for financial calculations), and improving type contrast through interfaces and method signature alignment. This should trigger for requests such as Review Java code for type design; Improve type design in Java code; Fix primitive obsession in Java code; Create value objects in Java code. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
Builds a positioning canvas (competitive alternatives, differentiated value, best-fit customer, category) plus a strategic narrative and sales-pitch storyboard, and grades existing positioning or messaging. Use for 'positioning', 'how do we describe our product', 'messaging', 'our pitch isn't landing', 'category', 'differentiation', 'one-liner', 'value prop', 'old game new game'. Draws on 43 Lenny's Podcast guests incl. April Dunford, Andy Raskin and Arielle Jackson.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when someone wants to articulate, explore, or document their personal worldview, values, or philosophy. Triggers on "articulate my values", "figure out what I believe", "document my philosophy", "write a manifesto", "define my leadership philosophy", "explore my beliefs". Surfaces beliefs through systematic interrogation, identifies tensions, and generates narrative outputs.
日本語の概要は準備中です。原文の説明を表示しています。
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.
日本語の概要は準備中です。原文の説明を表示しています。
Refactoring pass — extracts repeated Tailwind class combos and markup into components, and lifts magic values into design tokens. Use when the codebase has obvious duplication, hardcoded hex values or pixel sizes, or when the user says "clean this up" / "extract components" / "tokenize styles". Invoke when the user asks for extract on their UI, or mentions 'extract' alongside design / UI / frontend work.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to design, improve, or audit a post-signup activation flow to get new users to their first value moment. Activate when activation is lagging, time-to-value feels excessive, or first sessions lack impact.
日本語の概要は準備中です。原文の説明を表示しています。
Perform value engineering analysis using CWICR data. Identify cost-saving alternatives while maintaining function and quality.
日本語の概要は準備中です。原文の説明を表示しています。
Write a developer value proposition that is specific, provable, and free of puffery. Use when the messaging leans on "powerful," "better," "seamless," or "best-in-class," when claims have no proof, or when the same line is supposed to reach both the developer and the buyer.
日本語の概要は準備中です。原文の説明を表示しています。