1---2name: preline-documentation-guide3description: Guides agent to check Preline documentation when markup or component patterns are needed that aren't available…4---56# skills/get-documentation/skill.md
P
skill.mdAgent skill
Transport
File
Status
Listed
SKILL.md
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
shterminal
1npx skills add htmlstreamofficial/preline --skill get-documentation -a cursor -y
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
Download skills/get-documentation/skill.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does preline-documentation-guide live?
The publisher keeps it at https://github.com/htmlstreamofficial/preline.
Which agents can use preline-documentation-guide?
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
From the publisher
SKILL.md
name
preline-documentation-guide
description
Guides agent to check Preline documentation when markup or component patterns are needed that aren't available in standard components.
Preline Documentation Guide
This file is for the AGENT (LLM) only — not end users.
This skill helps you understand when and how to access Preline documentation to find the right markup patterns, component variations, and implementation details.
When to Check Documentation
You SHOULD check the Preline documentation when:
User requests a component variant not available in the standard component list
Example: "floating label input", "accordion with icons", "navbar with mega menu"
These variants often exist in documentation but aren't separate components
User needs specific markup patterns or HTML structure
Example: "how to structure a form", "proper card layout", "input group with button"
Documentation shows best practices and proper HTML structure
User asks about component behavior or configuration
Example: "how to make accordion open by default", "how to disable a dropdown"
Documentation contains data attributes and configuration options
User mentions specific features or functionality
Example: "auto-close on outside click", "keyboard navigation", "validation states"
These are often documented with specific HTML attributes and examples
This skill works together with other Preline skills:
preline-theme-generator: Documentation shows how themes affect component appearance
Component tools (single_component, batch_components): Use these first, fall back to documentation for variants
Browser testing: Test documented patterns to ensure they work correctly
Best Practices
Always prefer documented patterns over custom implementations
Use exact HTML structure from documentation for accessibility
Include all required data attributes for JavaScript functionality
Maintain semantic HTML as shown in documentation
Follow naming conventions for classes and IDs
Test component behavior after implementation
Keep documentation patterns up to date with the current Preline version
Agent Response Pattern
When you need to check documentation, inform the user:
Good:
"Let me check the Preline documentation for the floating label input variant to ensure I use the correct HTML structure and classes."
Also Good:
"I'll look up the accordion configuration options in the documentation to find the right data attribute for keeping items open."
Avoid:
"I'm not sure how to do this." (Instead, check documentation first)
Avoid:
"Let me just try this..." (Don't guess when documentation exists)
Summary
When to use this skill:
User requests component variants not in standard components
User needs specific markup patterns or HTML structure
User asks about component behavior or configuration
You need to verify correct implementation patterns
You're implementing advanced or complex component compositions
How to use this skill:
Use ListMcpResources to see available documentation
Use FetchMcpResource to get specific documentation
Extract the relevant HTML structure, classes, and attributes
Implement using documented patterns
Test the implementation
Key principle:
Always prefer documented patterns over assumptions. Preline documentation is your source of truth for correct HTML structure, classes, and behavior configuration.