「rop」の検索結果

Property-based testing strategies, mutation testing, shrinking, and combined PBT+mutation workflow for test quality validation

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

Monthly, browser conditional. On its first run it discovers the member's properties from the sites they name, writes the three strategy files, creates every ledger and folder the kit reads, files the opening cards, and registers the eight scheduled jobs. Every month after that it re-reads the evidence rather than its own previous conclusions, rebuilds the topic map and the internal link map, corrects any property fact it can prove wrong, and records every change with the path of the evidence that forced it. It holds publishing and spending unless you released the channel, and it never touches a credential.

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

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.

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

Monthly, on the last weekday, file work only, no browser at all. Folds the decision ledger, scores this Employee's own judgement against the metric files that measured it rather than against its own predictions, appends one outcome line per closed decision, retires a move proposed three times and never accepted, and rewrites the priorities where the evidence disagrees with them. It refuses to publish a calibration figure on too few closed decisions, changes nothing outside its own folder, proposes nothing to anybody, sends only where you released the channel, spends only where you released it, and never touches a credential.

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

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 one master design has to become every size a campaign needs — feed, story, reel, cover, and ad placements: the standard size matrix, three strategies of scale-and-crop, re-compose, or rebuild, safe-zone rules, platform crop behavior, and file naming. Trigger on 'resize this design', 'all the sizes', 'adapt to other placements', 'safe zone', 'standard size chart', 'the text gets cut off in stories'. Also use when one visual exists and six placements are waiting on it. Not for — the original concept brief, see `42-image-brief-global`; production steps in Canva or Figma, see `45-design-tool-brief-global`; the full campaign asset list, see `41-campaign-asset-list-global`; an urgent new creative, see `48-quick-visual-brief-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`.

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

用于配置 Visual Studio 属性表（.props），通过设置绝对路径解决项目引用后 DLL 运行时找不到的问题，且不修改全局环境变量，实现引入即用。

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

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

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

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

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

Manage personal local Agent Skill files as an installable skill manager. Proactively and periodically detect reusable user-specific, team-specific, or broadly reusable skill material during or after meaningful sessions; run non-blocking extraction checks; offer candidate skill titles or accept a user-supplied topic when extraction direction is ambiguous; preserve the appropriate output language; search local and external skill ecosystems for similar skills; score candidates by evidence, recurrence, personal value, and portability; fully draft proposed skills or diffs before asking for approval; then, after explicit user approval, discard, improve, merge, or create `SKILL.md` folders.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Start a safe, governed autonomous loop from a plain-language goal. Use when the user says /coco-loop, "run an autonomous loop", "keep my build green for N hours", "work on X autonomously for a while", or wants a bounded self-improving loop that proposes fixes and never commits on its own. Turns a vague goal into a readable charter the user confirms, then arms and runs the loop propose-only under the coco-loops governance framework.

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

Implement Pages Router data fetching with getServerSideProps, getStaticProps, and API routes in Next.js legacy projects. Use when working in a pages/ directory project, adding SSR/SSG data fetching, or creating API routes.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

시스템이 학습한 사용자의 디자인 취향을 한 뷰로 렌더. .omd/preferences.md + foldin-proposal.json + DESIGN.md를 읽어 반영됨/대기 중/보류됨/모르는 것 4그룹으로 보여준다. '/omd-taste', '내 취향 보여줘', '취향 현황', 'what are my preferences', 'show my taste', 「私の好みを見せて」, 「顯示我的偏好」류의 발화에 트리거. 기록은 omd:remember, DESIGN.md 반영은 omd:learn.

Property-based testing (PBT) patterns with fast-check (JS/TS), Hypothesis (Python), and gopter (Go). Generate random inputs, define invariants, shrink failures to minimal cases. Adapted from Trail of Bits. Use when testing pure functions, parsers, serializers, state machines, or any code where example-based tests miss edge cases.

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

Provides design token system and theming framework for consistent, customizable UI styling across all components. Covers complete token taxonomy (color, typography, spacing, shadows, borders, motion, z-index), theme switching (CSS custom properties, theme providers), RTL/i18n support (CSS logical properties), and accessibility (WCAG contrast, high contrast themes, reduced motion). This is the foundational styling layer referenced by ALL component skills. Use when theming components, implementing light/dark mode, creating brand styles, customizing visual design, ensuring design consistency, or supporting RTL languages.

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

When distributing traffic across multiple servers or regions, use this skill to select and configure the appropriate load balancing solution (L4/L7, cloud-managed, self-managed, or Kubernetes ingress) with proper health checks and session management.

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

Implements drag-and-drop and sortable interfaces with React/TypeScript including kanban boards, sortable lists, file uploads, and reorderable grids. Use when building interactive UIs requiring direct manipulation, spatial organization, or touch-friendly reordering.

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

Create cinematic movie poster concepts and final poster images from a user's brief, existing video plan, storyboard, character design, or project context. Use this skill whenever the user asks to generate a film poster, movie poster, key art, campaign poster, teaser poster, title poster, or promotional visual for a video project. This skill proposes several creative directions first when appropriate, defaults to a 3:4 poster ratio when no ratio is specified, and ensures typography, title treatment, imagery, genre, setting, and story tone are coherent and visually inventive.

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

DO NOT INVOKE when the primary request explicitly asks to convert, migrate, modernize, or rewrite a legacy/old-style project to SDK style; use msbuild-modernization. Migration prompts often mention ToolsVersion, explicit Compile/Reference entries, packages.config, or Microsoft.CSharp.targets, but merely reviewing or auditing a file that contains those patterns remains in scope here. USE FOR broad review, audit, lint, or maintainability/correctness checks of project/build files, including custom targets; prioritized cross-cutting findings; discrete anti-patterns; F# ordering/FS0039; cross-platform paths; and focused Import safety verdicts. Review/audit is analysis-only unless fixes are requested. For concrete property/item defects use property-patterns/item-management; use target-authoring for implementation and extension-points for NuGet auto-import/layout discovery. Exclude non-MSBuild systems.

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

Guide for modernizing and migrating MSBuild project files to SDK-style format. USE FOR: converting legacy .csproj/.vbproj with verbose XML to SDK-style, migrating packages.config to PackageReference, removing Properties/AssemblyInfo.cs in favor of auto-generation, eliminating explicit Compile Include lists via implicit globbing, consolidating shared settings into Directory.Build.props. Indicators of legacy projects: ToolsVersion attribute, an Import of Microsoft.CSharp.targets via $(MSBuildToolsPath), .csproj files over 50 lines for simple projects. DO NOT USE FOR: projects already in SDK-style format, non-.NET build systems (npm, Maven, CMake), .NET Framework projects that cannot move to SDK-style.

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

Own MSBuild import and hook discovery. USE FOR: CustomBefore/CustomAfter hooks, ordered wildcard and NuGet auto-imports, control properties, build/buildTransitive packed layout, package ID and file-name matching, per-TFM forwarders, and tracing why assets or hooks are missing, broken, or replaced. An import guard remains in scope when it is one defect in a broader hook/import flow. DO NOT USE for a focused safety verdict on whether one specific Import needs Exists or is an intentionally unguarded package contract; use msbuild-antipatterns. NEVER INVOKE when imports and hook placement already work and the request is only target Inputs/Outputs, incremental skipping, or FileWrites clean tracking; use incremental-build or target-authoring. Exclude props-versus-targets placement and non-MSBuild systems.

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