메뉴
Astro/AstroPaper platform configuration for the blog-workflow plugin
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | platform-astro |
| description | Astro/AstroPaper platform configuration for the blog-workflow plugin |
| tags | ["blog","astro","platform"] |
This skill provides Astro and AstroPaper-specific configuration for the blog-workflow plugin.
src/data/blog/dist/astro buildastro devpubDatetimemodDatetimeogImagecanonicalURLastro.config.mjs, astro.config.ts| Setting | Value |
|---|---|
| Published posts | src/data/blog/ |
| Build output | dist/ |
| Build command | astro build |
| Dev server | astro dev |
| Date field | pubDatetime |
| Updated field | modDatetime |
| Image field | ogImage |
| Canonical field | canonicalURL |
| Field | Type | Notes |
|---|---|---|
id | UUIDv4 | Stable artifact identifier |
title | string | Max 60 chars for SEO |
description | string | 150-160 chars for SEO |
pubDatetime | ISO 8601 | Must include timezone |
tags | string[] | At least one required |
| Field | Default | Notes |
|---|---|---|
modDatetime | null | Set on updates |
author | "aRustyDev" | Configurable per-project |
featured | false | Show on homepage |
draft | true | Exclude from build |
ogImage | "" | Open Graph image path |
canonicalURL | "" | For cross-posted content |
| Wrong | Correct | Reason |
|---|---|---|
date: | pubDatetime: | AstroPaper naming convention |
image: | ogImage: | AstroPaper naming convention |
canonical: | canonicalURL: | AstroPaper naming convention |
type: | (remove) | Not in AstroPaper schema |
This platform is detected when any of these files exist in the project root:
astro.config.mjsastro.config.tsFor detailed documentation, see:
Strategic search planning for agent-driven research. Generates structured search-term matrices with tiered fallback strategies, engine-specific operators, and grading criteria before executing any searches. Use this skill whenever research requires more than a single search query — comparing technologies, verifying claims across sources, surveying a landscape, investigating a multi-faceted question, or building evidence for a decision. Do NOT use for quick factual lookups, fetching a single known URL, or questions answerable from a single source. Covers tech, academic, regulatory, and general domains. Think of it as "research planning" — the matrix is the plan, execution comes after.
Create language conversion skills for translating code from language A to language B. Use when building 'convert-X-Y' skills, designing type mappings between languages, establishing idiom translation patterns, or defining conversion methodologies. Provides foundational patterns that specific conversion skills extend.
Guide for translating code between programming languages. Use when converting code from one language to another, planning language migrations, understanding conversion challenges, asking about type mappings, idiom translations, or referencing pattern mappings. Covers APTV workflow, type systems, error handling, concurrency, and language-specific gotchas.
Identify skill coverage gaps and improvement opportunities. Use when analyzing missing skills for a task, creating skill gap issues, evaluating skill effectiveness, or refining skill progressive disclosure.
Validate Claude Code skills against best practices. Use when checking skill quality, running validation, or creating improvement issues.
{{DESCRIPTION}}