「hook」の検索結果

Full instrumentation from day one. PostHog consolidates product analytics + feature flags + error tracking (one platform, one bill). GA4 via GTM (14-step automation, custom dimensions over events, server-side tagging). Sentry (deep error tracking + performance). Stripe (webhook-first with idempotent processing). Listmonk on Coolify (newsletters via Amazon SES SMTP relay). PLG 7-layer framework. Programmatic SEO (5 page types). Incident auto-remediation via Sentry→Inngest pipeline. AI search (GEO) awareness. Local business conversions (phone_click, direction_click, form_submit, booking_click) with CRO patterns for both SaaS and local.

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

Frappe-specific search and discovery guidance for finding benches, apps, remotes, sites, ports, hooks, DocTypes, builder DocTypes, and frontend surfaces quickly. Use when the task starts with locating or classifying Frappe context.

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

Frappe backend guidance for Python and backend-adjacent JavaScript surfaces such as client interaction patterns, hooks, APIs, patches, scheduler logic, reports, and server-side review. Use when implementing or reviewing Frappe backend behavior.

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

Frappe customization-surface guidance covering Custom Field, Property Setter, Client Script, Server Script, Workspace, Web Page, Page, Print Format, Report, Dashboard, Workflow, Role, Notification, Webhook, and related builder/admin DocTypes. Use when choosing or changing Frappe customization layers.

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

Frappe Payments and ERPNext payment workflow guidance for payment gateways, payment requests, subscriptions, invoices, reconciliation, webhooks, and secure checkout flows. Use when work touches payments in Frappe or ERPNext.

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

Mantine v7 component library — theming, styling, hooks, forms, notifications

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

Native WebSocket API patterns, connection lifecycle, reconnection strategies, heartbeat, message typing, binary data, custom hooks

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

Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8

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

Error boundary patterns, fallback UI, reset/retry, react-error-boundary library, React 19 createRoot error hooks

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

SvelteKit full-stack framework - file-based routing, load functions, form actions, server hooks, SSR/SSG, API routes, streaming, progressive enhancement

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

TanStack Form patterns - useForm, form.Field, validators, arrays, linked fields, createFormHook, type safety

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

Apollo Client GraphQL patterns — normalized cache and type policies, queries, mutations with optimistic updates, pagination, fragments, subscriptions, and Suspense hooks

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

MMKV high-performance key-value storage for React Native - synchronous JSI-based reads/writes, encryption, typed hooks, multiple instances, listeners, persistence middleware adapters

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

Xquik REST API patterns for X post search, user and timeline reads, cursor pagination, media downloads, monitors, signed webhooks, and approval-gated X actions

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

Bun-native HTTP framework — routing, TypeBox validation, Eden Treaty, plugins, lifecycle hooks

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

Electron Forge build toolchain -- makers, publishers, code signing, fuses, hooks, CI/CD packaging

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

Vercel AI SDK patterns - providers, text generation, streaming, structured output, tool calling, chat UI hooks, embeddings, and RAG

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

Replicate SDK patterns for TypeScript/Node.js -- client setup, predictions, streaming, webhooks, file handling, model versioning, deployments, and training

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

Stripe payment processing — Checkout Sessions, Payment Intents, subscriptions, webhooks, Connect, customer management, error handling

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

Payload CMS v3 — TypeScript-native headless CMS with code-first collections, hooks, access control, Local/REST/GraphQL APIs, admin panel, and database adapter pattern

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

Open-source headless CMS — content type schemas, REST API, Document Service API, custom controllers, lifecycle hooks, authentication, TypeScript

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

Phase 5 of the feature-pipeline suite. Use this after /fp-iterate prints the M4 stop hook confirming CI is green. Fetches origin/main, runs gaia dev diff to surface any skill-registry changes the PR introduced that are unrelated to its stated purpose (accidental drift), then prints the final pipeline summary including a CI churn report (via /ci-churn). Also invoke standalone whenever you want to audit whether a branch has unexpected registry drift — e.g. before merging any review/meta or cli/ branch, or when a reviewer asks "did this PR touch anything it shouldn't?". Triggers: "check for drift", "drift check", "final summary", "pipeline done", "wrap up the pipeline", "fp-drift", "Phase 5".

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

Phase 3 of the feature-pipeline suite. Run this after /fp-implement has pushed all commits and printed the M2 stop hook. Spawns a sandboxed sub-agent (HEAVIER) in an isolated worktree to run RED/GREEN tests against the PR diff and post a structured review comment. Use when you need an independent agent to verify correctness of implementation changes before CI runs — especially for schema mutations, CLI surface changes, or doc-touching commits. Triggers on: "review the PR", "run sandbox review", "fp-review", "Phase 3", "check the implementation", "validate the changes", "run tests on the PR", or any instruction to verify what /fp-implement just pushed.

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

Phase 2 of the feature-pipeline suite. Use this after /fp-explore has filed issues and printed the M1 stop hook — when you need to turn a set of filed GitHub issues into an approved implementation plan and a draft PR. Triggers on: "plan the fix", "create the branch and PR", "draft the implementation plan", "ready to plan", "fp-plan", "next step after explore", "convert issues to a plan", "plan phase". Reads issueNumbers from state, writes a Problem Statement, opens a feature branch + draft PR, spawns a HEAVIER sub-agent for the numbered plan, and blocks on explicit user approval before writing plan to state. Does NOT write any code — that is /fp-implement.

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