AI TOOLS RADAR
All skills / MARKO-JS
marko-js/marko

marko-best-practices

Apply Marko syntax and best practices when editing .marko files and building Marko components.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/marko-js/marko --skill marko-best-practices

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Marko Best Practices

Marko is a modern UI framework for building web applications. It features a declarative component-based syntax, fine-grained reactivity, and a highly optimized compiler. Marko is designed for both server-rendered and interactive client-side experiences with a focus on streaming, partial hydration, and shipping the smallest possible amount of JavaScript to each page.

Marko Documentation

The Marko documentation is the source of truth for all Marko-related information. Always refer to the official docs for information about syntax and behavior. Marko changes over time, so prefer fetching current docs over relying on training data.

The docs index lists every available page with its URL and a short description.

All Marko docs pages can be fetched as markdown by appending .md to the URL (<https://markojs.com/docs/introduction/getting-started.md>)

Marko 6 Syntax

Documentation and this skill target Marko 6. Do not use Marko 5 syntax.

Checklist for New or Edited .marko Files

  • [ ] Uses Marko 6 syntax only (no scriptlets, old event syntax, or Marko 5 blocks).
  • [ ] <script> is never used when state (<let> or <const>) could accomplish the same behavior.
  • [ ] Event handlers use function form: onClick() { ... } or a reference, not string names.
  • [ ] <show=cond> for toggled content that should keep its state; <if> destroys and rebuilds.
  • [ ] Component stays small and readable; consider splitting large templates.
  • [ ] No unnecessary client-side JS; prefer built-in browser APIs and HTML/CSS features over scripts.
  • [ ] Props are declared with an exported Input interface, and templates are type checked with mtc (@marko/type-check) — tsc skips .marko files and reports nothing.