一键导入
fabrizioduroni-new-blog-post
Scaffold a new blog post with correct directory structure, frontmatter, and opening template
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Scaffold a new blog post with correct directory structure, frontmatter, and opening template
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Orchestrate the full code SDLC for chicio-blog — explore → brainstorm → implement ⇄ review → PR (feature mode), or investigate → confirm → implement ⇄ review → PR (fix mode). Interactive (two human gates) or --autonomous (issue-as-contract, async label gates, PR-only, never merges). Code work only.
The producer side of the autonomous SDLC loop — runs deterministic code-health scanners (coverage, hygiene, a11y), dedups findings against open issues, and files loop-task issues (WITHOUT loop:ready — you curate) for the loop to drain. Session-bound, code work only.
Brainstorm a code idea into a high-confidence, loop-ready GitHub issue for chicio-blog — optionally explore the codebase, grill the idea to shared understanding, synthesize the loop-task contract, and file it via gh. The async front-half of the SDLC pipeline. Code work only.
The self-feeding autonomous loop — one tick either discovers work (scout, auto-approved) when the queue is empty or drains one loop:ready issue to a PR. Sequential (no port collision), session-bound, code-only, never merges.
One tick of the autonomous SDLC loop — pick the oldest loop:ready GitHub issue, hand it to the orchestrator's --autonomous mode, and report. Meant to be driven by /loop. Session-bound, code work only.
Use when adding a new videogame entry to an existing console in the videogames collection
基于 SOC 职业分类
| name | fabrizioduroni-new-blog-post |
| description | Scaffold a new blog post with correct directory structure, frontmatter, and opening template |
| user_invocable | true |
Create a new blog post with the correct directory structure and frontmatter template.
Ask the user for:
my-new-post). Suggest one based on the title if not provided.media/ folder (see step 3). Suggest reusing an existing post's featured image, or use a placeholder path and let the user drop the real file into the post's media/ folder later.Create a new branch with the title of the article separated by dashes.
Today's date determines the path. Create the post directory and its co-located media/ folder (image files live here and are mirrored to public/media/content/... at build time — the folder MUST be named media):
src/content/blog/post/YYYY/MM/DD/<slug>/
src/content/blog/post/YYYY/MM/DD/<slug>/media/
Write content.mdx with:
---
title: "<title>"
description: "<description>"
date: YYYY-MM-DD
image: /media/content/blog/post/YYYY/MM/DD/<slug>/<image-file>
tags: [<tags>]
authors: [fabrizio_duroni]
---
*<description expanded into an italic abstract>*
---
<!-- Start writing here -->
Tell the user:
npm run dev to see it locally