메뉴
Validate a blog post's frontmatter, resolve asset paths, and run astro check to catch type errors. Use when the user wants to verify a post is valid, check frontmatter, or validate before committing a new post.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Interviews the user about a blog post idea — one question at a time — to sharpen scope and nail down structure, producing a concise brief an agent can use to assist in writing. Use when the user wants to develop or clarify a blog post idea before writing.
Create a new Astro component for the dimitri.codes blog with TypeScript props, Tailwind styling, and correct project conventions. Use when the user wants to add a component, create a new UI element, or build a reusable Astro component.
Full coding context for the dimitri.codes Astro blog — commands, architecture, data flow, routing, conventions, and deployment. Load before writing code, reviewing changes, or discussing project conventions.
Generate a catchy excerpt for an existing blog post — resolves the post from a slug, path, or conversation context, produces 3 variants in the blog's established style, then writes the chosen one to the post's frontmatter. Use when the user wants to generate, create, or write an excerpt for a blog post.
Audit all tags across blog posts, surface case inconsistencies, near-duplicates (e.g. Node.js vs NodeJS), and low-frequency tags. Suggests canonical forms and outputs ready-to-use sed rename commands. Use when the user wants to clean up tags, find duplicate tags, audit tag quality, or rename a tag across all posts.
Scaffold a new blog post for the dimitri.codes Astro blog interactively — collects title, categories, tags, and featuredImage conversationally then creates the file with correct frontmatter. Use when the user wants to create a new blog post, write a new article, or add a new post to the blog.
| name | check-post |
| description | Validate a blog post's frontmatter, resolve asset paths, and run astro check to catch type errors. Use when the user wants to verify a post is valid, check frontmatter, or validate before committing a new post. |
Run the validation script, then astro check:
node .claude/skills/check-post/scripts/validate.js [path-or-slug]
npx astro check
validate.js:
node .claude/skills/check-post/scripts/validate.js 2025-02-05-cosmosdb
node .claude/skills/check-post/scripts/validate.js
validate.js exits with code 1 for any other reason (slug not found, multiple matches) → show the error and ask the user to be more specificParse the JSON output and format it as:
Validating src/content/posts/2025/2025-02-05-foo/index.md
✗ Errors (must fix before committing):
- categories: unknown value "java" (allowed: General, Java, JavaScript, Other, Tutorials, Cloud)
⚠ Warnings (non-blocking):
- tags: "spring boot" should be Title Case (e.g. "Spring Boot")
- excerpt: field is missing
ℹ Info:
- post is future-dated (2026-12-01) — it will be hidden in production
If all three arrays are empty: "Frontmatter looks good."
Skip any section whose array is empty.
Always run — regardless of validate.js results:
npx astro check
Tags use Title Case matching the technology name: "Spring Boot", "Node.js", "AngularJS". Not kebab-case.
/tag-cleanup for that)