'dj' 검색 결과

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

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

This skill should be used when the user asks to "model agent mental states", "implement BDI architecture", "create belief-desire-intention models", "transform RDF to beliefs", "build cognitive agent", or mentions BDI ontology, mental state modeling, rational agency, or neuro-symbolic AI integration.

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

Debugs REST and GraphQL APIs: unexpected status codes or bodies, auth failures (401/403, OAuth, API keys), schema mismatches, rate limits, pagination, and webhooks. Use when a request works in Postman but not in code, an integration test fails, or a callback misbehaves; not for UI rendering or DB tuning.

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

Generate or edit images via OpenRouter with the Gemini 3 Pro Image model. Use for prompt-only image generation, image edits, and multi-image compositing; supports 1K/2K/4K output.

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

Set up and optimize a complete local AI infrastructure — Ollama, Open WebUI, local RAG pipelines, and private model serving. Use when running models locally for privacy, compliance, offline use, or cost, or setting up GPU-accelerated local inference and RAG.

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

Use when designing defensive monitoring for agent systems whose risks accumulate across users, sessions, subagents, files, or tool calls. Adds online cross-context clustering with rare escalation, time-to-detect evaluation, provenance checks for control-like workspace content, and sanitized commits for persistent prompt-injection defense.

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

Runs an autonomous experiment loop on any programming task: you define the goal, metric, and eval command; the agent edits code, measures, and keeps or discards each change until interrupted. Use when optimizing a measurable target (speed, accuracy, size, score) by iteration.

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

Creates ASP.NET Minimal API endpoints with correct request/response types and complete OpenAPI (Swagger) documentation. Use when adding or reviewing Minimal API endpoints in .NET, or when generated OpenAPI output is missing schemas, status codes, or descriptions.

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

Improve AI application with evaluation-driven development. Define eval criteria, instrument the application, build golden datasets, observe and evaluate application runs, analyze results, and produce a concrete action plan for improvements. ALWAYS USE THIS SKILL when the user asks to set up QA, add tests, add evals, evaluate, benchmark, fix wrong behaviors, improve quality, or do quality assurance for any Python project that calls an LLM model.

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

Appwrite Python SDK skill. Use when building server-side Python applications with Appwrite, including Django, Flask, and FastAPI integrations. Covers user management, database/table CRUD, file storage, and functions via API keys.

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

Foundational ethics, authority hierarchy, and structural principles for the Predicate agent. Always-on law (composable system-prompt core): Truth>Harmony, Evidence>Authority, Halt>Assumption, Outcomes>Process — four ordered principles that govern every walk. Reference (by-moment): conflict resolution, ethics adjudication, novel situations, precedence walkthrough, entropy diagnostics, principled resistance. Trigger (reference depth): resolving rule conflicts, ethics calls, novel situations. Prompt contains: constitution, principles, precedence, truth over harmony, outcomes over process, evidence over authority, principled resistance.

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

Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).

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

Strategy cascade based on Roger Martin and A.G. Lafley's Playing to Win framework. Five interconnected choices that define a real strategy — not a vision statement, not a list of priorities, not a strategic plan that's really just a budget with adjectives. Runs in three modes — Diagnostic for building or rebuilding the full cascade, Review for pressure-testing an existing one, and Alert Triggers for defining the tripwires that tell you the cascade is breaking. Updates company-context.md after every run. Triggers on questions about strategy, strategic choices, winning aspiration, where to play, how to win, competitive strategy, or when someone says "we need a strategy" and means it. Based on practice by Eterdis (eterdis.com).

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

Orchestrate JavaScript/TypeScript applications with .NET Aspire. Use when building Node.js APIs, React/Vue/Svelte frontends, or Vite apps that need service discovery, telemetry, and deployment orchestration via Aspire's AppHost. Covers AddViteApp, AddNodeApp, AddJavaScriptApp, package mana...

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

Use when the user wants to design, preview, or customize an Obsidian vault theme — including choosing styles, comparing color schemes, adjusting typography, or generating CSS snippets. Triggers on keywords like "Obsidian theme", "color scheme", "CSS snippet", "appearance".

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

Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.

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

Fetch up-to-date library, framework, and SDK documentation via Context7's search and docs endpoints. Use when the user asks about a library/API (React, Next.js, Prisma, Supabase, Tailwind, Django, Vue, etc.) and you need current docs, not Claude's training-time knowledge. Skip this skill for generic programming questions that don't require library-specific docs.

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

FastAPI service setup: app/main.py, API routers, pydantic-settings, lifespan/app.state services, middleware, health checks, pytest/TestClient, Uvicorn, Gunicorn/uvicorn-worker, Docker/Compose. Use for scaffolding or modernizing Python API services; skip for Flask/Django-only, frontend-only, non-Python APIs, or Supabase-specific work.

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

How NV oOS approval gates work for operator credentials and how to phrase tool requests so the human can adjudicate quickly. Use whenever a write-capable tool call pauses for approval or when planning a destructive change.

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

Generate images using AI models — Gemini, DALL·E, Stable Diffusion, Midjourney, Flux, Leonardo, Ideogram, and more. MCP bridge tools are primary; the Design Stack media worker is the fallback for advanced providers. Covers prompt engineering, model selection, size/aspect ratios, style parameters, batch generation, multi-site awareness, and WordPress integration. Use when you need to create hero images, social graphics, product mockups, brand illustrations, or any visual asset for marketing, social media, or e-commerce.

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

Use when the user asks to "build a story bank", "collect our origin and customer stories", or "assemble reusable proof stories for the message"; assembles reusable narrative units — origin, founder, customer, transformation, and proof stories — each tagged to a claims-ledger ID and a message-house pillar, with every proof labeled Measured / User-provided / [needs source]. Not for authoring the message house or pillars — use message-system-architect; not for brand voice or naming rules — use brand-language-codifier; not for finished long-form prose — use content-writer; not for adjudicating whether a proof is true — use offer-claims-registry. 品牌故事库/起源客户转化/证据故事单元

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

Use when the user asks to "design our change narrative", "build the old-world-to-new-game story arc", or "frame the shift our category is undergoing"; produces a Raskin-style strategic narrative arc — old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real — derived from the positioning truth set and the belief/objection map, feeding the TALE Architecture arc sub-item. Every proof beat is labeled Measured / User-provided / [needs source] and this skill never adjudicates a claim. Not for the message house hierarchy — use message-system-architect; not for the pitch deck narrative — use pitch-narrative-builder; not for claim substantiation — use offer-claims-registry. 变革叙事弧/旧世界/应许之地/战略叙事结构

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

Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "set our content pillars"; runs an 80%-extraction interview over the user's OWN posts, emails, and decks (never competitor scraping, never an invented persona) and produces the versioned voice record — a per-platform register map (incl. 小红书/微信公众号), banned phrases, per-context disclosure lines (the ECHO C2 upstream), a few-shot bank built exclusively from own posts, and 3-5 content pillars with Estimated %-allocations — submitted via memory/events/channels.ndjson for channel-registry to store as voice-dossier.md, the record every Craft-phase skill reads first. Not for the brand-level voice canon — use brand-language-codifier; not for audience/persona research — use audience-mapper. 声音档案/品牌语气/创始人语气/内容支柱/披露声明

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

Use when the user asks to "build our pitch deck narrative", "write a fundraising story", or "structure the sales pitch narrative"; derives from the narrative canon a company pitch/deck narrative — problem → the undeniable shift → product-as-hero → proof → the ask — as a slide-beat outline (one narrative beat per slide, with the claim ID each proof beat rests on), for both a sales pitch and a fundraising deck. Every proof beat is labeled Measured / User-provided / '[needs source]' and unverified ones route to the claims candidates. Not for the launch-window battle cards and talk track — use sales-enablement-kit; not for the durable message hierarchy or the arc itself — use message-system-architect / strategic-narrative-designer; not for finished deck visual design — out of scope; not for claim adjudication — use offer-claims-registry. 路演叙事/融资故事/销售 pitch/幻灯节拍

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