Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Static web page stack v1.0.0

Use this resource to choose the tools for a polished static web page with charts and diagrams

New

  • 565 downloads
  • 206 likes
  • 233 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install static-page-stack

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent identifies what your page is (single document, dashboard, report, documentation site) and follows a decision tree to recommend an authoring tool, a styling system, a charting library and a diagram tool. It also flags common anti-patterns, such as the Tailwind CDN or hand-typed chart values, and lays out a phased migration.

Mostly picked by

Updated November 2, 2026

Decision tree for choosing the tools of a static web page.

Details

Generates with
Your agent's model
Uses
  • Quarto (depending on the chosen stack)
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: recommended stack, decision tree, phased migration plan
  • references/full-research-synthesis.md: layer-by-layer comparison
  • references/sota-urls.md: links to starter templates

Good fit for

  • Building a readable static report or dashboard with charts
  • Replacing a pile of utility classes with a coherent styling system
  • Setting up a small documentation or write-up site

Not for

  • Building an interactive web app with user accounts
  • Getting a ready-made page without any build tool

Tags

  • html
  • quarto
  • dashboard
  • charts
  • css

About

You say

"I want a campaign report as a static web page with three charts and a diagram. Which stack do you recommend?"

Decision tree for choosing the tools of a static web page.

Skill published by terrylica under the MIT license.

Show more

Prerequisites

You bring
The content or data for the page and The kind of output you want (single page, multi-page)
Dependencies
Quarto (depending on the chosen stack)

How to use it

  1. Install the skill in your agent.
  2. Describe the page you want: content, charts, number of pages.
  3. Follow the recommended stack and the migration plan.

Content preview

Files

  • LICENSE1 KB
  • NOTICE-PALATEKIT.md0.4 KB
  • references/full-research-synthesis.md8.8 KB
  • references/sota-urls.md4.4 KB
  • SKILL.md10.1 KB

Origin and licence

Modified by PalateKit

Author
terrylica
Source
github.com/terrylica/cc-skills/tree/0ca36f7260a3eb5de13a1b684509c4ecd5fe819b/plugins/doc-tools/skills/static-page-stack
Licence
MIT

Notice

Version modifiée de « static-page-stack » (terrylica, MIT) : traduction française et fiche par PalateKit.

User reviews

–

No ratings yet

Loading reviews…

Delete your review?

Your rating and comment will be removed from the page.

Frequently asked questions

Do I need to install Quarto?

Yes if you keep the default stack. The skill also lists fallbacks (Astro Starlight, Observable Framework) depending on the case.

Does the skill edit its own file?

It describes itself as self-evolving and asks the agent to fix SKILL.md when an instruction is wrong. Remove that section if you prefer a fixed file.