fls-syntax-blocks

Explain FLS syntax blocks and grammar conventions for reStructuredText documentation sources.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill fls-syntax-blocks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fls-syntax-blocks
Source: https://github.com/PLeVasseur/opencode-project-agents/tree/main/fls/skills/fls-syntax-blocks
Command: npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill fls-syntax-blocks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies how to use the FLS syntax directive and grammar conventions in documentation projects.

Core Features & Use Cases

  • Explain how to write grammar blocks with .. syntax::
  • Describe literal tokens with $$ and identifier rules for syntax categories

Quick Start

Provide concise examples of FLS syntax blocks using .. syntax:: and show how literal tokens like $$ and identifier rules are defined.

Frequently Asked Questions about fls-syntax-blocks

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

FAQPage Schema
How do I write grammar blocks in reStructuredText using the .. syntax:: directive?

To write grammar blocks in reStructuredText, use the .. syntax:: directive to define syntax rules and literal tokens. This approach aligns with frontmatter metadata to structure grammar conventions for software documentation.

What are literal tokens and identifier rules in FLS syntax blocks?

Literal tokens in FLS syntax blocks use the $$ notation to define specific text matches, while identifier rules categorize syntax elements. These conventions help structure grammar definitions within reStructuredText documentation sources.

How do I define syntax categories for documentation projects?

You define syntax categories by applying identifier rules within .. syntax:: blocks in your reStructuredText sources. This categorizes literal tokens and grammar elements, providing clear explanations for documentation authors.

Can I use FLS syntax blocks for editing existing reStructuredText documentation?

Yes, you can use FLS syntax blocks for editing existing reStructuredText documentation. The directive provides explanations and examples that integrate with in-text guidance to update literal tokens and syntax categories.

What is the best way to structure frontmatter metadata for .. syntax:: blocks?

The best way to structure frontmatter metadata for .. syntax:: blocks is to align it with your in-text guidance and literal token definitions. This ensures FLS syntax blocks render correctly and maintain consistent grammar conventions.

Why are my literal tokens not rendering correctly in reStructuredText sources?

Literal tokens may not render correctly in reStructuredText if the $$ notation or identifier rules are misaligned with frontmatter metadata. Verify that your .. syntax:: blocks match the defined FLS grammar conventions.