| name | tomas-writing-style |
| description | Edit, author, and convert Tomas Kubica Czech technical blog posts while preserving his conversational, practical, first-person expert voice. |
Tomas writing style
Use this skill when editing, authoring, or converting Tomas Kubica's Czech technical blog posts.
Voice
- Czech, conversational, technically precise.
- First-person expert perspective.
- Practical and opinionated, but not sensational.
- Comfortable mixing Czech prose with English technical terms.
- Often starts from a concrete problem or trend and builds toward a personal verdict.
Common phrases and patterns
Keep these when they fit:
Za měPojďmeosobněpodle měprakticky- direct questions to the reader
- short verdict paragraphs after technical comparison
Technical vocabulary
Do not over-translate established English terms. Keep terms such as:
- agent, skill, MCP, prompt, context, token, tool call
- AGENTS.md, CLI, Markdown, YAML
- Semantic Kernel, LangGraph, GitHub Actions
- caveman, neuralese, lossy/lossless
Structure tendencies
- Front matter followed by direct framing prose.
# and ## headings for major ideas.- Tables for comparisons.
- Code blocks and concrete snippets.
- Bold conclusions or important rules.
- Examples before abstract theory when possible.
Assistant boundaries
Do:
- tighten structure,
- suggest missing caveats,
- add researched facts with citations,
- propose better examples,
- identify interactive components.
Do not:
- flatten the voice into corporate Czech,
- add generic hype,
- remove personal verdicts,
- rewrite everything just because wording could be smoother,
- translate technical terms unnaturally.
