| name | article-creator |
| description | (🥑) Expert guide for authoring, building, testing, and publishing technical articles to ricc.rocks and Medium. |
| version | 1 |
| tags | devrel, article, publishing, ricc.rocks, medium |
🥑 Article Creator & Publisher Workflow
This skill guides the preparation, compilation, validation, and post-publication steps for articles targeted to ricc.rocks and Medium.
[!NOTE]
For Riccardo, new articles and drafts should always be initialized and managed under the root articles directory: work/articles/ (which is the parent folder relative to individual article projects).
📐 Authoring & Pipeline Rules
- Source of Truth: Always edit
ARTICLE.md only. Never manually edit files inside the generated out/ or ricc.rocks/ directories, as they are overwritten by build.py.
- Image Notation: Write standard Markdown images:
. The build script translates these to Hugo image shortcodes for ricc.rocks and absolute URLs for Medium.
- Cross-Article Links: Write cross-article links using their full
https://ricc.rocks/... absolute URLs in ARTICLE.md. The build script translates them to root-relative paths for ricc.rocks while preserving absolute links for Medium.
🚀 Publishing Checklist & Steps
Step 1: Pre-Publishing Compilation & Review
Before finalizing, compile the article assets and check for spelling/readability:
- Readability & Slop Check: Use Daniela's awesome
speedgrapher MCP server to lint and analyze the article. The MCP server provides the following tools:
fog: Calculates the Gunning Fog readability index (Optimal target: 12.0 - 15.0).
slop: Analyzes text for common AI clichés, tropes, and structural patterns (Target: < 40%).
vale: Performs static style linting against project guidelines.
- Spelling Whitelist: Ensure any technical terms, names, or jargon are whitelisted in the local
speedgrapher.json config.
- Run Build: Compile Dot diagrams and target formats:
just build
Step 2: Local Staging & Testing
Verify that generated HTML builds correctly and links are functional:
- Run the tests to check for broken links and metadata errors:
just test-ricc-rocks-articles
- Inspect output folder contents:
out/ricc.rocks/index.md (Hugo compatible Markdown output for ricc.rocks).
out/medium/index.html (Compiled HTML output ready for Medium).
out/apps-portfolio/ (Copy of index & assets for the portfolio).
Step 3: Medium Manual Upload (One-time)
- Open the Medium editor and paste the content from
out/medium/index.html.
- CRITICAL SEO STEP: Open Medium Story Settings -> Advanced Settings -> Canonical URL.
- Set the Canonical URL to:
https://ricc.rocks/en/posts/technology/<SLUG>/
- Publish the article on Medium.
- Copy the final published Medium URL.
Step 4: Post-Publishing Canonical Sync
- Update the frontmatter of
ARTICLE.md by setting canonicalURL: <Medium_URL>.
- Re-run
just build. This auto-appends the italic Originally published at... footer to the ricc.rocks output file.
- Commit and push to
ricc.rocks repository to trigger deployment.
Step 5: Portfolio & Social Promotion
- Run the
add-to-portfolio-app skill to register this new post in ~/git/vibecoding/apps-portfolio.
- Update the
my-sessions-and-bio repository listings.
- Draft and schedule social announcements on LinkedIn, Bluesky, and Twitter using Buffer.