AI Assistant Guidelines for Denis Palnitsky's Blog

About the Author

Denis Palnitsky writes technical articles focused on practical DevOps and backend development topics. His expertise spans GitHub Actions, Golang, Docker, Kubernetes, CI/CD, and modern development practices.

Medium profile: @denispalnitsky

Published Articles

GitHub Actions Advanced Techniques (Jul 2024)
- Topics: GitHub Actions, CI/CD, optimization, reusable workflows
- https://medium.com/@denispalnitsky/github-actions-advanced-techniques-78f0905f2668
How to reduce your GitHub Actions bill (Feb 2024)
- Topics: Cost optimization, third-party runners, DevOps economics
- https://blog.devops.dev/how-to-reduce-your-github-actions-bill-5e7205879eed
Autogenerated API documentation in Go with Open API(Swagger) (Jan 2024)
- Topics: Golang, REST APIs, documentation automation, code-first approach
- https://medium.com/@denispalnitsky/autogenerated-api-documentation-in-go-with-open-api-swagger-a0ed1edb084c
Mastering Service Tests in Golang: A Practical Guide (Nov 2023)
- Topics: Testing, Golang, microservices, integration testing
- https://blog.stackademic.com/mastering-service-tests-in-golang-a-practical-guide-89788393c906
Speeding up multistage docker build (Nov 2023)
- Topics: Docker optimization, build performance, DevOps
- https://blog.devops.dev/speeding-up-multistage-docker-build-3f16951cdbdd

Writing Style

Tone and Voice

Conversational and direct - Use first person ("I") and second person ("you") frequently
Pragmatic over theoretical - Focus on practical solutions, not academic discussions
Honest about limitations - Always mention trade-offs, gotchas, and when something "is not perfect"
Humble and helpful - Phrases like "If you need help, feel free to reach out"
No-nonsense - Get to the point quickly, avoid fluff

Structure Patterns

Opening:

Start with a brief problem statement or context (1-2 paragraphs)
Often include: "Straight to the code" with a GitHub link at the very beginning
Use rhetorical questions or scenarios: "So you have a multistage docker build..."

Body:

Use clear H3 (###) section headings
Break down complex topics into digestible chunks
Each section should be actionable and self-contained
Include step-by-step instructions with code examples
Use bullet points for lists of benefits, requirements, or steps

Code Examples:

ALWAYS include working code, not pseudocode
Show complete examples, not fragments
Link to full GitHub repositories with working examples
Use code blocks liberally with proper syntax highlighting
Include comments in code to explain non-obvious parts
Show "before and after" comparisons when optimizing

Visual Aids:

Use tables for comparisons (especially pricing, specs)
Include command-line output examples
Reference images/diagrams when they add value

Closing:

End with "Wrapping Up", "Last words", or "Final Considerations"
Summarize key takeaways
Encourage readers to try the solution
Offer to help: "feel free to reach out"

Technical Writing Guidelines

Keep it simple - Follow YAGNI principle
Be specific - Use exact version numbers, specific tool names, real examples
Link generously - Link to official docs, GitHub repos, related articles
Acknowledge complexity - If something is tricky, say so
Provide context - Explain WHY before diving into HOW
Show, don't just tell - Always pair explanations with code/examples

Common Patterns

Build tags and conventions: Explain Go-specific patterns like
```
//go:build servicetest
```
Configuration: Show environment variable setup, config files
Testing: Include test commands with flags explained
Docker: Show both Dockerfile and build commands
Real-world examples: Use actual open-source projects (go-ethereum, etc.)

Language and Phrasing

Preferred phrases:

"Here is what we need to do:"
"Let's test it"
"Things to keep in mind:"
"As you can see..."
"The idea is simple."
"That's it."
"Not bad, huh?"

Avoid:

Marketing speak or hype
Overuse of emojis (use sparingly, like ⚠️ for warnings)
Long introductions
Academic language
Unnecessarily complex explanations

Article Length

Aim for 1500-3000 words (medium-length articles)
Focus on one main topic with 5-8 subsections
Include at least 3-5 code examples
Link to a complete working GitHub repository

Topics of Expertise

Primary Topics

GitHub Actions: Optimization, cost reduction, advanced techniques, reusable workflows
Golang: Web services, testing, API documentation, practical patterns
Docker: Multi-stage builds, optimization, container best practices
DevOps: CI/CD, automation, infrastructure, cost optimization
Testing: Service tests, integration testing, testing pyramid

Secondary Topics

Kubernetes (deployment, helm charts)
REST APIs and OpenAPI
Microservices architecture
Build optimization
Developer productivity

Target Audience

Mid to senior level developers who already know the basics
DevOps engineers looking to optimize their workflows
Backend developers working with Go and microservices
People who value practical, copy-paste-able solutions over theory

Content Guidelines

When Writing New Articles

Start with a problem - What pain point are we solving?
Link to working code - Create or reference a GitHub repo with full example
Show the solution incrementally - Build up from simple to complete
Include all the pieces - Dockerfile, CI config, deployment specs, etc.
Test the code - All examples should actually work
Add practical context - Mention real-world usage, pricing, limitations
Keep it focused - One main topic per article

Topics to Avoid

Front-end development (not the focus area)
Purely theoretical computer science
Beginner tutorials (assume reader knows basics)
Product reviews without technical depth
Generic "how to code" content

Special Patterns

Disclaimers and Notes

Use disclaimers when needed, formatted as:

Italicized notes for clarifications
⚠️ emoji for warnings about limitations
"Things to keep in mind:" for important caveats

Repository References

Create example repos under DenisPalnitsky or num30 GitHub accounts

Use descriptive repo names:

github-actions-advanced-techniques

golang-service-test

Include README with clear instructions

Code-First Approach

Show the code first, explain after
Full working examples over snippets
Link to specific files in repos using GitHub URLs

Measurements and Benchmarks

Include before/after comparisons
Show actual numbers: "10 times faster", "$0.008/minute"
Use real-world examples with tangible results

Medium-Specific Formatting

Use H3 (###) for main sections (Medium converts these properly)
Use
```
<pre>
```
tags in Medium for code blocks (or code blocks in markdown drafts)
Keep paragraphs short (2-3 sentences) for readability
Use bullet points to break up text
Include links to related articles

AI Assistant Instructions

When helping Denis write blog articles:

Match the voice: Conversational, practical, humble
Structure first: Outline the article with clear sections before writing
Code-heavy: Include multiple working code examples
Link to repos: Suggest creating example repos with full code
Be specific: Use exact tools, versions, commands
Show trade-offs: Mention limitations and alternatives
Keep it focused: One main topic, explained well
Target the right audience: Mid/senior devs who want practical solutions
Edit ruthlessly: Cut fluff, keep only what adds value
Follow YAGNI: Keep solutions simple, don't over-engineer

Example Article Template

# [Practical Problem Title]

*Straight to the [code](https://github.com/username/repo).*

[Brief problem statement - 2-3 paragraphs]

### What is [Concept]?

[Quick explanation with context]

### Why [Problem] Matters

[Business/technical justification]

### The Solution

[Overview of approach]

Here is what we need to do:
- Step one
- Step two
- Step three

### Implementation

[Code example with explanation]

### Testing It

[How to run/test the solution]

### Things to Keep in Mind

- Limitation one
- Gotcha two
- Alternative approach

### Wrapping Up

[Summary, encouragement to try it, offer to help]

This agents.md file should be referenced when writing new articles to maintain consistency with Denis's established voice and style.

AI Assistant Guidelines for Denis Palnitsky's Blog

About the Author

Medium profile: @denispalnitsky

Published Articles

GitHub Actions Advanced Techniques (Jul 2024)
- Topics: GitHub Actions, CI/CD, optimization, reusable workflows
- https://medium.com/@denispalnitsky/github-actions-advanced-techniques-78f0905f2668
How to reduce your GitHub Actions bill (Feb 2024)
- Topics: Cost optimization, third-party runners, DevOps economics
- https://blog.devops.dev/how-to-reduce-your-github-actions-bill-5e7205879eed
Autogenerated API documentation in Go with Open API(Swagger) (Jan 2024)
- Topics: Golang, REST APIs, documentation automation, code-first approach
- https://medium.com/@denispalnitsky/autogenerated-api-documentation-in-go-with-open-api-swagger-a0ed1edb084c
Mastering Service Tests in Golang: A Practical Guide (Nov 2023)
- Topics: Testing, Golang, microservices, integration testing
- https://blog.stackademic.com/mastering-service-tests-in-golang-a-practical-guide-89788393c906
Speeding up multistage docker build (Nov 2023)
- Topics: Docker optimization, build performance, DevOps
- https://blog.devops.dev/speeding-up-multistage-docker-build-3f16951cdbdd

Writing Style

Tone and Voice

Conversational and direct - Use first person ("I") and second person ("you") frequently
Pragmatic over theoretical - Focus on practical solutions, not academic discussions
Honest about limitations - Always mention trade-offs, gotchas, and when something "is not perfect"
Humble and helpful - Phrases like "If you need help, feel free to reach out"
No-nonsense - Get to the point quickly, avoid fluff

Structure Patterns

Opening:

Start with a brief problem statement or context (1-2 paragraphs)
Often include: "Straight to the code" with a GitHub link at the very beginning
Use rhetorical questions or scenarios: "So you have a multistage docker build..."

Body:

Use clear H3 (###) section headings
Break down complex topics into digestible chunks
Each section should be actionable and self-contained
Include step-by-step instructions with code examples
Use bullet points for lists of benefits, requirements, or steps

Code Examples:

ALWAYS include working code, not pseudocode
Show complete examples, not fragments
Link to full GitHub repositories with working examples
Use code blocks liberally with proper syntax highlighting
Include comments in code to explain non-obvious parts
Show "before and after" comparisons when optimizing

Visual Aids:

Use tables for comparisons (especially pricing, specs)
Include command-line output examples
Reference images/diagrams when they add value

Closing:

End with "Wrapping Up", "Last words", or "Final Considerations"
Summarize key takeaways
Encourage readers to try the solution
Offer to help: "feel free to reach out"

Technical Writing Guidelines

Keep it simple - Follow YAGNI principle
Be specific - Use exact version numbers, specific tool names, real examples
Link generously - Link to official docs, GitHub repos, related articles
Acknowledge complexity - If something is tricky, say so
Provide context - Explain WHY before diving into HOW
Show, don't just tell - Always pair explanations with code/examples

Common Patterns

Build tags and conventions: Explain Go-specific patterns like
```
//go:build servicetest
```
Configuration: Show environment variable setup, config files
Testing: Include test commands with flags explained
Docker: Show both Dockerfile and build commands
Real-world examples: Use actual open-source projects (go-ethereum, etc.)

Language and Phrasing

Preferred phrases:

"Here is what we need to do:"
"Let's test it"
"Things to keep in mind:"
"As you can see..."
"The idea is simple."
"That's it."
"Not bad, huh?"

Avoid:

Marketing speak or hype
Overuse of emojis (use sparingly, like ⚠️ for warnings)
Long introductions
Academic language
Unnecessarily complex explanations

Article Length

Aim for 1500-3000 words (medium-length articles)
Focus on one main topic with 5-8 subsections
Include at least 3-5 code examples
Link to a complete working GitHub repository

Topics of Expertise

Primary Topics

GitHub Actions: Optimization, cost reduction, advanced techniques, reusable workflows
Golang: Web services, testing, API documentation, practical patterns
Docker: Multi-stage builds, optimization, container best practices
DevOps: CI/CD, automation, infrastructure, cost optimization
Testing: Service tests, integration testing, testing pyramid

Secondary Topics

Kubernetes (deployment, helm charts)
REST APIs and OpenAPI
Microservices architecture
Build optimization
Developer productivity

Target Audience

Mid to senior level developers who already know the basics
DevOps engineers looking to optimize their workflows
Backend developers working with Go and microservices
People who value practical, copy-paste-able solutions over theory

Content Guidelines

When Writing New Articles

Start with a problem - What pain point are we solving?
Link to working code - Create or reference a GitHub repo with full example
Show the solution incrementally - Build up from simple to complete
Include all the pieces - Dockerfile, CI config, deployment specs, etc.
Test the code - All examples should actually work
Add practical context - Mention real-world usage, pricing, limitations
Keep it focused - One main topic per article

Topics to Avoid

Front-end development (not the focus area)
Purely theoretical computer science
Beginner tutorials (assume reader knows basics)
Product reviews without technical depth
Generic "how to code" content

Special Patterns

Disclaimers and Notes

Use disclaimers when needed, formatted as:

Italicized notes for clarifications
⚠️ emoji for warnings about limitations
"Things to keep in mind:" for important caveats

Repository References

Create example repos under DenisPalnitsky or num30 GitHub accounts

Use descriptive repo names:

github-actions-advanced-techniques

golang-service-test

Include README with clear instructions

Code-First Approach

Show the code first, explain after
Full working examples over snippets
Link to specific files in repos using GitHub URLs

Measurements and Benchmarks

Include before/after comparisons
Show actual numbers: "10 times faster", "$0.008/minute"
Use real-world examples with tangible results

Medium-Specific Formatting

Use H3 (###) for main sections (Medium converts these properly)
Use
```
<pre>
```
tags in Medium for code blocks (or code blocks in markdown drafts)
Keep paragraphs short (2-3 sentences) for readability
Use bullet points to break up text
Include links to related articles

AI Assistant Instructions

When helping Denis write blog articles:

Match the voice: Conversational, practical, humble
Structure first: Outline the article with clear sections before writing
Code-heavy: Include multiple working code examples
Link to repos: Suggest creating example repos with full code
Be specific: Use exact tools, versions, commands
Show trade-offs: Mention limitations and alternatives
Keep it focused: One main topic, explained well
Target the right audience: Mid/senior devs who want practical solutions
Edit ruthlessly: Cut fluff, keep only what adds value
Follow YAGNI: Keep solutions simple, don't over-engineer

Example Article Template

# [Practical Problem Title]

*Straight to the [code](https://github.com/username/repo).*

[Brief problem statement - 2-3 paragraphs]

### What is [Concept]?

[Quick explanation with context]

### Why [Problem] Matters

[Business/technical justification]

### The Solution

[Overview of approach]

Here is what we need to do:
- Step one
- Step two
- Step three

### Implementation

[Code example with explanation]

### Testing It

[How to run/test the solution]

### Things to Keep in Mind

- Limitation one
- Gotcha two
- Alternative approach

### Wrapping Up

[Summary, encouragement to try it, offer to help]

This agents.md file should be referenced when writing new articles to maintain consistency with Denis's established voice and style.

AI Assistant Guidelines for Denis Palnitsky's Blog

Related Skills

Markdown Converter

Nano Banana Pro

1password