Expand toolkit to 135 agents, 120 plugins, 796 total files

- Add 60 new agents across all 10 categories (75 -> 135)
- Add 95 new plugins with command files (25 -> 120)
- Update all agents to use model: opus
- Update README with complete plugin/agent tables
- Update marketplace.json with all 120 plugins
This commit is contained in:
Rohit Ghumare
2026-02-04 21:08:28 +00:00
parent 79573df7cb
commit c3f43d8b61
540 changed files with 22594 additions and 281 deletions

View File

@@ -0,0 +1,6 @@
{
"name": "react-native-dev",
"version": "1.0.0",
"description": "React Native mobile development with platform-specific optimizations",
"commands": ["commands/create-screen.md", "commands/native-module.md"]
}

View File

@@ -0,0 +1,30 @@
Create a React Native screen with navigation, layout, and platform-specific handling.
## Steps
1. Define the screen requirements:
2. Set up the screen file:
3. Build the layout:
4. Add data fetching:
5. Add navigation:
6. Test on both iOS and Android simulators.
7. Handle keyboard avoidance for forms.
## Format
```
Screen: <name>
Navigator: <stack|tab|drawer>
Data: <API endpoints or data sources>
Platform Handling: <iOS/Android differences>
```
## Rules
- Always use SafeAreaView for screens that touch screen edges.
- Handle both iOS and Android keyboard behavior.
- Use FlatList over ScrollView for long lists (performance).

View File

@@ -0,0 +1,30 @@
Create a React Native native module to bridge platform-specific functionality.
## Steps
1. Define the native module interface:
2. Create the TypeScript interface:
3. Implement the iOS native code (Swift/Objective-C):
4. Implement the Android native code (Kotlin/Java):
5. Handle platform differences:
6. Test the module on both platforms.
7. Document the module API and usage.
## Format
```
Module: <name>
Methods:
- <method>(params): <return type>
Events:
```
## Rules
- Always provide TypeScript types for the module interface.
- Handle errors consistently across both platforms.
- Use promises over callbacks for async operations.