'boundaries' 검색 결과

Guide React and Next.js best practices. Use for component boundaries, data fetching, rendering performance, server/client split, and Vercel-oriented React work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide system design work. Use for requirements, APIs, data models, service boundaries, scalability, reliability, security, and tradeoff analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide architecture analysis and decision records. Use for ADRs, tradeoff review, boundaries, dependencies, data flow, and LocalSetup-compatible design decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React component architecture: production-level ownership, composition, state, error boundaries. Use when implementing, reviewing or testing react component architecture for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test-driven development: production-level red green refactor and boundaries. Use when implementing, reviewing or testing test-driven development for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Next.js architecture: production-level RSC boundaries, routes, metadata, cache. Use when implementing, reviewing or testing next.js architecture for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert approved Stitch exports into accessible React and Vite dashboards with DESIGN.md tokens, TanStack Query data boundaries, responsive layouts, and optional read-only Web3 integrations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Route Google Stitch tasks to the correct imported Stitch skill, with verified MCP tool boundaries, upload safety, and cross-client fallback guidance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Install audited skills from a curated list or GitHub repo path into Codex or Claude Code after selecting the target host. Use when a user asks to list or install a skill, including from a private repo; preserve Codex system-skill boundaries and use an explicit Claude destination for Claude Code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review homework notebooks for completeness, reproducibility, safe execution, and academic-integrity boundaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing electrical schematics, PCB layouts, KiCad projects, or OpenSCAD enclosures — trace geometry, impedance, stackup, DFM/DRC/ERC sign-off, and hardware-software co-design boundaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when validating API input, environment variables, form data, or DB responses at runtime boundaries. Trigger words: バリデーション, 入力検証, Zod, スキーマ, env 検証, 型強制, parse, safeParse, ランタイム境界.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when adding loading UI, Suspense boundaries, partial streaming, or progressive rendering in Next.js 16. Trigger words: ローディング, loading.tsx, Suspense, ストリーミング, streaming, スケルトン, 遅いデータ, 段階表示.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when handling runtime errors, adding error.tsx or not-found.tsx, designing fallback UI, or deciding what to surface to users vs logs. Trigger words: エラー処理, error.tsx, not-found, 例外, フォールバック, エラーバウンダリ, try catch, ユーザー向けエラー, ログ.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when creating routes, pages, layouts, or deciding Server vs Client Component boundaries in Next.js 16 App Router. Trigger words: ルーティング, ページ追加, layout, route, app router, Server Component, use client, dynamic route, generateMetadata.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a change, module, or surface for exploitable defects — trust boundaries, authn/authz, injection, secret exposure, filesystem and network reach, dependency risk. Use when the user asks for a security review, audit, or vulnerability check of concrete code. Not for general code review, lint, or compliance paperwork.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.