Firecrawl Documentation Helper

An AI assistant specialized in working with Firecrawl documentation while respecting localization constraints.

What This Skill Does

This skill helps you work with the Firecrawl documentation codebase safely by:

Instructions

When working with the Firecrawl documentation:

1. **Identify File Types Before Editing**

- Check if a file has locale suffixes (`.de.mdx`, `.es.json`, `.fr.md`, etc.)

- Look for locale-specific directory paths (`/[locale]/`, `/en/`, `/de/`, `/es/`, `/fr/`, etc.)

- Identify translation dictionaries and i18n JSON files

- Only proceed with edits if the file is a base/source file

2. **Safe Files to Modify**

- Base documentation files without locale suffixes

- Source MDX/MD files in root documentation directories

- Configuration files that aren't locale-specific

- English source content files (if they're marked as source, not locale-specific)

3. **Files to NEVER Modify**

- Any file with a locale suffix (e.g., `getting-started.de.mdx`)

- Files in locale-specific directories (e.g., `/de/introduction.mdx`)

- Translation JSON files (e.g., `translations.es.json`, `dictionaries/de.json`)

- Any i18n-related content managed by translation tools

4. **When Uncertain**

- If you're unsure whether a file is localized, examine its path and filename

- Look for patterns: locale codes (en, de, es, fr, ja, zh, etc.), `/[locale]/` segments, or translation-related naming

- Default to asking the user before modifying files in ambiguous locations

5. **Making Documentation Changes**

- Always read the file first to understand its structure

- Make targeted changes to source files only

- Preserve existing formatting, frontmatter, and markdown structure

- Note that translations will be updated separately through the localization workflow

Examples

Good: Editing a source file

```

User: "Update the API endpoint in the getting-started guide"

Assistant: *Reads `/docs/getting-started.mdx` (base file, no locale suffix)*

Assistant: *Makes the change to the source file*

```

Bad: Editing a localized file

```

User: "Fix a typo in the German version of the API docs"

Assistant: "I cannot modify `/docs/de/api.mdx` as it's a localized file managed by the translation workflow. Please update the source English file instead, and the translation will be updated separately."

```

Good: Multiple file changes

```

User: "Add a new section to all documentation files about rate limiting"

Assistant: *Identifies base files: `/docs/api-reference.mdx`, `/docs/quickstart.mdx`*

Assistant: *Makes changes only to base files, skips `/docs/es/api-reference.mdx`, `/docs/de/quickstart.mdx`*

```

Constraints

Notes