热门技能

gh-pr-description

vercel

Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.

vellum-feature-flag-rollout

vellum-ai

Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.

contacts

vellum-ai

Manage contacts, communication channels, access control, and invite links

sentry-app-setup

vellum-ai

Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity

media-processing

vellum-ai

"Ingest and process media files (video, audio, image)"

thinking-second-order

tjboudreaux

When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

thinking-first-principles

tjboudreaux

When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.

local-ai-agents

microsoft

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the privacy/cost/offline trade-offs. Based on Lesson 17 of AI Agents for Beginners. USE FOR: run an agent locally, offline agent, on-device agent, Foundry Local, Qwen function calling, local tool calling, local RAG, Chroma vector database, local MCP server, privacy-preserving agent, hybrid local and cloud agent, small language model agent, engineering assistant on my machine. DO NOT USE FOR: deploying agents to the cloud at scale (use deploying-scalable-agents / Lesson 16), building your first agent concept (Lesson 01), Foundry (cloud) hosted agents, GPU cluster / server-side inference provisioning.

azure-openai-to-responses

microsoft

testing-course-samples

microsoft

Koristite kada se zatraži validacija, testiranje, smoke-test ili pokretanje

azure-openai-to-responses

microsoft

azure-openai-to-responses

microsoft

azure-openai-to-responses

microsoft

microsoft-docs

microsoft

Kysy virallista Microsoftin dokumentaatiota löytääksesi käsitteitä, opetusohjelmia

concurrent-agents

BuilderIO

How to work safely when many Claude Code and Codex agents share this one checkout at once. Use before editing any file, before concluding someone reverted your work, before any branch operation, and before committing, pushing, or merging — this is almost always relevant here.

client-side-routing

BuilderIO

How to add routes without remounting the app shell. Use when adding a new route, fixing agent sidebar reloads on navigation, or choosing between root.tsx layout and pathless _app.tsx layout patterns.

msbuild-modernization

dotnet

"Guide for modernizing and migrating MSBuild project files to SDK-style format. USE FOR: converting legacy .csproj/.vbproj with verbose XML to SDK-style, migrating packages.config to PackageReference, removing Properties/AssemblyInfo.cs in favor of auto-generation, eliminating explicit <Compile Include> lists via implicit globbing, consolidating shared settings into Directory.Build.props. Indicators of legacy projects: ToolsVersion attribute, <Import Project=\"$(MSBuildToolsPath)\">, .csproj files > 50 lines for simple projects. DO NOT USE FOR: projects already in SDK-style format, non-.NET build systems (npm, Maven, CMake), .NET Framework projects that cannot move to SDK-style."

test-anti-patterns

dotnet

Audit an existing test file or suite and produce a severity-ranked diagnostic report. ALWAYS USE for findings about tests that verify nothing, missing or tautological assertions, swallowed/broad exceptions, flaky or order-dependent tests, duplication, or magic values. Polyglot. DO NOT USE for direct edits: use writing-mstest-tests for supplied MSTest assertions, attributes, or lifecycle, and code-testing-agent for new tests. Do not use for running tests, migration, assertion metrics (assertion-quality), coverage/CRAP metrics, or the testsmells.org catalog (test-smell-detection).

build-perf-diagnostics

dotnet

"Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target/Task Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems."

test-gap-analysis

dotnet

Find or close verified gaps in existing tests. USE FOR: "add missing edge cases", "would tests catch this bug?", weak tests, survived boundaries/guards/ errors, or pseudo-mutation analysis. Polyglot. DO NOT USE FOR: a new suite (code-testing-agent), smells/assertion audits, or an actual mutation tool.

exp-test-maintainability

dotnet

"Detects duplicate boilerplate, copy-paste tests, and structural maintainability issues across .NET test suites. Use when the user asks to reduce repetition, consolidate similar test methods, convert copy-paste tests to data-driven parameterized tests, suggest a better test structure, or identify refactoring opportunities. Identifies repeated construction, assertion patterns, copy-paste methods convertible to DataRow/Theory/TestCase, redundant setup/teardown, and shared infrastructure. Produces an analysis report with concrete before/after suggestions. Works with MSTest, xUnit, NUnit, and TUnit. DO NOT USE FOR: writing new tests (use writing-mstest-tests), reviewing test quality or anti-patterns (use test-anti-patterns), or deep mock auditing (use exp-mock-usage-analysis)."

unity-editor

Besty0728

"Unity Editor control. Use when users want to enter play mode, select objects, undo/redo, or execute menu commands. Triggers: play, stop, pause, select, undo, redo, menu, editor, Unity编辑器, Unity播放, Unity撤销, Unity选择."

unity-optimization

Besty0728

"Project optimization utilities. Use when users want to optimize textures, meshes, or improve performance. Triggers: optimize, compression, texture size, mesh compression, performance, LOD, Unity优化, Unity压缩, Unity性能."

unity-script

Besty0728

"C# script management. Use when users want to create, read, or modify C# scripts. Triggers: script, C#, MonoBehaviour, code, class, method, Unity脚本, Unity代码, Unity创建脚本."