livemark-customization

Name: livemark-customization
Availability: InStock
Author: Datist

Override Livemark components, styles, and routes via the .livemark directory.

1|Updated Mar 16, 2026

Search Tags:#branding #components #customization #routes #static-assets #livemark #ui-overrides

Ready to run

npx skills add https://github.com/datisthq/livemark --skill livemark-customization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: livemark-customization
Source: https://github.com/datisthq/livemark/tree/main/skills/customization
Command: npx skills add https://github.com/datisthq/livemark --skill livemark-customization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customizing Livemark's built-in UI, adding or replacing routes, and shadowing defaults require careful file organization, and this skill provides proven patterns to override components, styles, and routes without forking the core repository.

Core Features & Use Cases

Replace or shadow a default component/style by dropping files into .livemark/components, .livemark/elements, or .livemark/styles.
Add new pages or custom routes under .livemark/routes, or serve static assets via .livemark/public for branding and content tweaks.
Discover overridable files with the escape workflow and compose overrides using the plugin's resolution system to preserve upgrades.

Quick Start

Run livemark escape to copy defaults into .livemark and begin customizing components, routes, or public assets.

Frequently Asked Questions about livemark-customization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I customize Livemark UI components without forking the core repository?▼

You can customize Livemark UI components without forking by dropping replacement files into the .livemark/components, .livemark/elements, or .livemark/styles directories to shadow the built-in defaults. The override resolver composes these changes automatically.

What is the livemark escape workflow used for when overriding UI elements?▼

The livemark escape workflow is used to discover overridable files by copying Livemark's default components and styles into your local .livemark directory so you can begin safely customizing them without losing future upgrades.

Can I add custom routes and static assets to a Livemark project?▼

Yes, you can add custom routes by placing files under .livemark/routes and serve static branding assets directly from the .livemark/public directory without requiring any configuration changes to the core system.

Does Livemark zero-fork customization preserve updates to the core framework?▼

Yes, Livemark zero-fork customization preserves core framework updates by using an override resolver to compose your local .livemark directory changes over built-in defaults without altering the original package files.

What is the best way to apply branding and layout tweaks across Livemark projects?▼

The best way to apply branding and layout tweaks across Livemark projects is to shadow built-in styles in .livemark/styles and serve branded media from .livemark/public, requiring no configuration changes.