القائمة
Use when a new RAPS version is released or a major feature ships and the raps-website repo needs updating — release entries, docs pages, blog posts, stats.
التثبيت باستخدام 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 | updating-raps-website |
| version | 1.0 |
| description | Use when a new RAPS version is released or a major feature ships and the raps-website repo needs updating — release entries, docs pages, blog posts, stats. |
Update the RAPS documentation website after releases or major features.
Repo: /root/github/raps/raps-website (Astro + MDX + Tailwind)
| File | When | Purpose |
|---|---|---|
src/data/releases.js | Every release | Changelog, homepage badge, version refs |
src/content/docs/en/*.mdx | New/changed features | CLI documentation |
src/content/blog/en/*.mdx | Major features | Technical blog posts |
src/pages/index.astro:57-62 | Stats change | Homepage stats (APIs, commands, modes) |
Latest version MUST be first in the array. Fields:
{
version: '4.16.0',
date: '2026-03-01', // YYYY-MM-DD
highlights: ['Feature1', 'Feature2', 'Feature3', 'Feature4'], // exactly 4
description: 'One-line summary of the release',
type: 'minor', // 'major' | 'minor' | 'patch'
changes: {
added: ['Feature description'],
changed: ['Change description'],
fixed: ['Fix description'],
security: ['Security fix'], // optional
},
}
---
title: "Page Title"
description: "SEO description"
section: "guides" # getting-started | modes | commands | guides | cookbook
order: 2 # sort order within section
icon: "📋" # optional emoji
---
File location: src/content/docs/en/<slug>.mdx (+ uk/ for Ukrainian translation).
---
title: "Post Title"
description: "SEO description"
pubDate: 2026-03-01
author: "RAPS Team"
tags: ["ci-cd", "automation", "pipelines"]
featured: true
draft: false
---
File location: src/content/blog/en/<slug>.mdx.
Supports Astro component imports. Use className not class in JSX.
const stats = [
{ value: '15+', label: t('home.stats.apis') },
{ value: '95+', label: t('home.stats.commands') },
{ value: '7', label: t('home.stats.modes') },
{ value: '0', label: t('home.stats.deps') },
];
Update values when command count, API count, or mode count changes.
src/data/releases.js (first position)pipelines.mdx for Pipeline v2)npm run build to verify no Astro/MDX errors{ and < in MDX (use { or {'${{ secrets.X }}'} for GitHub Actions syntax)class instead of className in MDX JSX elements