// Create new log articles in nibzard.com style. Use when the user says "write an article", "create a blog post", "new log entry", or mentions wanting to write about a topic, experience, or idea. This skill captures the established voice: conversational, narrative-driven, technically deep yet accessible, with authentic personal perspective.
Generate CLI-style PNG images from structured data. Use when the user wants to create terminal-looking tables, command output visualizations, or any data rendered as a CLI screenshot. Triggers on: 'make a table image', 'render as CLI', 'terminal style table', 'screenshot of table', 'CLI visualization', 'illustrate this data', or when user wants to turn tabular data or command output into a shareable image. Also use when creating images for blog posts or articles that show benchmark results, comparison tables, or structured data in terminal style.
Add new GitHub projects to nibzard-web projects page. Fetches repo metadata via gh CLI, generates appropriate topics, and formats entries for src/pages/projects.astro. Use when user says "add project", "add to projects page", or mentions adding GitHub repos to the site.
Create new "idea" entries - product/service concepts with marketing flair. Use when the user says "add an idea", "new idea", "write an idea", or mentions wanting to capture a product or service concept.
Create new "image" entries - visual content with brief captions. Use when the user says "add an image", "new image", "post an image", or mentions wanting to share a screenshot, photo, or visualization.
Create "now" page entries showing current focus areas. Use when the user says "create a now post", "update my now page", "write about what I'm doing now", "now entry", "current status update", or wants to document what they're focused on right now. Triggers for periodic life updates with multiple focus areas.
Create new "thought" entries - quick insights, observations, or reflections. Use when the user says "add a thought", "new thought", "write a thought", or mentions wanting to capture a quick insight or observation.
| name | article-writer |
| description | Create new log articles in nibzard.com style. Use when the user says "write an article", "create a blog post", "new log entry", or mentions wanting to write about a topic, experience, or idea. This skill captures the established voice: conversational, narrative-driven, technically deep yet accessible, with authentic personal perspective. |
| allowed-tools | ["Write","Read","Bash"] |
Create new log articles following the established writing voice and style. Articles are published at root-level URLs (e.g., /vacuum, /api-first).
Create new articles in: src/content/log/
Use kebab-case with short, unique names (1-2 words max) for clean URLs and OG image generation.
Examples: vacuum.md, blink.md, theloop.md, agent-experience.md
Why short names matter: They become URLs (/vacuum) and OG image filenames. Keep them punchy and memorable.
---
title: "Catchy, descriptive title in quotes"
description: "Brief summary (max 130 characters)"
tldr: "Even shorter summary in quotes (max 333 characters)"
date: YYYY-MM-DD
tags: [TAG1, TAG2, TAG3] # Use ALL CAPS
draft: false
author: "Nikola Balić"
topics: [Topic 1, Topic 2, Topic 3] # Detailed topics in sentence case
entities: [Entity 1, Entity 2] # People, companies, tools mentioned
answers_questions:
- Question 1 that the article answers?
- Question 2 that the article answers?
- Question 3 that the article answers?
---
Critical frontmatter rules:
title: max 60 characters, use quotesdescription: max 130 characters, use quotestldr: max 333 characters, use quotestags: ALL CAPS (e.g., [HUMAN, OPINION], [AI, AGENTS, TOOLS])topics and entities: arrays for detailed categorizationanswers_questions: list 2-4 questions the article explicitly answersauthor: "Nikola Balić"draft: false for published articlesExample:
"The most experienced developers--those who've built systems from scratch, debugged the impossible, and shipped products that millions use—are often the most skeptical about AI coding tools."
Example from "The Agent is The Loop":
"There's a moment when a tool stops being a tool and becomes an agent. For most people, that moment with AI happens in a chat interface. You ask, it answers. You ask again, it answers again. But what if it could just... keep going?"
Example:
"I've seen many times how metrics can be deceiving, e.g.: a high signup rate means nothing if users aren't getting real value."
Featured blockquote style:
<blockquote class="featured-quote primary">
Senior engineers have to talk themselves into coding some things… but with AI, I just start writing a wishlist in the text box and send it off.
<cite><a href="https://example.com">Source Name</a></cite>
</blockquote>
Blockquote types:
primary - Main featured quotessecondary - Supporting quotesaccent - Emphasis pointsunattributed - General insightsAI-Human Collaboration
Technical Deep Dives
Growth & Community
Process & Methodology
When the user wants to write an article:
Understand the core experience or insight
Plan narrative arc
Draft in sections
##) to structure ideasRefine voice
Complete frontmatter
Verify with build
pnpm run build to check for errorsCollaborative revision (optional but common)
Commit and push
pnpm run build (generates OG image)git add src/content/log/filename.md public/og/filename.pngadd: Short article title
One-line summary of what the article covers and why it matters.
git pushMANDATORY STEP: After completing any new article, you MUST run the build to ensure it doesn't break:
pnpm run build
This checks for:
Never skip this step - it prevents broken deployments and ensures content quality. If the build fails, fix the errors before considering the article complete.
Short & Focused (500-1000 words)
Medium (1000-2000 words)
Long-Form (2000+ words)
Study these for reference:
vacuum.md - Opinion piece with personal insightsagent-experience.md - Technical deep diveblink.md - Market analysis with strong voicetheloop.md - Short, focused insight2025-year-in-review.md - Long-form narrativegrowth-value-flow.md - Prescriptive advice from experienceThe goal is to share valuable learning experiences with other developers. Your unique perspective, failures, and insights are what make the content valuable. Be authentic, be technical, and be generous with your knowledge.
The best articles feel like learning from an experienced colleague who's been in the trenches and is willing to share both their successes and failures to help you grow.