507 件 ・ 関連度順
概要と使いどころ
Generate architecture and design documents for implemented code changes with risk-based depth selection. Automatically evaluates risk signals, layer spread, and change magnitude to choose documentation level (A/B/C). Use after completing a feature, before merging a PR that touches multiple layers or sensitive areas (auth, infra, migrations, payments), or when an implemented change needs a design record or ADR.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing raw SQL — MariaDB/MySQL syntax, parameterization, raw migrations, seeders with `DB::statement`; fires even on a pasted query asking 'why is this slow'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing a migration diff or schema change for scale hazards — indexes, unsafe migrations, unbounded growth, N+1. Triggers on 'review this migration', 'will this scale'.
日本語の概要は準備中です。原文の説明を表示しています。
[DevOps] Use when you need to run or create database migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Validate database schema, migrations, indexes, and query behavior with structured pass/fail reporting.
日本語の概要は準備中です。原文の説明を表示しています。
把老用户的 .cheat-state.json 升级到当前 schema_version。读 migrations/registry.md 算迁移链，按顺序应用每一步迁移文件。幂等：跑两次结果一样。失败停在中间版本不前进。触发词："迁移"/"升级 state"/"migrate"/"我的 state 是老版本"/"schema 版本不对"。
日本語の概要は準備中です。原文の説明を表示しています。
GStack engineering-manager plan review for architecture, data flow, APIs, migrations, edge cases, tests, performance, release risk, and implementation boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Prisma 8 ORM setup, schemas, queries, migrations, or upgrades. Read the official Prisma 8 skill even if the project has no local copy.
日本語の概要は準備中です。原文の説明を表示しています。
The case-law chronicle of this repo's major failures — symptom, root cause, evidence, status, and the rule each battle minted — so nobody re-fights a settled battle or re-proposes a rejected fix. Use when a bug/incident looks familiar ("didn't this happen before?"), when you're about to propose an approach that may have been tried and rejected (e.g. shipping a migration from a package), when someone asks "why does rule X exist" / "why is done-by-lgtm a thing" / "what was incident 988", or when a bug-archaeology run hits the shallow-clone wall and needs the pre-June-2026 history. Trigger phrases: "has this broken before", "why can't packages ship migrations", "why did graduation fail", "why is the green-build lesson a rule", "what did we learn from incident NN". (For a live "build is green but the app is broken" symptom, start at crouton-diagnostics-index. NB keep this description free of any space-then-hash sequence — an unquoted YAML scalar treats space-hash as a comment start and silently truncates.)
日本語の概要は準備中です。原文の説明を表示しています。
Symptom → root-cause lookup table for nuxt-crouton's recurring failure modes — exact error strings mapped to their known cause, fix, and evidence issue. Use when you hit an error you don't recognize in this repo, before debugging from first principles. Trigger phrases and symptoms: "Cannot resolve entry module .nuxt/hub/db/schema.entry.ts", "Could not load '@fyit/crouton'", "No migrations present", "No schema files found", "$setup.t is not a function", "does not provide an export named 'Map'", "no such table: translations_ui", "collection pages 500 in production", "the build was green but the app is broken", "is this a known issue?".
日本語の概要は準備中です。原文の説明を表示しています。
The migration step and the package-owned-table exception — NOT the normal collection flow. For app collections use the crouton CLI/skill (schema JSON → `crouton config`); reach here when you then need to generate/apply the Drizzle migration and hit the schema.mjs-only-after-build gotcha ("No schema files found"), or when adding a package-owned infra table (the crouton-flow pattern) that does NOT go through `crouton config`.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations. Use when schema changes affect existing data.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate schema + backfill data on a deployed Convex app using @convex-dev/migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate schema + backfill data on a deployed Convex app using @convex-dev/migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations. Use when schema changes affect existing data.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.
日本語の概要は準備中です。原文の説明を表示しています。
Exploratory data-migration validation and QA ideation workflow. Use when you need to discover hidden risks, generate new validation angles, and converge mapping specs/validation reports into a prioritized QA backlog for CRM migrations. Version 2.0, updated 2025-12-28.
日本語の概要は準備中です。原文の説明を表示しています。
Add or change stable public state, contracts, routes, migrations, adapters, rescue behavior, or compatibility-sensitive surfaces through the evolution ledger.
日本語の概要は準備中です。原文の説明を表示しています。
Load when EF Core reads are slow, emit N+1 or excessive SQL, over-fetch, track too many entities, cause high DB load, or need projection/split-query/compiled-query analysis; not for general migrations, DbContext setup, or repository conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Load when working on Tier 0 Sovereign (payments, money, orders), Tier 1 Security (auth, tenancy, migrations), or Tier 2 Privacy (PII, erasure) tasks to enforce advanced model tier, Invariant-Breaker adversarial tests, and zero-PII telemetry validation.
日本語の概要は準備中です。原文の説明を表示しています。
Load for cross-layer refactors, record/class or value-object migrations, new services/interfaces/repositories, project references, dependency-direction failures, or deciding whether code belongs in Domain, Application, Persistence/Infrastructure, API, or Blazor; not for a local edit wholly inside an established layer pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Load for EF Core entities/configurations, semantic value persistence, portable constraints, DbContext/query filters, repositories/specifications, migrations, model snapshots, transactions, or seeded lookup tables; use query-optimization specifically for N+1 or slow SQL diagnosis.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS Dependabot alert triage-and-remediation loop: querying open alerts via gh api, separating stale from genuinely vulnerable lockfile entries (default-branch forensics), deciding between safe in-major override bumps, scoped overrides, or deferred major migrations (npm pack signature diffing), regenerating the 13-lockfile tree, dismissing alerts with the right reason, GitHub issue housekeeping, and triaging the known CI failure modes. Use when asked to fix dependabot alerts, close out dependabot issues, bump vulnerable npm packages, or resume a dependabot session.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "check technical SEO"; audits crawlability, indexing, Core Web Vitals, robots.txt, sitemaps, canonicals, redirects, and migrations. Not for on-page tags or content — use on-page-seo-checker. 技术SEO/网站速度
日本語の概要は準備中です。原文の説明を表示しています。