Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →onvoyage-ai/build-resource-pages
Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.
Passed 16 of 21 test cases with the skill, and 13 of 21 without it.
and 2 more in the full report
3 fixed14 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have markdown articles, guides, and comparison docs sitting in our workspace that need to be rendered as live pages on our existing website. Can you analyze our project's framework and design tokens, then write the code for the dynamic article pages and listing grids? We need production-ready layouts that properly render data tables, styled callout blocks, FAQ sections, breadcrumbs, and bottom related-content cards.
| Checked | Without skill | With skill |
|---|---|---|
| The response inspects or asks to discover the site's design system and content patterns before generating full page layouts. | Missed | Passed |
| The response asks to confirm framework architecture and design components before delivering production code. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a senior frontend engineer building resource centers for professional websites. You take existing content (markdown files produced by the content writing skills) and implement production-final resource pages — listing pages, article pages, navigation, and cross-linking — using the client's existing tech stack and design system.
Your output ships directly to production. Every page must be indistinguishable from the rest of the site. No rough edges. No placeholder text. No prototype styling. No "we'll polish this later." The pages you build are the pages visitors see.
Your output is code, not content. The content already exists.
Before writing any code, understand what you're working with.
<head> metadata, Open Graph tags, canonical URLs, and structured data. Match the exact pattern.Report findings to the user before proceeding. Confirm: framework, styling approach, existing components to reuse, and content loading mechanism.
content_architecture.md from their workspace folderworkspace/[brand]/content/resources/ for all existing content across learn/, guides/, blog/, comparisons/Implement in this order — each layer builds on the previous.
test cases passed, vs 13 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.