german-technical-writing

Estrellas7

Forks0

Actualizado20 de junio de 2026 a las 11:49

Use this skill when the user asks in German for technical explanations, documentation, README text, release notes, CLI help text, commit or PR descriptions, architecture summaries, or precise editing of German developer-facing prose.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

SimonWaldherr

SimonWaldherr/RustyLLM

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	german-technical-writing
description	Use this skill when the user asks in German for technical explanations, documentation, README text, release notes, CLI help text, commit or PR descriptions, architecture summaries, or precise editing of German developer-facing prose.

German Technical Writing

Style

Use clear, direct German with technical terms where they are normal for developers.
Prefer active voice and concrete nouns over abstract filler.
Keep sentences short when explaining commands, flags, errors, or implementation behavior.
Preserve code identifiers, CLI flags, API paths, filenames, and English library names exactly.

Structure

State the key point first.
Explain the relevant mechanism or tradeoff.
Give commands, examples, or next steps only when they help the user act.

Output Rules

Do not translate identifiers such as --skills-dir, SKILL.md, GenerationOptions, or /v1/chat/completions.
Use German punctuation and capitalization.
Avoid marketing tone, exaggerated claims, and vague words like "einfach", unless the simplicity is the actual point.
When editing existing prose, keep the original intent and shorten where possible.

Más de este repositorio

mismo repositorio

local-llm-troubleshooting

SimonWaldherr/RustyLLM

Use this skill when diagnosing local LLM startup speed, prompt latency, GGUF model loading, tokenizer/chat-template issues, Metal or CPU backend behavior, model selection problems, context-window limits, sampling settings, or API compatibility for OpenAI, LM Studio, Ollama, and MCP routes.

2026-06-207

rust-code-review

SimonWaldherr/RustyLLM

Use this skill when reviewing Rust code, diagnosing borrow checker errors, checking unsafe code, improving Cargo feature boundaries, or evaluating performance-sensitive Rust changes. Also use it when the user asks for a Rust review, Rust bug hunt, compiler error explanation, or refactoring guidance.

2026-06-207

skill-authoring

SimonWaldherr/RustyLLM

Use this skill when creating, reviewing, or improving SKILL.md files, agent skills, workflow instructions, trigger descriptions, progressive disclosure structure, bundled skill examples, or skill-selection behavior. Also use it when the user asks for best practices for skills.

2026-06-207

name	german-technical-writing
description	Use this skill when the user asks in German for technical explanations, documentation, README text, release notes, CLI help text, commit or PR descriptions, architecture summaries, or precise editing of German developer-facing prose.

German Technical Writing

Style

Use clear, direct German with technical terms where they are normal for developers.
Prefer active voice and concrete nouns over abstract filler.
Keep sentences short when explaining commands, flags, errors, or implementation behavior.
Preserve code identifiers, CLI flags, API paths, filenames, and English library names exactly.

Structure

State the key point first.
Explain the relevant mechanism or tradeoff.
Give commands, examples, or next steps only when they help the user act.

Output Rules

Do not translate identifiers such as --skills-dir, SKILL.md, GenerationOptions, or /v1/chat/completions.
Use German punctuation and capitalization.
Avoid marketing tone, exaggerated claims, and vague words like "einfach", unless the simplicity is the actual point.
When editing existing prose, keep the original intent and shorten where possible.