fls-roles-definitions

Clarify FLS definition roles and standard library references for glossary construction.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies how to interpret FLS definition roles :t:, :c:, and :s: and the related definition forms :dt:, :dc:, :ds:, plus guidance on prefix/suffix and label syntax for links. It also explains how to use :std: for Rust standard library references and provides strategies to resolve glossary collisions by identifying the intended term or defining a qualified term without altering spelling.

Core Features & Use Cases

  • Explain definition roles :t:, :c:, and :s: and their usage in definitions.
  • Explain definition forms :dt:, :dc:, :ds:, including examples and disambiguation strategies.
  • Show prefix/suffix and label syntax for links and how to reference standard library items with :std:.
  • Provide glossary-collision resolution guidance when nearby terms are ambiguous, using qualified terms when needed.
  • Use cases: building or reading a glossary in codebases, docs, or educational materials.

Quick Start

Explain a term's FLS roles and standard library references for quick glossary clarification.

Frequently Asked Questions about fls-roles-definitions

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

FAQPage Schema
What do the FLS definition roles :t:, :c:, and :s: mean in technical documentation?▼

FLS definition roles :t:, :c:, and :s: specify how terms are interpreted in glossary construction, distinguishing type, concept, and syntax definitions for precise disambiguation in technical docs.

How do I resolve glossary collisions when multiple terms share similar spelling?▼

Resolve glossary collisions by identifying the intended term or defining a qualified term without altering spelling, ensuring precise interpretation when nearby terms are ambiguous in documentation.

What is the correct syntax for linking to Rust standard library references using :std:?▼

Use the :std: definition role to reference Rust standard library items, applying the appropriate prefix and suffix link syntax to ensure accurate standard library references in glossaries.

How do FLS definition forms :dt:, :dc:, and :ds: differ from their base roles?▼

Definition forms :dt:, :dc:, and :ds: extend the base :t:, :c:, and :s: roles by providing structured definition containers, including examples and disambiguation strategies for glossary entries.

When should I use qualified terms instead of standard definitions in a glossary?▼

Use qualified terms in glossary construction when nearby terms cause ambiguity or collisions, allowing you to identify intended meanings without altering original spelling in technical documentation.

Can I use FLS roles for disambiguation in educational materials and codebase docs?▼

Yes, FLS definition roles and standard library references apply in technical documentation and educational materials where terms require precise interpretation and disambiguation across codebases and learning resources.