usmds
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: usmds
description: Use when building React Native mobile apps with the U.S. Mobile Design System (USMDS) by blencor…
category: design
runtime: no special runtime
---
# usmds output preview
## PART A: Task fit
- Use case: Use when building React Native mobile apps with the U.S. Mobile Design System (USMDS) by blencorp. Triggers on: imports from @/components/ui/, NativeWind className styling, npx @blen/usmds commands, react-native-usmds, federal mobile app design, USMDS components (Alert, Button, Card, Accordion, AlertDialog, Badge, Avatar, TextInput, Checkbox, RadioButton, Select, Textarea). Also use when setting up NativeWind + Tailwind theming for React Native, accessible mobile UI following federal design standards, or @rn-primitives/portal overlay components..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Quick Reference / Core Architecture / Project Setup (Quick)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when building React Native mobile apps with the U.S. Mobile Design System (USMDS) by blencorp. Triggers on: imports from @/components/ui/, NativeWind className styling, npx @blen/usmds commands, react-native-usmds, federal mobile app design, USMDS components (Alert, Button, Card, Accordion, AlertDialog, Badge, Avatar, TextInput, Checkbox, RadioButton, Select, Textarea). Also use when setting up NativeWind + Tailwind theming for React Native, accessible mobile UI following federal design standards, or @rn-primitives/portal overlay components.”.
- **02** When the source has headings, the agent prioritizes “Quick Reference / Core Architecture / Project Setup (Quick)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/path`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Quick Reference / Core Architecture / Project Setup (Quick)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: usmds
description: Use when building React Native mobile apps with the U.S. Mobile Design System (USMDS) by blencor…
category: design
source: tomevault-io/skills-registry
---
# usmds
## When to use
- Use when building React Native mobile apps with the U.S. Mobile Design System (USMDS) by blencorp. Triggers on: import…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Quick Reference / Core Architecture / Project Setup (Quick)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "usmds" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Quick Reference / Core Architecture / Project Setup (Quick)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} USMDS Development Guide
Build accessible React Native mobile interfaces using the U.S. Mobile Design System (USMDS) with NativeWind styling.
Quick Reference
- Components: See references/components.md for all components with imports and usage examples
- Setup: See references/setup.md for project initialization, Metro/Babel/Tailwind config
- Theming: See references/theming.md for design tokens, colors, and custom theme configuration
Core Architecture
USMDS has three layers:
- Components — Pre-built accessible UI from
@/components/ui/*(Button, Card, Alert, etc.) - NativeWind Styling — Tailwind CSS classes via the
classNameprop - Theme Tokens — CSS custom properties (HSL-based) for consistent design language
Components are imported individually. Styling uses NativeWind (Tailwind for React Native). Theming flows through tailwind.config.js CSS variables.
Project Setup (Quick)
# Automatic setup (recommended)
npx @blen/usmds init -y
# Or specify project path
npx @blen/usmds init -c /path/to/project
This generates: tailwind.config.js, metro.config.js, babel.config.js, global.css, and TypeScript definitions. See references/setup.md for manual setup.
Component Usage Pattern
All components import from @/components/ui/:
import { Button } from '@/components/ui/button';
import { Text } from '@/components/ui/text';
<Button onPress={handlePress}>
<Text>Click me</Text>
</Button>
Key convention: USMDS Button and most interactive components require <Text> children — they do not accept bare strings.
Styling with NativeWind
Apply Tailwind classes via className:
<Button className="w-full mt-4">
<Text>Full Width Button</Text>
</Button>
<View className="bg-background border border-border rounded-lg p-4">
<Text className="text-foreground font-medium">Themed content</Text>
<Text className="text-muted-foreground text-sm">Supporting text</Text>
</View>
Accessibility
USMDS components follow WAI-ARIA patterns for React Native:
- Alert components automatically get the
alertaccessibility role for screen readers - AlertDialog provides structured confirmation with accessible header/footer
- Accordion follows WAI-ARIA accordion pattern with proper expand/collapse semantics
- Always wrap text in
<Text>components (React Native requirement) - Use
variant="destructive"for error/danger states — provides semantic meaning
PortalHost (Required for Overlays)
Components like AlertDialog, Tooltip, Popover, and DropdownMenu require PortalHost in your root layout:
import { PortalHost } from '@rn-primitives/portal';
export default function RootLayout() {
return (
<ThemeProvider>
<Stack />
<PortalHost />
</ThemeProvider>
);
}
Without PortalHost, overlay components will not render. Add it as the last child in your root layout.
Common Patterns
Form with Validation
import { View } from 'react-native';
import { Button } from '@/components/ui/button';
import { Text } from '@/components/ui/text';
import { TextInput } from '@/components/ui/textinput';
import { Checkbox } from '@/components/ui/checkbox';
const [errors, setErrors] = useState({});
<View className="flex-1 p-4 gap-4">
<View>
<Text className="mb-2 font-medium">Email</Text>
<TextInput
value={email}
onChangeText={setEmail}
placeholder="you@example.com"
keyboardType="email-address"
autoCapitalize="none"
className={errors.email ? 'border-destructive' : ''}
/>
{errors.email && (
<Text className="text-destructive text-sm mt-1">{errors.email}</Text>
)}
</View>
<Button onPress={handleSubmit} className="mt-4">
<Text>Submit</Text>
</Button>
</View>
Card Layout
import { Card, CardHeader, CardTitle, CardDescription, CardContent, CardFooter } from '@/components/ui/card';
import { Badge } from '@/components/ui/badge';
<Card className="mb-4">
<CardHeader>
<CardTitle>Title</CardTitle>
<CardDescription>Subtitle</CardDescription>
</CardHeader>
<CardContent>
<Text className="text-muted-foreground">Body content</Text>
<View className="flex-row gap-2 mt-3">
<Badge><Text>Tag 1</Text></Badge>
<Badge variant="secondary"><Text>Tag 2</Text></Badge>
</View>
</CardContent>
<CardFooter className="gap-2">
<Button variant="outline" size="sm" className="flex-1">
<Text>Cancel</Text>
</Button>
<Button size="sm" className="flex-1">
<Text>Confirm</Text>
</Button>
</CardFooter>
</Card>
Confirmation Dialog
import {
AlertDialog, AlertDialogAction, AlertDialogCancel, AlertDialogContent,
AlertDialogDescription, AlertDialogFooter, AlertDialogHeader,
AlertDialogTitle, AlertDialogTrigger,
} from '@/components/ui/alert-dialog';
<AlertDialog>
<AlertDialogTrigger asChild>
<Button variant="outline"><Text>Delete</Text></Button>
</AlertDialogTrigger>
<AlertDialogContent>
<AlertDialogHeader>
<AlertDialogTitle>Are you sure?</AlertDialogTitle>
<AlertDialogDescription>This action cannot be undone.</AlertDialogDescription>
</AlertDialogHeader>
<AlertDialogFooter>
<AlertDialogCancel><Text>Cancel</Text></AlertDialogCancel>
<AlertDialogAction><Text>Continue</Text></AlertDialogAction>
</AlertDialogFooter>
</AlertDialogContent>
</AlertDialog>
Theme Colors
Theme uses HSL CSS variables mapped in tailwind.config.js:
| Token | Usage |
|---|---|
background / foreground |
Page background, primary text |
primary / primary-foreground |
Primary actions, emphasis |
secondary / secondary-foreground |
Secondary actions |
destructive / destructive-foreground |
Error states, danger actions |
muted / muted-foreground |
Subtle backgrounds, secondary text |
accent / accent-foreground |
Highlights, active states |
card / card-foreground |
Card surfaces |
border / input / ring |
Borders, input borders, focus rings |
See references/theming.md for full configuration.
Source: blencorp/skills — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review