rn-forge
Skill4 starsChanged 6 months agoApache-2.0View on GitHub
Generate production-ready React Native screens with React Query, typed navigation, and enterprise standards
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read agents/rn-forge.md for the full RN code generation workflow
- Very specific: line 18
Read react/REACT_QUERY_RULES.md and react/REACT_NATIVE_PATTERNS.md
- Distinctive: line 22
Always include: Screen + Components + Hooks + Queries + Service + Tests
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
React Native Screen Generation
Generate complete React Native features following enterprise patterns.
Instructions
- Read
agents/rn-forge.mdfor the full RN code generation workflow - Read
react/REACT_QUERY_RULES.mdandreact/REACT_NATIVE_PATTERNS.md - React Query MANDATORY. FlatList for all dynamic lists. StyleSheet.create always
- Data fetching at the leaf level — each component fetches its own data
- Reuse existing components — search codebase first, refactor god components
- Always include: Screen + Components + Hooks + Queries + Service + Tests
- SafeAreaView, KeyboardAvoidingView, Platform.select for iOS/Android
- Handle loading, error, empty states. Haptic feedback for confirmations
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/code-review.mdcCursor rule
- .cursor/rules/db-design.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/django-forge.mdcCursor rule
- .cursor/rules/dotnet-forge.mdcCursor rule
- .cursor/rules/flutter-forge.mdcCursor rule
- .cursor/rules/nestjs-forge.mdcCursor rule
- .cursor/rules/neuraforge.mdcCursor rule
- .cursor/rules/pr-review.mdcCursor rule
- .cursor/rules/react-forge.mdcCursor rule
- .cursor/rules/refactor.mdcCursor rule
- .cursor/rules/rn-forge.mdcCursor rule
- .cursor/rules/scaffold.mdcCursor rule
- .cursor/rules/spring-forge.mdcCursor rule
- .cursor/rules/test-forge.mdcCursor rule
- api-designSkill
- api-testingSkill
- architecture-reviewSkill
- changelogSkill
- codebase-graphSkill
- code-reviewSkill
- db-designSkill
- debugSkill
- deps-auditSkill
- design-syncSkill
- devils-advocateSkill
- devopsSkill
- django-forgeSkill
- doc-generatorSkill
- documentationSkill
- domain-setupSkill
- dotnet-forgeSkill
- explainSkill
- feature-pipelineSkill
- flutter-forgeSkill
- fullstack-orchestratorSkill
- git-worktreesSkill
- load-testingSkill
- migrateSkill
- nestjs-forgeSkill
- performance-reviewSkill
- presentation-builderSkill
- product-managerSkill
- pr-reviewSkill
- react-forgeSkill
- refactorSkill
- scaffoldSkill
- security-reviewSkill
- spring-forgeSkill
- test-forgeSkill
- ui-validationSkill
- video-creatorSkill
- workspace-protocolSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

