Kevinnnnn-ai

article-image-gen

Use when the user invokes /article-image-gen <slug>, or asks to "generate images for article", "fill image placeholders", or "create article images". Scans article.md for ![description]() placeholders and batch-generates SVG infographics in the site's tech/glow aesthetic.

article-interlink

Use when the user invokes /interlink or /interlink <slug>. Scans article HTML pages, builds and maintains a persistent link-map.json, and adds Wikipedia-style internal cross-links to article bodies. Triggers on "/interlink", "interlink articles", "add internal links", or "cross-link articles".

article-scaffold

Use when the user invokes /article-scaffold <slug> or an agent creates a new article page from a source folder. Reads markdown + images from src/articles/content/<slug>/, produces a static article HTML page, updates config.js, and wires the listing card. Triggers on "/article-scaffold", "create an article", "build an article page", or agent invocation with a slug.

code-navigation-system

Use after completing a coding task that added a new section, file, renamed/moved/changed code, or altered how sections connect. This updates docs/code-map.md accordingly, refreshes inline section anchors, and appends an entry to docs/change-log.md. Skip for within-section tweaks like tuning values, color changes, or typo fixes.

Data & Documents Listed

content-data-update

Use when the user wants to add, edit, or remove content anywhere in the website, including but not limited to SITE_CONFIG data (articles, hero copy, stats, topics, ticker, nav, CTA), HTML structure, CSS styles, or JS behaviour. Triggers when an agent invokes the skill or the user calls it manually.

page-scaffold

Use when the user invokes /page-scaffold followed by a description of a new page to add. This runs a site-aware brainstorming phase, produces a spec doc, then implements via frontend-design, screenshot-feedback, and code-navigation-system. Triggers on an agent call, "/page-scaffold", or any phrase relating to page scaffolding.

project-scaffold

Use when the user invokes /project-scaffold <slug> or asks to create/scaffold/build a project showcase page. Reads project metadata from src/projects/content/<slug>/meta.json, invokes brainstorming to design a creative showcase, then implements via frontend-design and a screenshot loop. Triggers on "/project-scaffold", "create a project page", "scaffold a project", "build a project showcase", "add a project", or agent invocation with a slug. Use this even when the user just says "I want to add my project to the site" or provides a GitHub link and asks to showcase it.

screenshot-feedback

Use after capturing a screenshot during a feedback loop, to audit whether the rendered output matches a reference image, or the project's design criteria. This skill triggers on a request for screenshot comparison, attempts to audit rendered output, statements stating that the rendered output did match descriptions or reference, or any invocation passing a screenshot path. Outputs a verdict, grouped P1/P2/P3 findings tied to likely source locations, and a recommended next action. Skips for static code review or pre-render design work.

section-scaffold

Use when the user invokes /section-scaffold followed by a description of a new section to add to an existing page. Runs a site-aware brainstorming phase, produces a spec doc, then implements via frontend-design, screenshot-feedback, and code-navigation-system. Triggers on "/section-scaffold" or "scaffold a new section".

website-optimizer

Use when the user wants to make the astronology.dev website faster, audit performance, optimize loading, reduce bundle size, fix render-blocking resources, or improve Lighthouse scores. Triggers on phrases like "optimize the website", "make it faster", "audit performance", "reduce JS/CSS size", "speed up loading", "improve performance", or any request to find and fix performance issues across `src/`. Produces a prioritized findings report, then applies approved changes without altering functionality. Use this skill even when the user only hints at speed concerns (e.g., "the hero feels sluggish", "first paint is slow").