Name: no-hardcoded-ui-text
Author: Zynapses

Prompt file imported from Zynapses/Radiant (.windsurf/workflows/no-hardcoded-ui-text.md). Copyright stays with the author.

No Hardcoded UI Text Policy

MANDATORY: All user-facing text in Radiant and Think Tank must be localized through the localization registry. No hardcoded strings are permitted.

Rules

NEVER hardcode UI text - All user-visible strings must use the localization system
Register all strings - Every new UI string must be registered in the localization registry
Use translation keys - Reference strings by their localization key, not raw text
Include all languages - Translations must be provided for all supported languages

Supported Languages

English (en) - Primary
Spanish (es)
French (fr)
German (de)
Italian (it)
Portuguese (pt)
Japanese (ja)
Korean (ko)
Chinese Simplified (zh-CN)
Chinese Traditional (zh-TW)
Arabic (ar)
Hebrew (he)
Russian (ru)
Dutch (nl)
Polish (pl)
Turkish (tr)

Implementation

1. Register String in Backend

import { localizationService } from '@/services/localization';

// Register the string
await localizationService.registerString({
  key: 'thinktank.chat.send_button',
  defaultText: 'Send Message',
  context: 'Button label for sending chat messages',
  category: 'thinktank',
});

2. Use in React Components

import { useTranslation } from '@/hooks/useTranslation';

function ChatInput() {
  const { t } = useTranslation();
  
  return (
    <button>{t('thinktank.chat.send_button')}</button>
  );
}

3. Add Translations via Admin Dashboard

Navigate to: Admin Dashboard → Localization → Add Translation

Or use the API:

await localizationService.setTranslation(
  'thinktank.chat.send_button',
  'es',
  'Enviar Mensaje'
);

String Key Naming Convention

Use dot-notation with these prefixes:

common.* - Shared across all apps
admin.* - Admin dashboard specific
thinktank.* - Think Tank specific
deployer.* - Swift Deployer specific
errors.* - Error messages
validation.* - Form validation messages

Examples:

common.buttons.save
common.buttons.cancel
thinktank.chat.placeholder
thinktank.settings.language_label
errors.network.connection_failed

Code Review Checklist

Before approving any PR, verify:

No hardcoded strings in JSX/TSX
No hardcoded strings in Swift UI
All new strings registered with registerString()
Translation keys follow naming convention
Context provided for translators
Translations added for at least English + Spanish

Exceptions

The ONLY exceptions are:

Brand names: "Radiant", "Think Tank"
Technical identifiers shown to developers
Log messages (not user-facing)
Test fixtures

Enforcement

This policy is enforced by:

ESLint rule: no-hardcoded-strings (custom)
Code review checklist
CI/CD pipeline checks

Install no-hardcoded-ui-text and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# No Hardcoded UI Text Policy **MANDATORY**: All user-facing text in Radiant and Think Tank must be localized through the localization registry. No hardcoded strings are permitted. ## Rules 1. **NEVER hardcode UI text** - All user-visible strings must use the localization system 2. **Register all strings** - Every new UI string must be registered in the localization registry 3. **Use translation keys** - Reference strings by their localization key, not raw text 4. **Include all languages** - Translations must be provided for all supported languages ## Supported Languages - English (en) - Primary - Spanish (es) - French (fr) - German (de) - Italian (it) - Portuguese (pt) - Japanese (ja) - Korean (ko) - Chinese Simplified (zh-CN) - Chinese Traditional (zh-TW) - Arabic (ar) - Hebrew (he) - Russian (ru) - Dutch (nl) - Polish (pl) - Turkish (tr) ## Implementation ### 1. Register String in Backend ```typescript import { localizationService } from '@/services/localization'; // Register the string await localizationService.registerString({ key: 'thinktank.chat.send_button', defaultText: 'Send Message', context: 'Button label for sending chat messages', category: 'thinktank', }); ``` ### 2. Use in React Components ```tsx import { useTranslation } from '@/hooks/useTranslation'; function ChatInput() { const { t } = useTranslation(); return ( <button>{t('thinktank.chat.send_button')}</button> ); } ``` ### 3. Add Translations via Admin Dashboard Navigate to: Admin Dashboard → Localization → Add Translation Or use the API: ```typescript await localizationService.setTranslation( 'thinktank.chat.send_button', 'es', 'Enviar Mensaje' ); ``` ## String Key Naming Convention Use dot-notation with these prefixes: - `common.*` - Shared across all apps - `admin.*` - Admin dashboard specific - `thinktank.*` - Think Tank specific - `deployer.*` - Swift Deployer specific - `errors.*` - Error messages - `validation.*` - Form validation messages Examples: - `common.buttons.save` - `common.buttons.cancel` - `thinktank.chat.placeholder` - `thinktank.settings.language_label` - `errors.network.connection_failed` ## Categories - `buttons` - Button labels - `labels` - Form labels - `placeholders` - Input placeholders - `messages` - User-facing messages - `errors` - Error messages - `tooltips` - Tooltip text - `headings` - Page/section headings - `navigation` - Nav menu items ## Code Review Checklist Before approving any PR, verify: - [ ] No hardcoded strings in JSX/TSX - [ ] No hardcoded strings in Swift UI - [ ] All new strings registered with `registerString()` - [ ] Translation keys follow naming convention - [ ] Context provided for translators - [ ] Translations added for at least English + Spanish ## Exceptions The ONLY exceptions are: - Brand names: "Radiant", "Think Tank" - Technical identifiers shown to developers - Log messages (not user-facing) - Test fixtures ## Enforcement This policy is enforced by: 1. ESLint rule: `no-hardcoded-strings` (custom) 2. Code review checklist 3. CI/CD pipeline checks

{ "prompt": "# No Hardcoded UI Text Policy\n\n**MANDATORY**: All user-facing text in Radiant and Think Tank must be localized through the localization registry. No hardcoded strings are permitted.\n\n## Rules\n\n1. **NEVER hardcode UI text** - All user-visible strings must use the localization system\n2. **Register all strings** - Every new UI string must be registered in the localization registry\n3. **Use translation keys** - Reference strings by their localization key, not raw text\n4. **Include all languages** - Translations must be provided for all supported languages\n\n## Supported Languages\n\n- English (en) - Primary\n- Spanish (es)\n- French (fr)\n- German (de)\n- Italian (it)\n- Portuguese (pt)\n- Japanese (ja)\n- Korean (ko)\n- Chinese Simplified (zh-CN)\n- Chinese Traditional (zh-TW)\n- Arabic (ar)\n- Hebrew (he)\n- Russian (ru)\n- Dutch (nl)\n- Polish (pl)\n- Turkish (tr)\n\n## Implementation\n\n### 1. Register String in Backend\n\n```typescript\nimport { localizationService } from '@/services/localization';\n\n// Register the string\nawait localizationService.registerString({\n key: 'thinktank.chat.send_button',\n defaultText: 'Send Message',\n context: 'Button label for sending chat messages',\n category: 'thinktank',\n});\n```\n\n### 2. Use in React Components\n\n```tsx\nimport { useTranslation } from '@/hooks/useTranslation';\n\nfunction ChatInput() {\n const { t } = useTranslation();\n \n return (\n <button>{t('thinktank.chat.send_button')}</button>\n );\n}\n```\n\n### 3. Add Translations via Admin Dashboard\n\nNavigate to: Admin Dashboard → Localization → Add Translation\n\nOr use the API:\n```typescript\nawait localizationService.setTranslation(\n 'thinktank.chat.send_button',\n 'es',\n 'Enviar Mensaje'\n);\n```\n\n## String Key Naming Convention\n\nUse dot-notation with these prefixes:\n- `common.*` - Shared across all apps\n- `admin.*` - Admin dashboard specific\n- `thinktank.*` - Think Tank specific\n- `deployer.*` - Swift Deployer specific\n- `errors.*` - Error messages\n- `validation.*` - Form validation messages\n\nExamples:\n- `common.buttons.save`\n- `common.buttons.cancel`\n- `thinktank.chat.placeholder`\n- `thinktank.settings.language_label`\n- `errors.network.connection_failed`\n\n## Categories\n\n- `buttons` - Button labels\n- `labels` - Form labels\n- `placeholders` - Input placeholders\n- `messages` - User-facing messages\n- `errors` - Error messages\n- `tooltips` - Tooltip text\n- `headings` - Page/section headings\n- `navigation` - Nav menu items\n\n## Code Review Checklist\n\nBefore approving any PR, verify:\n\n- [ ] No hardcoded strings in JSX/TSX\n- [ ] No hardcoded strings in Swift UI\n- [ ] All new strings registered with `registerString()`\n- [ ] Translation keys follow naming convention\n- [ ] Context provided for translators\n- [ ] Translations added for at least English + Spanish\n\n## Exceptions\n\nThe ONLY exceptions are:\n- Brand names: \"Radiant\", \"Think Tank\"\n- Technical identifiers shown to developers\n- Log messages (not user-facing)\n- Test fixtures\n\n## Enforcement\n\nThis policy is enforced by:\n1. ESLint rule: `no-hardcoded-strings` (custom)\n2. Code review checklist\n3. CI/CD pipeline checks", "variables": [], "notes": "Policy - No hardcoded UI text allowed, all strings must be localized", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/Zynapses/Radiant", "path": ".windsurf/workflows/no-hardcoded-ui-text.md", "ref": "dfcafdfbbf2191ee48921207c5c8a8ca77da957b", "url": "https://github.com/Zynapses/Radiant/blob/dfcafdfbbf2191ee48921207c5c8a8ca77da957b/.windsurf/workflows/no-hardcoded-ui-text.md", "key": "Zynapses/Radiant/.windsurf/workflows/no-hardcoded-ui-text.md" } } }

no-hardcoded-ui-text

About