page-template-library
SolidUse when the user says 'save this as a template', 'create a playbook from this page', 'capture this layout', or has hand-built the same page type three times. Captures canonical page patterns as reusable playbooks that later page generation can spawn from in seconds.
Install
Quality Score: 86/100
Skill Content
Details
- Author
- respira-press
- Repository
- respira-press/agent-skills-wordpress
- Created
- 4 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
planpage
Render a skill's plan, review gate, or report as a beautiful, self-contained, INTERACTIVE HTML page — via the open-source planpage package (Preact components → static HTML + a local post-back server so the user can approve / adjust / flip decisions in the browser and the choice comes straight back to the agent). Use whenever a skill needs an approval gate, a decision review, or a shareable before/after report — author with the kit's components instead of hand-rolling HTML each time.
landing-page-generator
Turns a one-paragraph event/webinar brief into a publish-ready landing page, either a WordPress/Elementor section structure or a standalone custom-HTML page, plus a matching set of marketing collaterals. Reads a brand kit on every run so every output is on-brand. A human reviews and publishes; the skill never publishes on its own.
memory-palace
Reproducible kit for mounting Henry Heffernan's 3D-CRT-monitor + Win98-desktop portfolio template (`/palace`) on top of an existing Next.js site. Ships drop-in build scripts, config snippets (webpack / Next / Vercel / tsconfig), placeholder showcase pages, NOTICE templates, a post-deploy DevTools verification snippet, and the 13-gotcha PLAYBOOK that catalogues every way this rollout breaks in production. Use when the user wants a /palace-style 3D portfolio with a clickable retro monitor mounted on their own site, when integrating a vendored CRA app inside a Next.js host, or when debugging "same-origin iframe but Chrome treats it as cross-origin", iframe stuck on broken-document, framer-motion type drift on Vercel, COOP/X-Frame-Options blocking own-iframe, or font fallback inside the inner OS.