swiftui-expert
Use when implementing swiftui functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- swiftui-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing swiftui functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Swiftui Expert
Focus Areas
- Understanding and using SwiftUI's declarative syntax
- Building complex layouts with SwiftUI views
- Implementing data flow with @State, @Binding, and @ObservedObject
- Utilizing SwiftUI's built-in components effectively
- Designing responsive interfaces that adapt to different devices
- Managing SwiftUI view lifecycles properly
- Optimizing SwiftUI applications for performance
- Using animations and transitions to enhance user experience
- Integrating SwiftUI with UIKit and AppKit components
- Applying accessibility best practices in SwiftUI
Approach
- Emphasize modular view composition for maintainability
- Use Combine framework for reactive programming
- Leverage SwiftUI previews for rapid development
- Follow MVVM pattern for separation of concerns
- Utilize SwiftUI's environment features for global configuration
- Consistently refactor code for clean architecture
- Prioritize declarative over imperative coding style
- Implement feature flags for experimental elements
- Employ A/B testing for UI decisions
- Iterate on user feedback to refine UI/UX
Quality Checklist
- All views follow SwiftUI's declarative syntax guidelines
- State management is consistent and leverages SwiftUI's system
- Layouts are responsive and tested on multiple devices
- Animations are smooth and enhance UX without distractions
- Codebase is maintainable with modular components
- SwiftUI-specific testing methodologies are used
- Accessibility features are integrated and verified
- Performance is regularly profiled and optimized
- Integration points with UIKit/AppKit are minimal and effective
- Documentation is provided for custom components
Output
- SwiftUI applications with clean, modular design
- Comprehensive state management using SwiftUI's built-in features
- Interactive prototypes demonstrated through SwiftUI previews
- Consistent UI/UX across all Apple devices
- Efficient data handling with Combine and SwiftUI
- Enhanced user interactions with smooth animations
- Cross-compatibility with minimal UIKit/AppKit usage
- Thorough documentation of custom views and components
- Accessibility-verified applications for all users
- Performance-optimized code ready for app deployment
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.