'orm' 검색 결과

Frame multi-agent designs through explicit environment, autonomy, information, coordination, commitment, incentive, and verification assumptions. NOT for endorsing multi-agent architecture without need or claiming runtime correctness from conceptual methods.

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

Architecture and systems design for agents that retain bounded state across sessions. Covers durable event history, owned state, derived memory, retrieval indexes, framework evaluation, recovery, deletion, and rebuild behavior. Uses constructed implementation examples and workload calibration rather than universal vendor, latency, similarity, retention, or cost claims. 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).

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

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

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

Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).

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

Apache Airflow DAGs, operators, SLA monitoring, and workflow orchestration. Activate on: Airflow, DAG, operator, sensor, scheduler, task dependency, SLA, backfill, XCom. NOT for: dbt transformations (use dbt-analytics-engineer), streaming pipelines (use streaming-pipeline-architect).

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

Migrate configuration from Bluejay voice AI testing platform to Coval. Use when customer says "migrate from bluejay", "bluejay migration", "import bluejay config", or needs to transfer agents, simulations, metrics, and schedules from Bluejay to Coval.

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

Build or improve a Coval dashboard with metric visualizations backed by real data. Creates new dashboards from scratch or rebuilds existing ones by analyzing usage patterns, metric frequency, and data density. Use when user says "create a dashboard", "build a dashboard", "improve my dashboard", "add widgets", "visualize my metrics", "make a performance dashboard", or "dashboard for my runs".

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

Run the full static analysis suite — ruff lint, ruff format check, pyright type check, auth analysis, license headers, example.env check. Use before committing or to verify code quality after changes.

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

Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

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

Maps intelligence for local SEO: geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification, competitor radius mapping, and LocalBusiness schema generation. Three tiers: free (Overpass + Geoapify), DataForSEO, and DataForSEO + Google. Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", or "SoLV".

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

Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".

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

Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", "single URL", "check this page", "page analysis", or provides a single URL for review.

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

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".

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

Dense UI posture — maximum information density with clear hierarchy. Use when building or reworking admin dashboards, data tables and grids, ops or monitoring views, settings-heavy panels, debug inspectors, state or log viewers, and multi-pane tool UIs someone drives all day.

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

Lean, sharp UI posture — the everyday default for building or redesigning a UI. Use when asked to build or make a page, panel, list, form, or dashboard good, cleaner, or nicer, or for a fast confident refresh where the agent uses its judgment instead of asking for a spec.

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

Use when adding/changing a CMS surface manifest, the site_structure/html_pages_structure framing XML, a CMS context menu/extraSections wiring, or the cms-authoring platform skill. Also use when a new CMS route/tab needs an agent entry point.

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

The watch-fix-rerun method for making an existing platform agent or automated process efficient and correct: baseline its ledger, run one unit yourself, fix the class behind every wasted call, rerun, record. Use when asked to improve, optimize, watch, or 'make efficient' an agent, a sandbox session, a sync job, or any recurring automated process.

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

Platform agent skill and content blocks that teach agents a render block, building the block first if new. Use when asked to create the skill for a render block, skill-ify flashcards or quiz, add content blocks for a block, or add a new render block type. NOT for tool result displays (use create-tool-renderer).

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

The interview primitive for putting open decisions to an owner. Use on 'grill me', 'stress-test this', or 'what do you need from me before you build this', and whenever a plan, scope, spec, vision, or question ledger needs owner rulings. NOT for steps only a human can perform (use a guided session).

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

The gate and path for any question an agent wants Arman to decide. Use when about to ask him anything, ending a turn on a question for him, writing 'needs Arman's decision', marking work blocked on him, or on /ask-arman. NOT for a step only he can perform (use a guided session).

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

The one association system (platform.associations) and schema-qualified table refs. Use when touching an M2M junction table, an associate_*/attach_*/tag_* RPC, FK columns used as tags, a 'things attached to X' list or card, or a PGRST205 / 42703 table-not-found on a bare .from().

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

The staged pipeline that turns any API, provider payload, scrape, or computed result into registered, rendered platform kinds. Use on 'create kinds for X', 'distill X into kinds', 'point yourself at API X', or as a stage (A/B/V/D/C) of a running data-to-kinds run. NOT for consuming existing kinds (use aidream's workflow-io-kinds / matrx-frontend's shape-system).

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

Putting a platform feature on the Board (/board) as an Add-menu item with its real component and full agent surface. Use when adding a feature, record type or 'X on the board', or editing features/board/items/** or a tile body.

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

Locate CCSPlayer_WeaponServices::DropWeapon in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the WeaponPaints gamedata entry "CCSPlayer_WeaponServices::DropWeapon" (symbol CCSPlayer_WeaponServices_DropWeapon). This is a VIRTUAL function — emit the vtable slot, NOT a byte signature. Resolve the CCSPlayer_WeaponServices vtable via RTTI and identify the DropWeapon slot: the body takes a CBasePlayerWeapon handle/pointer, detaches it from the player, spawns the dropped weapon entity and transfers ownership. Verify by xrefs from weapon-drop commands (!!drop) and pickup logic. vtable slots commonly differ between platforms — never assume identical indices. Trigger: CCSPlayer_WeaponServices_DropWeapon, CCSPlayer_WeaponServices::DropWeapon

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