no-slop rules for prose writing

When writing any prose (docs, emails, READMEs, PR descriptions):

1. BANNED WORDS: Never use: delve, tapestry, pivotal, vibrant, meticulous, landscape (metaphorical), testament, underscore, intricate, interplay, garner, bolster, foster, showcase, emphasize, crucial, enhance, leverage, utilize, facilitate, streamline, robust (in prose), seamless, holistic, synergy, paradigm, ecosystem (metaphorical), groundbreaking, renowned, profound, comprehensive.

2. COPULAS: Use “is/are/has.” Not “serves as,” “stands as,” “boasts,” “features.”

3. NO STRUCTURAL FORMULAS: No rule-of-three. No “not only X but also Y.” No “challenges and future prospects” endings.

4. NO PARTICIPLE CHAINS: Cut “-ing” filler words (highlighting, showcasing, emphasizing).

5. NO PROMOTIONAL TONE: State facts. No hype. No vague attributions.

6. NO COLLABORATIVE LANGUAGE: No “let’s explore,” “we will examine.”

7. FORMATTING: Minimal bold. No emoji. Sentence-case headings.

8. WRITE LIKE A HUMAN: Vary sentence length. Use contractions. Be specific.

llms.txt maintenance

When a change adds, removes, renames, or moves public site content, review llms.txt in the same change. Update its links and descriptions whenever the published content or site structure changes. Keep the file curated rather than copying the full sitemap, and confirm that its internal URLs match the Jekyll routes.

Agent skills

Issue tracker

Issues and PRDs are tracked in this repository’s GitLab Issues. See docs/agents/issue-tracker.md.

Triage labels

Triage uses the default label names: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. See docs/agents/triage-labels.md.

Domain docs

This repository uses a single-context domain doc layout. See docs/agents/domain.md.