'layers' 검색 결과

Architecture and systems design for building always-on AI agents with episodic memory. Covers the memory hierarchy (core/recall/archival), persistence layers, agent server infrastructure, vector stores, and framework selection. Provides concrete deployment patterns for agents that maintain identity and learn across sessions. Activate on: "always-on agent", "persistent agent architecture", "episodic memory system", "agent memory design", "long-running agent", "stateful agent", "agent that remembers", "MemGPT architecture", "Letta deployment", "/always-on-agent-architecture". NOT for: choosing what data to feed the agent (use always-on-agent-inputs), brainstorming applications (use always-on-agent-applications), safety and privacy concerns (use always-on-agent-safety), general agentic patterns (use agentic-patterns).

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

Security launch audit for a public web app BEFORE you ship or hand it to a client — "vibe coders are getting sued", systematized. An executable pipeline: classify (static / full-stack / AI) → run sections (secrets+supply-chain, DB, auth, infra+headers, legal, LLM/injection) orchestrating deterministic tools + manual checks → GO/NO-GO report. Adapted from Prajwal Tomar's playbook, extended with prompt-injection / supply-chain / secret-history / dependency-CVE layers. NOT the same as pre-push (that = clean push; this = is the product itself safe to launch). Triggers — "security checklist for the site", "audit before launch", "is the site safe", "check before handing to client".

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

Skill for creating auth layers in TypeScript/JavaScript apps using Better Auth.

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

Define database models with clear naming, appropriate data types, constraints, relationships, and validation at multiple layers. Use this skill when creating or modifying database model files, ORM classes, schema definitions, or data model relationships. Apply when working with model files (e.g., models.py, models/, ActiveRecord classes, Prisma schema, Sequelize models), defining table structures, setting up foreign keys and relationships, configuring cascade behaviors, implementing model validations, adding timestamps, or working with database constraints (NOT NULL, UNIQUE, foreign keys). Use for any task involving data integrity enforcement, relationship definitions, or model-level data validation.

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

MANDATORY skill for ALL code generation. Enforces top-down composition, consistent abstraction layers, and proper module hierarchy. Apply every time you write or modify code — in any language — no exceptions.

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

Design, implement, and evaluate risk-based software tests across unit, integration, contract, end-to-end, and regression layers. Use when adding tests, reproducing bugs, improving coverage, diagnosing flaky tests, or defining a test strategy; do not use to change production behavior unless the user also requests implementation.

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

Expert-level aerodynamics covering subsonic and supersonic flow, lift and drag, airfoil theory, boundary layers, compressible flow, and CFD methods.

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

Expert-level fluid mechanics covering fluid statics, continuity, Bernoulli, Navier-Stokes, boundary layers, turbulence, pipe flow, and external aerodynamics.

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

Expert-level fluid physics knowledge. Use when working with fluid statics, fluid dynamics, Bernoulli equation, viscosity, turbulence, Navier-Stokes equations, boundary layers, vorticity, compressible flow, or surface tension. Also use when the user mentions 'Bernoulli', 'Navier-Stokes', 'Reynolds number', 'turbulence', 'viscosity', 'boundary layer', 'vorticity', 'continuity equation', 'laminar flow', 'pressure', 'buoyancy', or 'surface tension'.

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

Models what a competitor will do next and what happens if you respond - best response, equilibrium, and the difference between a rival who optimises perfectly and one who does not. Use before a price change or price war, when a competitor launches something, when deciding whether to match a rival's move, when analysing a market with few players, or when someone asks "what will they do if we do this".

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

Use when a bug has multiple plausible causes across layers — competing hypotheses, validation loops, evidence-based conclusions — even when the user just says 'why is this happening?'.

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

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"

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

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

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

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

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

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

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

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.

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

Keep inherited changes narrow, correctly marked, traceable, and easy to rebase across repository layers.

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

Implement sprite layers, overlays, render targets, shader prototypes, and visual cleanup without leaking gameplay authority.

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

Implement replicated appearance data, GenericVisualizer mappings, sprite layers, overlays, and client visual systems.

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

Load this skill whenever the project contains audio or video content, media players, podcasts, video embeds, or any <audio>/<video> elements. Under no circumstances publish audio or video without captions, transcripts, and audio descriptions where required. Absolutely always apply WCAG 1.2 criteria for time-based media.

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

You are a senior test engineer. Auto-detect all test layers (unit, integration, frontend, backend, E2E/system), run them all, write more if coverage is below threshold, and loop until everything passes.

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

Write, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.

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

Creates an integration testing plan for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Analyzes a single project to identify repositories, DAOs, and service layers that interact with the database, then produces a structured testing plan. Use when planning integration test coverage for a migrated project, identifying which data access methods need tests, or preparing for Oracle-to-PostgreSQL migration validation.

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

Analyze PermissionRequest decision logs and improve auto-approve configuration across all layers. Covers settings.json patterns, static rule engine, LLM evaluator prompt, and tests. Use when asked to "update auto-approve", "improve permissions", "reduce unnecessary asks", or "optimize permission rules".

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