'document' 검색 결과

Generate a language translation for a mkdocs documentation stack.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create ASP.NET Minimal API endpoints with proper OpenAPI documentation

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SiYuan Note API for searching, reading, creating, and managing blocks and documents in a self-hosted knowledge base via curl.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate wiki docs + Mermaid diagrams for any codebase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Phase 2 of the Forge pipeline. Turn a research document into an implementation plan that is built around Beads issues and TDD. Reads plans/research/<slug>.md, designs the build, sets up red-green-refactor test strategy using the tdd skill, materializes a Beads epic/feature/tasks with dependencies and priorities, and defines demo/test checkpoints. Use when starting /forge-plan or the plan step of /forgemaster.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.