「documentation」の検索結果

Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modeling MCP tools to understand the data structure before providing guidance.

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

Skills for accessing official documentation

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

Generate a language translation for a mkdocs documentation stack.

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

Ensure that Java types are documented with Javadoc comments and follow best practices for documentation.

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

Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.

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

Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.

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

Ensure that C# types are documented with XML comments and follow best practices for documentation.

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

Create a tldr page from documentation URLs and command examples, requiring both URL and command name.

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

Use this skill when someone wants to learn GitHub Copilot CLI from scratch. Offers interactive step-by-step tutorials with separate Developer and Non-Developer tracks, plus on-demand Q&A. Just say "start tutorial" or ask a question! Note: This skill targets GitHub Copilot CLI specifically and uses CLI-specific tools (ask_user, sql, fetch_copilot_cli_documentation).

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

Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.

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

Use Copilot Spaces to provide project-specific context to conversations. Use this skill when users mention a "Copilot space", want to load context from a shared knowledge base, discover available spaces, or ask questions grounded in curated project documentation, code, and instructions.

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

Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.

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

Configures AI agents (GitHub Copilot, Claude Code, Cursor, Codex) to understand a codebase and self-improve as the project evolves. Use when setting up a new project for AI-assisted development, onboarding AI agents to an existing repo, creating AGENTS.md, configuring MCP servers for code navigation, packaging project workflows as agent skills, or establishing self-improvement feedback loops. Covers AGENTS.md authoring, skill packaging, MCP configuration, context management, and living-documentation strategies.

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

Create ASP.NET Minimal API endpoints with proper OpenAPI documentation

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

Generate wiki docs + Mermaid diagrams for any codebase.

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

Plan mode: write an actionable markdown plan to .hermes/plans/, no execution. Bite-sized tasks, exact paths, complete code.

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

Fact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.

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

Stress-test a plan against existing domain language, code behavior, and durable decisions. Use when the user wants DDD/domain-model grilling, glossary refinement, terminology challenges, context documentation, ADR candidates, or plan validation against a repo's language.

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

Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.

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

Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.

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

Create Mermaid diagrams for flowcharts, sequences, ERDs, and architectures. Masters syntax for all diagram types and styling. Use PROACTIVELY for visual documentation, system diagrams, or process flows.

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

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

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

You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices.

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

Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation

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