learning-article
/learning-article
Turn something the user has just learned or built into an article for their learning-notes repository, written in Russian. Use when the user says "напиши статью", "оформи в статью", "добавь в learning-notes", "write an article about what I learned", or asks to explain a topic or one of their projects as a learning note.
- Author
- kasevvlad ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Turn something the user has just learned or built into an article for their learning-notes repository, written in Russian. Use when the user says "напиши статью", "оформи в статью", "добавь в learning-notes", "write an article about what I learned", or asks to explain a topic or one of their projects as a learning note.
Triggers from the description
Original author description
Turn something the user has just learned or built into an article for their learning-notes repository, written in Russian. Use when the user says "напиши статью", "оформи в статью", "добавь в learning-notes", "write an article about what I learned", or asks to explain a topic or one of their projects as a learning note.
How it works
- Before writing
- Structure
- Style
- After writing
SKILL.md preview
---
name: learning-article
description: Turn something the user has just learned or built into an article for their learning-notes repository, written in Russian. Use when the user says "напиши статью", "оформи в статью", "добавь в learning-notes", "write an article about what I learned", or asks to explain a topic or one of their projects as a learning note.
---
# Learning article
Write an article in Russian that explains one topic the way the user would explain it to a colleague who knows PHP but has not met this topic yet. The goal is understanding, not a reference manual.
## Before writing
1. Find out the topic and the source. The source is either code in the current repository, a conversation, or just the topic name. If it is code, read the relevant files first and base the article on what the code really does.
2. Find the learning-notes repository. Look for a `learning-notes` directory next to the current project or ask for the path. Read its `README.md` to see the sections and the existing articles, so the new one does not repeat them and links to related ones.
3. If the topic is wide, agree on the angle in one question before writing ("очередь на Postgres целиком или только SKIP LOCKED?").
## Structure
Every article follows the same arc. Headings can change, the order should not.
1. **Problem.** A concrete situation where things go wrong, in two or three paragraphs. A double charge, a lost event, a server that fell over. No definitions yet.
2. **The naive solution and why it breaks.** Show the first thing everyone writes and the exact moment it fails.
3. **The idea.** The solution in plain words, before any code. A small ASCII diagram if there is movement between parts.
4. **How it works.** Step by step, with short code. Go or SQL by default, PHP when comparing.
5. **Pitfalls.** What still can go wrong, what the solution does not guarantee.
6. **Summary.** Three to five bullet points the reader should remember.
7. **Further reading.** Two to four links to primary sources: RFCs, official docs, well-known engineering blogs. Only links you are sure exist.
## Style
- Russian, informal but precise. "Мы", "давай посмотрим" are fine, jokes and exclamation marks are not.
- Technical terms stay in English when that is how people say them: idempotency key, backoff, mutex. Explain each one the first time it appears.
- Short paragraphs. One idea per paragraph.
- Code blocks have no comments: everything that needs explaining goes into the text around the block.
- Code must be correct. Do not invent library functions; check the code compiles or matches the real API if there is any doubt.
- No filler: no "в современном мире", "давайте разберёмся", "в заключение хочется сказать". No phrases that sound like generated text.
- No mention of AI, Claude or how the article was written.
- Comparisons with PHP are welcome when they help: the reader knows Laravel and Symfony well.
- Length: as long as the topic needs, usually 150–400 lines of markdown.
## After writing
1. Save the article as `<section>/<short-slug>.md` inside learning-notes. Use an existing section if one fits, create a new folder only if none does.
2. Add the article to the table of contents in the learning-notes `README.md` under its section.
3. Show the user the path and a three-line summary of what the article covers. Do not commit unless asked; when committing, write a plain message without any AI attribution or Co-Authored-By trailer.
Versions
The database has no other skills named learning-article.
Database snapshot: 13.11.2026 · package version 42c3e2664479 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95solo-paper
Turn a research result (math, algorithms, video/audio, systems, datasets) into a solid preprint or conference paper — LaTeX (amsart/article) built locally with tectonic, written from the project's research journal, references verified against databases, reviewed for errors and… - 100statya
Написание русскоязычной статьи или лонгрида с нуля: бриф, фактура, структура, черновик и самопроверка по методу Людмилы Сарычевой. Use this skill whenever the user asks to write, outline, structure, draft, assemble, or turn notes/interviews/materials into a Russian article,… - 100write-article
Use when the author wants a new article, post or essay about this project for Substack, Medium, dev.to or another outlet and gives a topic direction to start from — "напиши статтю про…", "стаття для сабстеку", "пост на dev.to", "write an article about…", "/write-article… - 96study-note
Write a study note in the user's notes vault (Obsidian-style markdown) for a topic they are learning in this project. Use before writing cards for a new topic, or when the user asks for a vault note. - 95orbitant-learning-report
Use when the user wants to review what they've learned, see progress on their gaps, get a summary of recent learning sessions, or wants article ideas based on learnings. Triggers on: "learning report", "what have I learned", "progress report", "summarize my learning", or…