MobX observable state management patterns with mobx-react-lite. Use when implementing reactive client state with observables, computed values, actions, and the observer HOC.
日本語の概要は準備中です。原文の説明を表示しています。
1,608 件 ・ 関連度順
概要と使いどころ
MobX observable state management patterns with mobx-react-lite. Use when implementing reactive client state with observables, computed values, actions, and the observer HOC.
日本語の概要は準備中です。原文の説明を表示しています。
TypeScript Result/Either types for type-safe error handling, railway-oriented programming patterns, error as values
日本語の概要は準備中です。原文の説明を表示しています。
Unistyles 3.0 styling - C++ powered StyleSheet superset with zero re-renders, theming, breakpoints, variants, dynamic functions, runtime values
日本語の概要は準備中です。原文の説明を表示しています。
MMKV high-performance key-value storage for React Native - synchronous JSI-based reads/writes, encryption, typed hooks, multiple instances, listeners, persistence middleware adapters
日本語の概要は準備中です。原文の説明を表示しています。
React Native Reanimated 4 - shared values, animated styles, spring/timing/decay, layout animations, gesture integration, scroll-driven animations, interpolation, worklets, CSS animations
日本語の概要は準備中です。原文の説明を表示しています。
Serverless Redis-compatible key-value store via Upstash REST API -- edge-compatible, automatic JSON serialization, TTL-based caching
日本語の概要は準備中です。原文の説明を表示しています。
Update Pharos funding donations by reconciling inbound transfers, rejecting wallet self-activity and spam, pricing receipt-time value, and appending user-approved rows.
日本語の概要は準備中です。原文の説明を表示しています。
Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` / `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next/<target>/config` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, façade imports, `@prisma-next/postgres/config`, `@prisma-next/postgres/contract-builder`, `@prisma-next/postgres/control`, `@prisma-next/mongo/config`, `@prisma-next/mongo/contract-builder`, `extensions:`, `extensionPacks`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next/extension-supabase`, `@@control`, control policy, managed, tolerated, external, observed, PN-CLI-4002, PN-CLI-4003, PN-CLI-4011.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new standalone skill repo under gaia-research/ from the canonical template set at gaia-research/gaia-research/templates/skill-repo/. Handles the full flow: interactive prompts for all placeholders, fetches templates via the GitHub API, substitutes values, creates the new repo (gaia-research/skill-<name>), writes README.md / SKILL.md / install.sh / .gitignore / LICENSE / powered-by-gaia.svg, makes the initial commit and pushes. Also supports update mode: re-applies the template structure to a pre-existing skill repo and opens a draft PR with the drift. Use when the user says "new skill repo", "bootstrap a skill repo", "/skill-template", "create skill-foo", "spin up a gaia-research skill repo", "template a new skill", "align skill-fuse to the template", or "/skill-template update <repo>". Requires: gh CLI (authenticated with gaia-research org access), python3, git.
日本語の概要は準備中です。原文の説明を表示しています。
Hunts for Cobalt Strike beacon traffic by detecting default stager URI checksum8 values, default Malleable C2 profile artifacts, and default ports/named pipes in HTTP and process telemetry. Activates for requests to hunt Cobalt Strike, detect beacon stager URIs, or find default Malleable C2 indicators.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether a Pulp test earns its place — before writing it, when reviewing one, or when sweeping a subsystem for low-value, duplicated, or mis-routed tests. Applies a four-question authoring gate, a junk-pattern list, a retention bar, and an evidence template for any deletion, and routes kept tests to the right lane (required gate, pr-fast, slow, nightly). Handles "should I add a test for this", "is this test useful", "audit these tests", "reduce test time", "which tests can go", and "move toward functional tests".
日本語の概要は準備中です。原文の説明を表示しています。
How to write source comments, doc comments, and test names/tags that have lasting value — and what to never write. Consult before adding or editing comments in core/**, examples/**, tools/**, test/**, docs/**, or any shipped source. Handles "write a comment", "is this comment ok", "comment hygiene", and keeping new code from adding the breadcrumbs the cleanup stream removes.
日本語の概要は準備中です。原文の説明を表示しています。
Automate App Store & Google Play screenshot generation for Flutter apps. Scans routing and screens, scores high-value marketing screens, generates self-contained mock harness, runs native simulator captures (iPhone 6.9", iPad 13", Android Phone/Tablet), strips alpha channels, and validates exact store resolutions.
日本語の概要は準備中です。原文の説明を表示しています。
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
日本語の概要は準備中です。原文の説明を表示しています。
Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on variable meaning, field naming, derived state, or reference/value identity, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when behavior-preserving frontend refactoring focuses on record, collection, value, responsibility, delegation, or algorithm boundaries, and the selected technique needs family-specific mechanics, risks, and JavaScript/TypeScript/React/Vue adaptation.
日本語の概要は準備中です。原文の説明を表示しています。
Marketing analytics and data-driven optimization for B2B SaaS campaigns. Use this skill when analyzing marketing performance, optimizing conversion rates, running A/B tests, conducting customer research, creating marketing dashboards, building attribution models, analyzing funnel metrics, or storytelling with data. Also triggers on: marketing ops, performance analytics, CRO, A/B testing, data storytelling, customer insights, tracking plan, event taxonomy, UTM taxonomy, GA4 audit, consent mode, instrumentation contract, sample size calculation, minimum detectable effect, test duration, not enough traffic to A/B test, statistical significance, Bayesian vs frequentist, sample ratio mismatch, experiment feasibility, martech stack, marketing tech stack audit, tool consolidation, build vs buy, vendor evaluation, shadow IT tools, ESP/CRM/platform migration, switching cost, cutover plan, suppression list migration, data portability, customer interviews, survey design, sampling frame, non-response bias, how many people should I interview, thematic saturation, voice of customer, jobs-to-be-done, buyer persona research, is this finding real, data enrichment, which enrichment provider should we buy, waterfall enrichment, contact data quality, match rate, our list data is bad, email verification, catch-all domain, accept-all, bounce rate from bad data, B2B data decay, how often should we re-verify contacts, ZoomInfo vs Apollo vs Clearbit evaluation, cost per usable record, where did this list come from, GDPR Article 14 notice, purchased list compliance, suppression screening, TAM list building, demand planning, marketing plan, how many leads do we need, what pipeline target should marketing carry, funnel model, top-down vs bottom-up plan, plan of record, annual marketing planning, quarterly planning, pipeline coverage we have to create, sales cycle lag, our leads cannot close this quarter, carry-in pipeline, scenario planning, conservative moderate aggressive forecast, stretch target, reforecast, re-forecast triggers, assumption register, capacity ceiling, addressable audience ceiling, marginal cost per lead, blended CPL is wrong, we missed plan and nobody knows why, AI policy for the marketing team, AI governance, AI acceptable use policy, which AI tools are we allowed to use, can I paste customer data into ChatGPT, shadow AI, AI use register, human review of AI output, when can we stop reviewing every AI draft, can the agent send on its own, the AI made a mistake now what, pull back AI autonomy, AI evals, our AI vendor changed the model, AI output went out wrong, prompt injection, can our AI read prospect replies safely, lethal trifecta, the AI leaked internal notes, turn off auto-generated ad assets, auto-applied recommendations, AI literacy training, EU AI Act Article 4, duplicate records in the CRM, dedupe before import, which value wins in a merge, CRM cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Engine and Other Machine Assembler — following the specified multi-stage torque sequence for a multi-bolt joint rather than tightening bolts to final value in convenient order, measuring bearing clearance directly rather than confirming free rotation by hand, verifying critical clearances on the actual assembled stack-up rather than trusting individually-in-tolerance components, or testing sub-assemblies before final integration rather than only at final test.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Dental Laboratory Technician — calculating wax pattern dimensions from a die measurement and alloy-specific casting shrinkage, rejecting a restoration built on a flawed impression or scan, verifying occlusal contacts against the articulator-mounted bite rather than sculpting by eye, or prioritizing value over hue when finalizing a shade match.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Butcher/Meat Cutter — computing true cost per sellable pound from a primal's actual cutting yield, allocating a primal's cost across cut categories by relative market value, pricing dry-aged product against its finished (not green) weight, or diagnosing whether a below-average yield traces to cutting spec rather than the animal itself.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Postsecondary Chemistry Teacher — grading a lab report where the numeric result misses the "expected" value but the methodology is sound, distinguishing a conceptual misunderstanding from an arithmetic slip on a problem set, deciding how much procedural freedom to give students on an open-ended lab, or vetting whether a demo/lab procedure is safe to run in this specific room.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Civil Engineer — sizing stormwater detention/drainage systems, checking foundation bearing capacity against a geotechnical report, verifying IBC/ASCE 7 code compliance for site civil work, reviewing construction RFIs against stamped drawings, or evaluating value-engineering changes for safety-margin impact.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Biofuels/Biodiesel Technology and Product Development Manager — deciding whether a lab/bench-scale process is ready to scale up, evaluating feedstock flexibility tradeoffs in process design, pricing a technology's value against regulatory credit pathways (RFS RIN, LCFS CI score), or managing IP strategy for a novel conversion process. Distinct from biofuels-production-manager, which runs an existing operating facility — this role owns R&D and commercialization of new or improved process technology.
日本語の概要は準備中です。原文の説明を表示しています。