「net」の検索結果

Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace. Covers adding new content, updating plugin.json, validation, and release tagging.

日本語の概要は準備中です。原文の説明を表示しています。

Design .NET types for performance. Seal classes, use readonly structs, prefer static pure functions, avoid premature enumeration, and choose the right collection types.

日本語の概要は準備中です。原文の説明を表示しています。

Write integration tests using TestContainers for .NET with xUnit. Covers infrastructure testing with real databases, message queues, and caches in Docker containers instead of mocks.

日本語の概要は準備中です。原文の説明を表示しています。

Create and maintain AGENTS.md / CLAUDE.md snippet indexes that route tasks to the correct dotnet-skills skills and agents (including compressed Vercel-style indexes).

日本語の概要は準備中です。原文の説明を表示しています。

Use Verify for snapshot testing in .NET. Approve API surfaces, HTTP responses, rendered emails, and serialized outputs. Detect unintended changes through human-reviewed baseline files.

日本語の概要は準備中です。原文の説明を表示しています。

Test email sending locally using Mailpit with .NET Aspire. Captures all outgoing emails without sending them. View rendered HTML, inspect headers, and verify delivery in integration tests.

日本語の概要は準備中です。原文の説明を表示しています。

Choose the right serialization format for .NET applications. Prefer schema-based formats (Protobuf, MessagePack) over reflection-based (Newtonsoft.Json). Use System.Text.Json with AOT source generators for JSON scenarios.

日本語の概要は準備中です。原文の説明を表示しています。

Guidance for selecting appropriate AI model (sonnet vs haiku) based on task complexity, reasoning requirements, and performance needs. Use when implementing agents or justifying model selection.

日本語の概要は準備中です。原文の説明を表示しています。

Set up OpenRouter as your LLM provider. Guides through account creation, API key setup, config, and making it the default model. Use when a user wants to use OpenRouter models like Claude Sonnet 4.5.

日本語の概要は準備中です。原文の説明を表示しています。

AI-powered diary generation for agents - creates rich, reflective journal entries (400-600 words) with Quote Hall of Fame, Curiosity Backlog, Decision Archaeology, and Relationship Evolution. Generates personal, emotional entries from the agent's perspective. Works best with Claude models (Haiku, Sonnet, Opus).

日本語の概要は準備中です。原文の説明を表示しています。

Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

日本語の概要は準備中です。原文の説明を表示しています。

Read, search, and manage Confluence Cloud pages, spaces, blog posts, comments, attachments, and labels. Use this whenever the user wants to find a page, read a doc, search the wiki with CQL, create or update a page, add a comment, list pages in a space, pull an attachment, or ask "what does the wiki say about X" — even if they don't say "API". Also use it for any *.atlassian.net/wiki URL, or a CQL string when the context is wiki content rather than tickets. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

日本語の概要は準備中です。原文の説明を表示しています。

Expert FinOps guidance for cloud, AI, and SaaS technology spend. Covers AI cost management, agentic FinOps, GenAI capacity planning, self-hosted vs managed inference, Anthropic billing, open-weight vendor APIs (DeepSeek, Qwen, Kimi, GLM), AWS (EC2, Bedrock, SageMaker, Savings Plans, CUR), Azure (reservations, AHB, OpenAI PTUs), GCP (Vertex AI, BigQuery), OCI, Kubernetes cost allocation, data platforms (Databricks, Fabric F-SKUs, Snowflake), tagging governance, SaaS management (SAM, shadow IT), AI coding tools (Cursor, Claude Code, Copilot, Codex), ITAM, allocation, showback, chargeback, anomaly management, KPIs and benchmarking, waste detection playbooks, workload onboarding and M&A, and GreenOps (cloud carbon, CSRD). Use for any question about technology cost or waste in your estate - expiring commitments or RIs, NAT gateway bills, idle VMs, snapshot sprawl - and for commitment sizing, rightsizing, allocation, SaaS sprawl, AI dev tool spend, or connecting spend to business value. Built by OptimNow.

日本語の概要は準備中です。原文の説明を表示しています。

起草、修订或合规自检中国发明专利（CNIPA 发明专利）申请文件——请求书、说明书摘要、权利要求书、说明书、说明书附图。当用户提及"发明专利""权利要求""说明书""CNIPA""[0001]""分案""答复审查意见"，或要求修改 patent-tex 项目下任意 .tex 文件时触发。仅处理 CN 发明专利申请材料；软件著作权 / 实用新型 / 外观设计不在范围内。

日本語の概要は準備中です。原文の説明を表示しています。

Research a topic in depth for the current or given task plan, by combining Internet/Web search with a grounding in the source artifacts of the project, and append the resulting research report to the "research" attachment of the task, optionally refining the plan by its recommendations. Use when the user wants to "research", "investigate", or "look into" a topic for a "task" or "plan".

日本語の概要は準備中です。原文の説明を表示しています。

Search the Internet/Web with a query. Prefer this skill before using Perplexity, Brave and WebSearch.

日本語の概要は準備中です。原文の説明を表示しています。

Find quotes for a set of topic keywords and place them into a 2x2 matrix, spanned by the presence of an author/origin and by the literal containment of a keyword, optionally grounded in Internet/Web facts and optionally widened to the conceptual neighborhood of the topic. Use when the user wants "quotes", "sayings", "aphorisms", or "citations" on a topic.

日本語の概要は準備中です。原文の説明を表示しています。

Explain a topic in "Explain Like I'm 5" (ELI5) style, optionally grounded in Internet/Web facts. Use when the user wants a topic explained in a very simple, child-friendly way, or mentions "eli5" or "explain like I'm 5".

日本語の概要は準備中です。原文の説明を表示しています。

Determine the conceptual proximity of a topic -- its parent topic, its most relevant sibling topics, and its most relevant child topics -- optionally grounded in Internet/Web facts and optionally navigable in an interactive loop. Use when the user wants to explore the conceptual neighborhood of a topic, or mentions "proximity" or "related topics".

日本語の概要は準備中です。原文の説明を表示しています。

Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing, writing, or debugging Go code under exercises/part2/ (and matching embedded code in docs/part2/**/*.mdx). Thinks hard about correctness, idiomatic Go, error handling, resource cleanup, concurrency, and — crucially — what the tests would catch: edge cases, races, leaks, timeouts, and port conflicts. Knows the repo's module-mode quirk (GO111MODULE=off) and which dirs carry go.mod.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to map or analyze flows, pipelines, processes, or sequences of events in this repo — e.g. "mapa el flujo", "flow", "pipeline", "ciclo de vida", "trace the request", "how does the build/release flow work", "diagrama del flujo". Maps data flows, request lifecycles, CI/CD pipelines, and state transitions with verified file:line evidence. Distinct from analyze-code (which maps code structure); this skill maps movement over time.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing, debugging, or giving feedback on Go code in this repo (exercises/part2, website/tools, or any *.go file) or when asked for a "code review", "review this Go", "revisa este código Go", or "crítica de código". Reviews for correctness, idiomatic Go, error handling, resource cleanup, concurrency, performance, and security, and always ends with a test-thinking pass (what a test would catch). For exercises/part2, prefer the go-exercise-reviewer skill which knows the module-mode quirk; this skill covers general Go anywhere in the repo.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing, debugging, or improving frontend code in this repo (website/ HTML, CSS, JS, service workers, PWA assets) or when asked to "review frontend", "revisa el html/css", "review JS", or "audita el frontend". Reviews for correctness, browser compatibility, accessibility, performance, security (XSS), responsive behavior, and PWA/service-worker correctness, and ends with a "what a user/reviewer would catch" pass.

日本語の概要は準備中です。原文の説明を表示しています。