778 件 ・ 関連度順
概要と使いどころ
Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.
日本語の概要は準備中です。原文の説明を表示しています。
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or es
日本語の概要は準備中です。原文の説明を表示しています。
Secure AI coding agents (Claude Code, Cursor, Codex, Copilot) with permission boundaries, secret protection, code review gates, and safe sandbox configurations for team environments.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "write SEO content", "draft a blog post / landing page", "update outdated content", or "fix traffic/ranking decay"; two modes — new drafts pages with keywords, headers, snippets, and evidence boundaries; refresh scores decay, prioritizes update work, and produces a republish plan with GEO guidance. Not for AI-citation/GEO readiness scoring — use geo-content-optimizer; not for publish-gate scoring — use content-quality-auditor. SEO文章写作/内容更新/排名恢复
日本語の概要は準備中です。原文の説明を表示しています。
Ensure designs define data flow, state ownership, consistency boundaries, and cross-boundary writes to prevent drift and incidents.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture diagrams are readable, consistent with text, and clear on scope, boundaries, and data flow.
日本語の概要は準備中です。原文の説明を表示しています。
Detects route data fetched in useEffect instead of loaders, server/client API leaks across loader boundaries, and missing HydrateFallback in React Router v7 framework mode.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture docs define bounded contexts, ownership, and a consistent ubiquitous language to prevent domain drift and coupling.
日本語の概要は準備中です。原文の説明を表示しています。
Detect breaking API contract changes, DTO modifications without compatibility handling, and missing tests for changed API boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Create a non-explicit romantic scene from authorized adult references with clear consent, identity boundaries, and synthetic-media labeling.
日本語の概要は準備中です。原文の説明を表示しています。
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
日本語の概要は準備中です。原文の説明を表示しています。
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
日本語の概要は準備中です。原文の説明を表示しています。
Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Create a bookkeeping context profile before downstream bookkeeping work. Captures entity type, tax jurisdiction, accounting method, chart of accounts baseline, connected tools, approval thresholds, record-retention policy, and review boundaries. Trigger on "set up my bookkeeping", "bookkeeping context", "chart of accounts", "cash or accrual", "configure my books", "what info do you need before bookkeeping".
日本語の概要は準備中です。原文の説明を表示しています。
Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and reviews mobile architecture across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers state ownership, data flow, modules, dependency boundaries, navigation, offline data and KMP shared source sets versus host apps. Use when structuring a feature, choosing state management, refactoring layers or deciding where a real class or screen belongs.
日本語の概要は準備中です。原文の説明を表示しています。
Integrates and reviews Firebase across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers Auth, databases, Storage, Functions, FCM, Analytics, Crashlytics, Remote Config, App Check and KMP shared-to-platform SDK boundaries. Use for any Firebase setup, bug, security rule, emulator, configuration file or product integration.
日本語の概要は準備中です。原文の説明を表示しています。
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
日本語の概要は準備中です。原文の説明を表示しています。
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that must follow AGENTS.md, POLICY.md, focused reproducer-first debugging, strict DRY/OOP boundaries, English comments, GOEXPERIMENT=runtimesecret test discipline, Makefile-driven validation, prompt-sync checks, and dirty-tree preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
日本語の概要は準備中です。原文の説明を表示しています。
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
日本語の概要は準備中です。原文の説明を表示しています。
Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.
日本語の概要は準備中です。原文の説明を表示しています。