/create-view
Generate a SwiftUI view with proper architecture and best practices.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/create-view
Context preview
What this command does when you run it.
Generate a SwiftUI view with proper architecture and best practices.
Command definition
create-view.md/create-view - Create SwiftUI View
Generate a SwiftUI view with proper architecture and best practices.
Steps
1. Ask the user for the view name, purpose, and data requirements 2. Determine the view type: screen (full page), component (reusable), or sheet (modal) 3. Create the SwiftUI view file with the appropriate structure 4. Add @State, @Binding, @ObservedObject, or @EnvironmentObject properties as needed 5. Implement the view body with proper layout: VStack, HStack, ZStack, List, or Grid 6. Add navigation elements: NavigationLink, sheet, alert, or confirmationDialog 7. Include loading, empty, and error states with appropriate UI 8. Add accessibility modifiers: accessibilityLabel, accessibilityHint, accessibilityValue 9. Implement dark mode support with proper color assets 10. Create a PreviewProvider with multiple preview configurations 11. Add the view to the navigation flow in the appropriate coordinator or router 12. Document the view's purpose, parameters, and usage examples
Rules
- Follow MVVM architecture: views should not contain business logic
- Use @StateObject for owned data, @ObservedObject for injected data
- Keep views small; extract subviews for sections over 30 lines
- Use SF Symbols for icons instead of custom assets when available
- Support Dynamic Type for all text elements
- Add proper keyboard handling for form views
- Use the project's design system colors and typography
Read more
/create-view - Create SwiftUI View
Generate a SwiftUI view with proper architecture and best practices.
Steps
1. Ask the user for the view name, purpose, and data requirements 2. Determine the view type: screen (full page), component (reusable), or sheet (modal) 3. Create the SwiftUI view file with the appropriate structure 4. Add @State, @Binding, @ObservedObject, or @EnvironmentObject properties as needed 5. Implement the view body with proper layout: VStack, HStack, ZStack, List, or Grid 6. Add navigation elements: NavigationLink, sheet, alert, or confirmationDialog 7. Include loading, empty, and error states with appropriate UI 8. Add accessibility modifiers: accessibilityLabel, accessibilityHint, accessibilityValue 9. Implement dark mode support with proper color assets 10. Create a PreviewProvider with multiple preview configurations 11. Add the view to the navigation flow in the appropriate coordinator or router 12. Document the view's purpose, parameters, and usage examples
Rules
- Follow MVVM architecture: views should not contain business logic
- Use @StateObject for owned data, @ObservedObject for injected data
- Keep views small; extract subviews for sections over 30 lines
- Use SF Symbols for icons instead of custom assets when available
- Support Dynamic Type for all text elements
- Add proper keyboard handling for form views
- Use the project's design system colors and typography
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

