home / skills / upamune / radicaster / tailwind

tailwind skill

safe

This skill helps you quickly access Tailwind documentation and citations from docs/ with source references and fetch dates.

npx playbooks add skill upamune/radicaster --skill tailwind

Review the files below or copy the command above to add this skill to your agents.

Files (211)

SKILL.md

737 B

---
name: tailwind
description: TAILWIND documentation assistant
---

# TAILWIND Skill

This skill provides access to TAILWIND documentation.

## Documentation

All documentation files are in the `docs/` directory as Markdown files.

## Search Tool

```bash
python scripts/search_docs.py "<query>"
```

Options:
- `--json` - Output as JSON
- `--max-results N` - Limit results (default: 10)

## Usage

1. Search or read files in `docs/` for relevant information
2. Each file has frontmatter with `source_url` and `fetched_at`
3. Always cite the source URL in responses
4. Note the fetch date - documentation may have changed

## Response Format

```
[Answer based on documentation]

**Source:** [source_url]
**Fetched:** [fetched_at]
```

Overview

This skill is a TAILWIND documentation assistant that helps locate and summarize information from the project's docs. It searches Markdown files in the docs/ directory and returns concise, citation-backed answers. It is optimized for quick lookups and accurate references.

How this skill works

The skill inspects Markdown files stored under docs/ and uses a search utility to find relevant sections. It extracts frontmatter metadata (source_url and fetched_at) and includes those fields in every response so users can verify and follow up. A provided search script supports JSON output and result limits for programmatic use.

When to use it

When you need a concise explanation of TAILWIND features documented in the repo.
When you must locate configuration examples, API details, or usage notes from the docs/ directory.
When preparing documentation-based answers that require source citations and fetch dates.
When automating lookups via the search script for tooling or integrations.
When confirming whether documentation has changed since the fetched_at date.

Best practices

Always cite the source_url and include the fetched_at date in the response.
Prefer quoting short, relevant excerpts and then summarizing in plain language.
Use the search script (python scripts/search_docs.py) with --json for structured results.
Limit search results with --max-results when you only need top matches.
State uncertainty if the fetched_at date suggests docs may have changed since retrieval.

Example use cases

Summarize the documented steps for configuring a TAILWIND feature and provide the source link.
Find a code example from docs/ and paste a minimal excerpt with attribution.
Automate validation by running the search script and parsing JSON output for CI checks.
Answer a user question about behavior that is described in the documentation, including fetch date.

FAQ

Do responses need to include metadata?

Yes. Every answer should include the source_url and fetched_at from the document frontmatter.

How do I run the search tool?

Run python scripts/search_docs.py "<query>". Add --json for JSON output and --max-results N to limit results.