fa-help

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Answer Font Awesome questions by fetching and citing the official documentation. This skill grounds answers in authoritative, version-accurate content rather than relying on training data that may be stale.

通过获取并引用官方文档来解答Font Awesome相关问题。该技能以权威、版本准确的内容为依据给出答案，而非依赖可能过时的训练数据。

Documentation source

文档来源

Font Awesome publishes LLM-friendly docs at

https://docs.fontawesome.com

. The index at

/llms.txt

lists every available page. Each page is a self-contained Markdown file with headings, tables, and code examples.

Font Awesome在

https://docs.fontawesome.com

发布了适用于LLM的文档。

/llms.txt

路径下的索引文件列出了所有可用页面。每个页面都是一个独立的Markdown文件，包含标题、表格和代码示例。

Steps

操作步骤

Fetch the documentation index. Use
```
WebFetch
```
to retrieve
```
https://docs.fontawesome.com/llms.txt
```
. This file lists every available documentation page with its URL and a short description. Use a prompt like: "Return the complete content of this file exactly as-is. I need to see every URL and its description."
Identify the relevant page(s). Read the user's question and scan the
```
llms.txt
```
index to find the most relevant documentation URL(s). The URLs end in
```
.md
```
and the path structure is descriptive (e.g.,
```
/web/setup/use-kit.md
```
,
```
/web/style/animate.md
```
,
```
/web/use-with/react/troubleshoot.md
```
). Most questions map to one or two pages. If a question spans topics, pick the most specific page first.
Fetch the documentation page(s). Use
```
WebFetch
```
to retrieve the relevant Markdown page(s) identified in the previous step. Fetch the most specific page first. If the answer requires context from a second page, fetch that too — but limit yourself to three pages maximum per question.
When fetching, use a prompt like: "Return the full content of this documentation page as Markdown. Preserve all headings, code blocks, and tables."
Synthesize the answer. Using the fetched documentation as your primary source:
- Answer the user's question directly and concisely.
- Include relevant code examples from the docs, adapted to the user's context if possible.
- If the user has a
```
.font-awesome.md
```
  file in their project, tailor the answer to their specific integration method, version, and license.
- If the docs describe multiple approaches, recommend the one that best fits the user's project.
Cite the source. At the end of your answer, include a link to the documentation page(s) you referenced so the user can read more. Convert the
```
.md
```
URL to a web URL by removing the
```
.md
```
extension. For example:
Source: Use a Kit
Offer related skills. If the answer naturally leads to an action the user could take, offer the relevant skill:
- If they're asking how to add an icon → offer
```
/add-icon
```
- If they're asking about setting up Font Awesome → offer
```
/setup-fa
```
- If they're looking for the right icon → offer
```
/suggest-icon
```

获取文档索引：使用
```
WebFetch
```
获取
```
https://docs.fontawesome.com/llms.txt
```
。该文件列出了所有可用文档页面的URL及简短描述。使用如下提示语："原样返回该文件的完整内容。我需要查看每个URL及其描述。"
识别相关页面：阅读用户的问题，扫描
```
llms.txt
```
索引以找到最相关的文档URL。这些URL以
```
.md
```
结尾，路径结构具有描述性（例如：
```
/web/setup/use-kit.md
```
、
```
/web/style/animate.md
```
、
```
/web/use-with/react/troubleshoot.md
```
）。大多数问题对应一个或两个页面。如果问题涉及多个主题，优先选择最具体的页面。
获取文档页面：使用
```
WebFetch
```
获取上一步中识别出的相关Markdown页面。优先获取最具体的页面。如果答案需要第二个页面的上下文，也可获取该页面——但每个问题最多获取三个页面。
获取时使用如下提示语："以Markdown格式返回该文档页面的完整内容。保留所有标题、代码块和表格。"
合成答案：以获取到的文档为主要来源：
- 直接、简洁地回答用户的问题。
- 包含文档中的相关代码示例，如有可能，根据用户的上下文进行调整。
- 如果用户的项目中存在
```
.font-awesome.md
```
  文件，根据其特定的集成方式、版本和许可证调整答案。
- 如果文档描述了多种方法，推荐最适合用户项目的方案。
引用来源：在答案末尾，附上你参考的文档页面链接，方便用户进一步阅读。将
```
.md
```
格式的URL转换为网页URL，只需移除
```
.md
```
扩展名。例如：
来源：使用工具包
推荐相关技能：如果答案自然引出用户可以执行的操作，推荐相关技能：
- 如果用户询问如何添加图标 → 推荐
```
/add-icon
```
- 如果用户询问Font Awesome的设置方法 → 推荐
```
/setup-fa
```
- 如果用户寻找合适的图标 → 推荐
```
/suggest-icon
```

Guidelines

指导原则

Never provide bare SVG markup. If the user asks for raw
```
<svg>
```
output of a Font Awesome icon, do not generate it from your own knowledge or training data. Direct them to use
```
/add-icon
```
which can fetch authoritative SVG markup from the Font Awesome API.
Always fetch the docs. Do not answer from memory alone — the docs are the authoritative source and may contain v7-specific information that differs from your training data.
Stay within scope. This skill answers questions about Font Awesome. If the question is about general CSS, JavaScript, or a framework unrelated to Font Awesome, say so and answer briefly without fetching docs.
Be honest about gaps. If the docs don't cover the user's question, say so. Don't fabricate an answer.
Respect the user's integration method. If
```
.font-awesome.md
```
exists, tailor examples to their setup rather than showing generic code.

绝不提供原始SVG标记：如果用户请求Font Awesome图标的原始
```
<svg>
```
输出，不要凭借自身知识或训练数据生成。引导他们使用
```
/add-icon
```
技能，该技能可从Font Awesome API获取权威的SVG标记。
始终获取文档：不要仅凭记忆作答——文档是权威来源，可能包含与训练数据不同的v7专属信息。
保持在范围内：该技能仅解答Font Awesome相关问题。如果问题涉及通用CSS、JavaScript或与Font Awesome无关的框架，需说明这一点并简要作答，无需获取文档。
如实说明信息缺口：如果文档未涵盖用户的问题，需如实告知。不要编造答案。
尊重用户的集成方式：如果存在
```
.font-awesome.md
```
文件，针对其设置调整示例代码，而非展示通用代码。