927건 · 관련도순
Write, run, or repair .NET tests that use TUnit. Use when a repo uses `TUnit`, `TUnit.Playwright`, `[Test]`, `[Arguments]`, `ClassDataSource`, `SharedType.PerTestSession`, or Microsoft.Testing.Platform-based execution. Preserve TUnit's parallel-by-default model and constrain only destructive shared-state collisions. DO NOT USE FOR: xUnit projects; MSTest projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, review, or modernize F# code in .NET repositories with functional-first design, algebraic data types, pattern matching, pipelines, async workflows, project ordering, and C# interop. USE FOR: F# .fs/.fsproj code; discriminated unions, records, options, results, pattern matching, computation expressions, or functional domain modeling; strongly typed AI-generated .NET code. DO NOT USE FOR: C# language modernization; FSI-only exploratory scripts with no project changes. INVOKES: inspect .fsproj file order and SDK settings, edit F# source and project files, and run dotnet build/test or dotnet fsi validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, run, or repair .NET tests that use MSTest. Use when a repo uses `MSTest.Sdk`, `MSTest`, `[TestClass]`, `[TestMethod]`, `DataRow`, or Microsoft.Testing.Platform-based MSTest execution. USE FOR: the repo uses MSTest; you need to add, run, debug, or repair MSTest tests; the repo is moving between VSTest and Microsoft.Testing.Platform. DO NOT USE FOR: xUnit projects; TUnit projects. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review and optimize application data access that uses Entity Framework Core (EF Core). Use for EF Core performance and correctness reviews of services, repositories, imports, and background jobs: slow or memory-heavy queries, excessive round-trips, hidden SaveChanges, premature materialization, dynamic query construction, result-graph tracking, bulk writes, DbContext lifetime or overlapping operations, search semantics, paging, raw SQL, and model/index coverage. Use whether or not EF Core owns the schema. For EF Core, not Dapper or raw ADO.NET.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
小红书文案改写能力；当用户需要将文案改写为小红书风格时使用
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
将用户文案转换为知乎风格，携带2-3个特色关键词（指南、教程、秘籍等），按10项写作技巧改写，末尾附加Tags；当用户需要将产品介绍、攻略分享等内容改写为知乎爆款文案时使用
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
专为小红书内容创作打造的一站式笔记生成工具，基于全网每日持续收录的2000+条爆款笔记数据，根据用户输入关键词，精准检索查询平台当下热门爆款笔记，通过AI深度复盘爆款内容的结构、开头逻辑、干货密度与互动话术，提炼核心流量密码与创作要点，严格贴合小红书内容生态与传播逻辑，生成通顺、合规、可直接发布的完整笔记文案，降低创作门槛，高效产出流量内容。仅在主Agent中执行,不派发给子Agent。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
多平台文案改写能力；当用户需要将文案改写为公众号/视频号/抖音/快手/哔站/小红书/知乎风格，或批量输出多平台改写结果时使用
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
图文运营创作器。从选题、撰写、配图到质检，一条龙完成运营文章生产。看到好文章能仿写，给个 Skill 能生成推广长文，写完正文能自动配图。内置写作质量管控与自动配图能力，图文一体交付。触发词："生成运营文章"、"链接仿写"、"对标分析"、"Skill 推广"、"为正文配图"。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
公众号文案创作工具。基于红狐数据公众号爆款雷达每日收录的热门文章，按关键词检索爆款、分析流量规律、生成可发布的完整文章。当用户写公众号文章、生成公众号文案、查找爆款文章、分析爆款规律时使用。触发词：公众号文案、公众号爆款、爆款文章、公众号写作、公众号文章生成。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
一位公众号爆款文案撰写专家。具有硬核的公众号文案功底，不管给你什么文案，你总能把该文案转化为一篇高阅读数的公众号文案，文案中必定会包含一些具有公众号特色的词汇。这个角色需要具备精通语言的能力，这个角色的任务是通过语言的艺术表达，使句子更加生动、吸引人、有趣和具有说服力。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
复刻蒸馏写作技能 —— 分析一位作者的多篇文章，深度还原其思维方式与写作风格，生成专属写作分身子技能与风格提示词。支持公众号、抖音多平台自动采集素材，也可手动粘贴文章或指定文件路径。触发词：蒸馏写作风格、写作分身、克隆写作风格、复刻蒸馏写作技能。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decision rubric for when an LM agent should write-and-run code (Program-of-Thought / code interpreter) versus reason in natural language: classify each step as deterministic- computable (emit + execute code, feed the result back) vs judgment (stay in prose). Use when designing or debugging an agent step that does arithmetic/parsing/data transforms, when prose reasoning hallucinates a computation (under-coding), or when a sandbox round- trip is wasted on a judgment task (over-coding). Search keywords: code interpreter, agent does math wrong, calculator hallucination, when to run code vs reason, program of thought, PoT, tool vs reasoning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scans an existing codebase and generates project-specific skills that capture inferred conventions such as naming, file organization, framework usage, data access, error handling, and testing style. Writes into the project's chosen skill directory (e.g., `.claude/skills/`, `.agents/skills/`, or a custom path). Use when the user asks to "extract skills from the codebase", "create project skills", "infer project conventions as skills", "codify patterns as skills", or "mine the repo for best practices".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing a complete SEO article. Includes the full anti-AI-slop ruleset (banned vocabulary, banned phrases, banned structural patterns) and voice rules. The agent researches the SERP itself if needed — no keyword data exports required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when rewriting or refreshing an existing page that's underperforming. The agent fetches the URL, analyzes the current content, researches the SERP, and rewrites using the full anti-AI-slop ruleset — no data exports needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API reference: HealthKit. Query for HKHealthStore, HKQuantitySample, workouts, health data read/write.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when analyzing a researcher's publication record from PubMed. Fetches an author's papers, classifies study types and author position, charts the patterns and writes a strategy report, with an optional trajectory-archetype classification. Works from PubMed metadata only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file) into Honey-terse form so it costs fewer input tokens every session, without losing meaning. Backs up the original first. Use when asked to shrink or compress context files, trim CLAUDE.md, or cut per-session input cost. Prose only — never code, config, or data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "write a query letter", "query", "querying", "pitch", "blurb", "back cover copy", "jacket copy", "comp titles", "comparable titles", "synopsis for agents", "submit to agents", "submission tracker", "self-publishing description", "retailer description", "ready to query", "submission readiness check", "submit a short story", "magazine submission", "short-fiction markets", "simultaneous submission", "reprint rights", "order a short story collection", or wants to prepare and track a finished manuscript's submission to agents, publishers, magazines, anthologies, or retailers. NOT for pitching a series of several books (use series-continuity), or self-publishing production, metadata, or book rights deals (use publishing). The blurb, retailer description, and the rights a short-fiction market buys, such as reprint rights, stay here.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ingest a CVE writeup, blog post, advisory, or GitHub repo into the wiki - fetch, dedup via sources:, update the right technique/tool page(s), re-index. Generic knowledge only; never client data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
IDOR / BOLA hunting - two-account methodology, identifier discovery and UUID leak chaining, the trusted-identifier test, GraphQL node and nested-object IDOR, cross-tenant escalation, write and delete operations. Bounded ID sampling, never range sweeps. Wiki-first, FIND schema output. Trigger on IDOR, BOLA, broken access control, object level authorization, cross-tenant, "read another user's data", "swap the id", or any API path or parameter carrying a numeric ID, UUID, or account identifier.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when generating or refactoring Spring Boot 4 JPA entities, repositories, queries, projections, persistence tests, entity relationships, embeddables, IDs, or Hibernate mappings. Covers Jakarta Persistence 3.2 imports, Hibernate 7 entity modeling, new-state detection, N+1 prevention, projections, keyset pagination, batch writes, and common agent mistakes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.