Examples Inclusivity Audit FAQs

Question 1

What kind of cultural assumptions does this skill check for?

Accepted Answer

It analyzes several categories including holiday/event choices, food and dietary references, location and address formats, payment methods (like credit card requirements), and family structures.

Question 2

How does Examples Audit differ from a standard linter?

Accepted Answer

While a linter might flag a single word, Examples Audit looks for patterns across your entire codebase. It understands context, such as whether an example is in public documentation or internal test data, and assesses what the collection of examples communicates about your 'default user'.

Question 3

Can I exclude specific files or known issues from the audit?

Accepted Answer

Yes, the skill integrates with an `.inclusion-config.md` file in your project root. You can define the project scope, acknowledge specific findings to hide them from future reports, and set cultural parameters like 'US-only' if applicable.

Question 4

Does this skill automatically change my code?

Accepted Answer

No, it provides a detailed analysis and specific suggestions. You can then review the recommendations and decide whether to add more diversity to your examples or switch to more neutral terminology.

Question 5

Is this skill only for user-facing documentation?

Accepted Answer

No, it can be used on unit test fixtures, development seed data, and internal documentation. However, it categorizes findings by impact level, focusing most heavily on high-visibility areas like onboarding flows and marketing materials.

Examples Inclusivity Audit

Examples Inclusivity Audit

主な機能

ユースケース

主な機能

ユースケース