원클릭으로
inclusive-names
Generate culturally diverse names for examples, mock data, and test fixtures. Includes edge-case names that catch bugs.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Generate culturally diverse names for examples, mock data, and test fixtures. Includes edge-case names that catch bugs.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Surface code-level debt — TODO/FIXME markers, deprecated APIs, dead code, oversized units, magic numbers. Use when reviewing a module, planning cleanup work, or before a release. Not a linter — observes patterns and assesses impact.
Show available commands and explain how to use the Gotrino assistant.
Document the reasoning behind implementation decisions as markdown files. Creates decision records that future developers can reference.
Analyze mock data and examples for cultural assumptions, understanding what they communicate about who the product is for. Use when reviewing test data, documentation, or seed data.
Analyze code for internationalization issues, understanding the UI context and user impact before flagging problems. Use when reviewing code for global readiness.
Comprehensive inclusion analysis of code, examining language, internationalization, assumptions, and who might be excluded. Thorough review for releases or major features.
| name | inclusive-names |
| description | Generate culturally diverse names for examples, mock data, and test fixtures. Includes edge-case names that catch bugs. |
| allowed-tools | Read, Write, Edit |
| user-invocable | true |
Generate culturally diverse names for use in examples, mock data, and test fixtures.
Names in examples signal who you built your product for. But diverse names aren't just about representation—they're also better test data.
"If your tests only use 'John Smith', you're not testing your code. You're testing the happy path."
Names with apostrophes, diacritics, single words, and non-Latin characters catch real bugs that simple Western names miss.
Read for name lists and guidelines:
references/diverse-names.md - Names by region, gender-neutral options, edge casesThe user may request:
Always include some names that test code robustness:
| Type | Examples | What It Tests |
|---|---|---|
| Apostrophes | O'Brien, N'Golo, D'Angelo | String escaping, SQL injection |
| Diacritics | José, Müller, Björk, François | Unicode handling, encoding |
| Single names | Suharto, Madonna, Pelé | Required field assumptions |
| Long names | Wolfeschlegelsteinhausenbergerdorff | Field length limits, UI overflow |
| Non-Latin | 田中太郎, Иванов, محمد | Character encoding, font support |
| Hyphenated | García-López, Smith-Jones | Parsing, display formatting |
| Particles | Ludwig van Beethoven, Leonardo da Vinci | Sorting algorithms |
Provide names in the format the user needs:
Simple list:
Amara Okafor
Wei Chen
María García-López
Yuki Tanaka
Jordan O'Brien
JSON fixtures:
[
{ "name": "Amara Okafor", "email": "amara.o@example.com" },
{ "name": "José François", "email": "jose.f@example.com" },
{ "name": "田中太郎", "email": "tanaka.t@example.com" }
]
With flexible name fields (recommended):
const TEST_USERS = [
{ givenName: 'Amara', familyName: 'Okafor', displayName: 'Amara Okafor' },
{ givenName: 'Wei', familyName: 'Chen', displayName: 'Chen Wei' },
{ givenName: 'Suharto', familyName: null, displayName: 'Suharto' },
];
Edge-case focused:
const EDGE_CASE_NAMES = [
"O'Brien", // Apostrophe
"José García", // Diacritics
"Suharto", // Single name
"李明", // Non-Latin
"Smith-Jones", // Hyphenated
"Wolfeschlegelstein" // Long (truncated for display)
];
If the user wants to replace names in existing files:
Need 5 diverse names fast?
Amara Okafor (West Africa)
Wei Chen (East Asia)
Priya Sharma (South Asia)
María García (Latin America)
Jordan O'Brien (gender-neutral + apostrophe)
Need edge cases for testing?
O'Brien, José, Müller, 田中, Suharto, García-López