القائمة
Use when writing a technical blog post for the RAPS website — covers MDX frontmatter, Astro component imports, series linking, i18n stub creation, and common escaping pitfalls.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding a new MCP tool to the RAPS MCP server — covers tool schema definition, handler implementation, dispatch registration, and the client accessor pattern.
Use when adding a new CLI command or subcommand to RAPS — covers the clap struct pattern, module wiring, output formatting, and test structure across the 10-crate workspace.
Use when new RAPS features ship and LinkedIn content is needed — adds posts to the raps-smm post bank following established tone, format, and hashtag conventions.
Use when bumping the RAPS version for a new release — updates Cargo.toml workspace version, 9 internal crate dependencies, 6 npm package.json files, creates git tag, and triggers the release workflow.
Use when adding or updating CI/CD integrations in the raps-actions repo — GitHub Actions composite actions, GitLab CI include templates, test workflows, and floating tag management.
Use before releases or after dependency updates to run security checks — cargo-audit, ASVS compliance matrix review, clippy security lints, redaction pattern verification.
| name | writing-raps-blog-post |
| version | 1.0 |
| description | Use when writing a technical blog post for the RAPS website — covers MDX frontmatter, Astro component imports, series linking, i18n stub creation, and common escaping pitfalls. |
Create technical blog posts for the RAPS documentation website.
Repo: /root/github/raps/raps-website
Location: src/content/blog/en/<slug>.mdx
---
title: "Post Title"
description: "SEO description (150-160 chars)"
pubDate: 2026-03-01
author: "Dmytro Yemelianov"
tags: ["ci-cd", "automation", "pipelines"]
featured: true # Shows on homepage
series: "DevOps for Design" # Optional — groups related posts
seriesOrder: 4 # Optional — order within series
draft: false
---
raps commands, YAML pipelines, or GitHub Actions workflows| Pattern | Problem | Solution |
|---|---|---|
{variable} in prose | Parsed as JSX expression | Use {variable} |
${{ secrets.X }} | GitHub Actions syntax | Use {'${{ secrets.X }}'} |
<100MB | Looks like JSX tag | Write "under 100MB" |
{...} outside code blocks | JSX expression | Use HTML entities |
Inside fenced code blocks (```) these are safe — no escaping needed.
import PerformanceChart from '@/components/PerformanceChart.astro';
Use className not class in JSX elements. Custom divs for callouts:
<div className="not-prose mb-6 p-4 bg-green-50 dark:bg-green-900/20 rounded-lg border border-green-200 dark:border-green-800">
<p className="text-sm text-green-800 dark:text-green-200">
<strong>Note:</strong> Content here
</p>
</div>
English is primary. Ukrainian stubs go in src/content/blog/uk/<same-slug>.mdx with translated frontmatter. Content can remain in English as fallback.
ci-cd, automation, pipelines, github-actions, design-automation, revit, devops, mcp, ai, claude, cli, tutorial, installation, beginners, devcon, series, security, testing
src/content/blog/en/<slug>.mdx with frontmatteruk/npm run build to verify no MDX/Astro errors