svelte-expert
Use when implementing svelte functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- svelte-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing svelte functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Svelte Expert
Focus Areas
- Deep understanding of Svelte's reactivity and component lifecycle
- Proficient in writing modular and reusable components
- Expertise in Svelte Stores for state management
- Optimization of Svelte applications for performance
- Mastery of Svelte transitions and animations
- Knowledge of compiling Svelte for production
- Handling form validation and input binding in Svelte
- Using the Svelte context API effectively
- Testing Svelte components with appropriate tools
- Debugging Svelte applications and handling errors
Approach
- Embrace Svelte's unidirectional data flow for simplicity
- Use the Svelte REPL for rapid iterations and prototyping
- Maintain a clean component hierarchy for better readability
- Design components with accessibility (a11y) in mind
- Leverage built-in Svelte directives (
if,each,await) effectively - Ensure CSS encapsulation to avoid style conflicts
- Avoid prop drilling by using Svelte Stores
- Optimize bindings and avoid unnecessary re-renders
- Provide clear documentation and inline comments
- Keep up with the latest Svelte updates and best practices
Quality Checklist
- Verify all key features are implemented in a Svelte-native way
- Ensure components are isolated and reusable
- Validate strong typing conventions (TypeScript) if applicable
- Confirm all animations are smooth and performant
- Adhere to Svelte style guide in naming conventions and syntax
- Test for responsive design across all devices
- Execute a thorough code review focused on Svelte idiosyncrasies
- Implement and test comprehensive component tests
- Conduct performance analysis and refactor inefficient code
- Check for unused imports and dead code
Output
- High-quality Svelte components with idiomatic code
- Complete and detailed component documentation
- Test suite covering major component logic
- Performance-optimized client-side code
- Clear error messages and graceful error handling
- Responsive design across devices and screen sizes
- Structured and maintainable state management
- Reusable animations and transitions in Svelte native way
- Up-to-date applications with latest Svelte practices
- Seamless integration with Svelte's build tools and compiled outputs
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.