63건 · 관련도순
Use when filing an approved task spec as a GitHub issue with a local archive and optional worktree implementer. Don't use for spec drafting without human interrogation and redaction gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user explicitly asks for the Inngest REST API v2, raw HTTP, OpenAPI, API docs, API authentication, or an endpoint that the Inngest CLI does not expose. Covers api-docs.inngest.com, llms.txt, the OpenAPI v2 spec, Bearer authentication with API keys or signing keys, production and local base URLs, raw curl/fetch requests, request-shape discovery, pagination, secret redaction, and when to prefer the `inngest-api-cli` skill instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits whether a machine-readable regelrecht law model is faithful to the LETTER of the wettekst — and strictly separates the wettekst (leading) from the toelichting (Nota/Memorie van Toelichting; explanatory, not a norm). Runs in critical passes per article/lid and detects four deviation classes: toelichting-bleed (a modeled criterion that the letter only states as an open norm, or not at all), missing verbatim elements (a word/condition such as a "tenzij" or a qualifier dropped from the model), wrong legal_basis anchoring (an endpoint hung on a "kapstok"-article while the operative norm lives elsewhere), and verbatim-drift in text: (an ingetrokken/older redaction). Also detects positief-lid vs uitsluitings-lid conflicts and checks the chapeau for an explicit derogation rule ("zo nodig in afwijking van het eerste lid") before judging precedence. Classifies every finding as modelfout (fix), wettekst-gevolg (report, do not fix), or letter-vs-toelichting-question (jurist decides what is leading + revision signal). Use when the user wants to know if a model is "dicht bij de letter", mentions letter vs toelichting/bedoeling, fidelity, "natuurgetrouw", or before trusting feature outcomes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates California-compliant privilege logs for withheld or redacted discovery materials under CCP 2031.240. Use when the user mentions privilege log drafting, California privilege log, CCP 2031.240, attorney-client privilege logging, work product designation, Evid. Code 952/954, CCP 2018.030, redaction logging, meet-and-confer privilege disputes, waiver analysis, common interest doctrine, or asks for help documenting withheld documents. Also trigger on references to Hernandez v. Superior Court, Costco Wholesale, or Wellpoint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reviewing data flows, support macros, refund templates for GDPR/CCPA/HIPAA fit — regime, consent, PII redaction (email, order-id), breach triage. Triggers 'is this GDPR-safe', 'PII redact'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Curação de dados acelerada por GPU para treinamento de LLM. Suporta texto/imagem/vídeo/áudio. Recursos incluem deduplicação fuzzy (16× mais rápida), filtragem de qualidade (30+ heurísticas), deduplicação semântica, redação de PII, detecção NSFW. Escala em GPUs com RAPIDS. Use para preparar datasets de treinamento de alta qualidade, limpar dados web ou deduplicar grandes corpora.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Package an AI skill, prompt workflow, or internal operating habit into a public-ready release with a catchy hook, safe redaction, useful examples, demo tasks, README copy, and launch messaging. Use when preparing a skill for GitHub, social sharing, marketplace submission, documentation, or community feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
- Recover deleted, edited or historical web content using the Wayback Machine and its CDX API, archive.today, Common Crawl… Use when a page is deleted, changed or 404s, checking what a site used to say, finding old team or staff pages, prior pricing, removed posts, pre-redaction wording or old contact details, enumerating every archived URL for a domain, or preserving evidence before it disappears
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts one knowledge article or known-error article from a resolved incident or ticket thread: symptoms as reported, environment, cause exactly as the resolver stated it, resolution steps as performed, workaround with its limits, verification, things tried without effect, related records, keywords and proposed metadata, every statement traced to a ticket note or marked UNKNOWN, with a redaction log and a question list for the knowledge owner. Never decides a root cause, adds a step or publishes. Use when the user asks to "write a KB article from this ticket", "turn this resolved incident into a knowledge article", "draft a known error record for this", "document the fix we just did" or "make this thread into a how-to for the service desk". Do not use for a procedure the team will execute (runbook, operating procedure, playbook), use runbook-drafter instead; for a post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operational guide for the NV oOS assistant export/import track — the canonical nvoos-assistant bundle format (v1), the shared portability engine, its five surfaces (WP-CLI, REST, admin UI, AI tools, backup provider), the Pro blueprint exporter, credential-redaction rules, legacy/blueprint import compatibility, test conventions, and the Content Graph port checklist. Use when extending or debugging assistant export/import, adding a surface, changing the bundle schema, fixing round-trip fidelity, or continuing the portability track ("continue the portability plan", "add assistant export to X").
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and review native presenter classes in WordPress plugins without requiring better-data - converting DTOs or domain objects into REST arrays, admin table rows, JS config payloads, email variables, and public view models with allowlisted fields, context methods, redaction by default, locale/date/number formatting, no DTO mutation, and correct WordPress escaping boundaries. Use when adding FooPresenter, response mappers, admin-row arrays, wp_send_json payloads, rest_ensure_response data, wp_add_inline_script config, or when code returns raw DTOs, WP_Post, WC_Order, get_object_vars, json_encode, or unescaped HTML from controllers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement data handling for Adobe APIs including PII redaction in logs, Firefly content policy compliance, PDF document data classification, and GDPR/CCPA data subject access requests via Adobe Privacy Service. Trigger with phrases like "adobe data", "adobe PII", "adobe GDPR", "adobe data retention", "adobe privacy", "adobe content policy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pino (高速 JSON 構造化ロガー for Node.js、Fastify 標準ロガー) リファレンス。 logger, child logger, log levels (info / warn / error / debug / trace)、transport、 pretty print (pino-pretty)、redaction (機密情報マスキング)、serializers、 async / sync logging、ファイル出力、structured logging。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GPU-accelerated data curation for LLM training. Supports text/image/video/audio. Features fuzzy deduplication (16× faster), quality filtering (30+ heuristics), semantic deduplication, PII redaction, NSFW detection. Scales across GPUs with RAPIDS. Use for preparing high-quality training datasets, cleaning web data, or deduplicating large corpora.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements content safety filters with PII redaction, policy constraints, prompt injection detection, and safe refusal templates. Use when adding "content moderation", "safety filters", "PII protection", or "guardrails".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.