Marko Best Practices
Developmentmarko-best-practicesMarko Best Practices is an Agent Skill for development published in the marko-js/marko repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Apply Marko syntax and best practices when editing `.marko` files and building Marko components.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/marko-js/marko/blob/HEAD/skills/marko-best-practices/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/marko-best-practices, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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. - 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.