Write or edit documents in a distinctive Croatian educational prose style that blends authoritative lecturing with long form journalism. This style addresses readers directly, teaches technical concepts through extended physical analogies, grounds every abstraction in professional relevance, and uses flowing paragraph prose instead of bullet lists. Use this skill whenever the user asks to write lectures, course materials, educational chapters, textbook sections, explainer articles, or onboarding documents in Croatian, or whenever the user asks to apply "the lecture style", "predavanje stil", or references writing like the Web kao infrastruktura document. Also trigger when the user asks to edit or rewrite existing Croatian educational content to sound more engaging, more narrative, or less dry. This skill works for any subject matter, not only web technology.
This skill produces educational prose that reads like a seasoned practitioner talking to intelligent people who lack domain knowledge. The voice is authoritative without being condescending. It teaches deeply while making the reader feel capable rather than overwhelmed.
The style emerged from a specific document about web infrastructure aimed at communication studies students, but the underlying rhetorical machinery works for any subject where a knowledgeable author needs to make complex material accessible, relevant, and compelling for a professional audience.
Before writing or editing anything, read references/style-patterns.md for the full set of linguistic, structural, and rhetorical patterns that define this style.
Every technical or abstract concept in this style follows a four beat sequence. This is the signature move and the single most important pattern to internalize.
Beat one. Present the concept using an analogy drawn from the physical, everyday world. Roads, post offices, restaurants, hotels, envelopes, wristbands, highways, kitchens. Never abstract metaphors. Always objects the reader has touched or places the reader has been.
Beat two. Explain why the concept exists by naming the problem it solves. Do not describe what something is without first making the reader feel the absence it fills.
Beat three. Add technical depth. Go slightly deeper than the reader expects. Tell them they do not need to master the details, then teach the details thoroughly enough that they could explain them in conversation. This creates psychological safety while delivering real education.
Beat four. Connect to the reader's professional life. Use the phrase "why should this matter to you" or its equivalent. Construct a specific scenario where the knowledge becomes necessary. A meeting where a colleague says something technical. A decision where ignorance leads to silence and understanding leads to participation. This beat is mandatory. No concept is ever left floating in abstraction.
The author is a practitioner who has been in the rooms being described. The voice carries quiet professional authority. Claims land with confidence, not hedged into softness.
Address the reader directly using second person. In Croatian, use the vi form. Create a teacher to student relationship that assumes intelligence but not prior knowledge. Calibrate expectations explicitly with phrases like "ne morate znati sve detalje, ali morate razumjeti koncept."
Express genuine emotion about the subject. Awe at engineering elegance. Frustration at poor practices. Dry humor at historical ironies. The text is never emotionally flat.
Open every major piece with a vivid historical or narrative hook. Name a person, a date, a place. Include a sensory detail or an unexpected twist. The first paragraph should make the reader want to read the second.
Build technical knowledge layer by layer, never requiring the reader to understand something that has not yet been introduced.
Write in sustained paragraphs of eight to fifteen sentences. Never use bullet lists inside the explanatory body of the text. When listing items, unfold them inline using connectors like "prvo... drugo... treće" or sequential prose. Bullet lists and tables may appear only in glossaries, learning outcomes, or reference appendices.
Vary sentence length strategically. After a long explanatory passage, drop a short declarative punch for emphasis. These punches should appear roughly every two to three paragraphs. Examples from the source text include "Internet je, dakle, započeo slovom L" and "Ovo nije opcija nego standard."
Analogies are the engine. They share three properties.
First, they are concrete and physical. Roads, postcards, wristbands, restaurants, highways, envelopes, hotel lobbies. Never abstract metaphors. Always things the reader has held in their hands or rooms the reader has stood in.
Second, they are extended rather than glancing. The postal analogy for packet switching runs an entire paragraph with numbered postcards, different routes through cities, and reordering at the destination. The hotel wristband analogy for cookies includes staff turnover and room numbers. Invest in the analogy. Let it breathe.
Third, they are explicitly mapped back to reality. After building the analogy, walk through each element and name its technical counterpart. Postcards become packets. Addresses become IP numbers. The waiter becomes the transport layer. Never leave the mapping implicit.
Repeatedly construct future workplace scenarios where the reader sits in a meeting with specialists. The specialist says something in jargon. The boss asks a budget question. Then present a binary choice: stay silent, or understand and participate.
Use real jargon in the scenario itself, exactly as someone would say it in a meeting. Do not simplify it inside the scenario. Let it arrive raw. The explanation follows after, which creates productive discomfort that motivates the reader.
When telling the history of a subject, write it as micro documentary. Each scene opens with a date, names specific actors and institutions, and locates events geographically. Favor ironic or surprising juxtapositions. A network designed for nuclear survival now delivers cat photos. A physicist solving a filing problem accidentally built the most transformative communication platform in history.
Frame history teleologically toward the reader's present. Every scene ends with a lesson extracted for their professional context. History is never told for its own sake.
Use standard literary Croatian with occasional deliberate colloquialisms for texture. Introduce technical English terms alongside Croatian translations, always with Croatian first and English in parentheses or following "poznat kao" or "ili." Example: predmemoriranje ili caching.
Prefer existing Croatian terms when they are natural and established (poslužitelj over server as the primary term, preglednik for browser, usmjerivač for router). Do not force awkward neologisms when the English term is standard professional vocabulary (API, JavaScript, CSS, CMS, SEO remain in English).
Explicitly manage the depth boundary. Say "ne morate znati sve detalje" and then teach those details thoroughly. The pattern is to provide a psychological safety net while actually delivering substantial education. The reader finishes thinking "I was told I did not need to master this, but now I could explain it to a colleague."
Use callout boxes for two purposes only. Factual asides that add texture without disrupting narrative flow (statistics, physical facts, supplementary context). Action prompts that convert passive reading into active exploration (open this tool, visit this site, try this exercise). The tone inside callouts is slightly more casual and directive than the main text.
It is not dry academic prose. It does not hide behind passive constructions and nominalizations.
It is not a listicle. It does not fragment ideas into bullet points.
It is not condescending. It never simplifies to the point of inaccuracy.
It is not hedging. When it makes a claim, the claim lands.
It is not emotionally neutral. It has a point of view about what matters.
When editing existing text to match this style, apply these transformations in order.
First, identify every abstract concept that lacks a concrete analogy. Add one.
Second, find every technical explanation that does not end with professional relevance. Add the fourth beat.
Third, convert all bullet lists inside explanatory prose into flowing paragraph text with inline enumeration.
Fourth, check sentence rhythm. If more than three paragraphs pass without a short declarative punch, add one.
Fifth, verify that every section opens with a hook rather than a definition. Move definitions to the second or third sentence.
Sixth, ensure all English technical terms have a Croatian primary term or explanation preceding them.
For the full inventory of linguistic patterns, sentence templates, paragraph rhythms, and Croatian language conventions, read references/style-patterns.md.