Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Best practices for developing zensical/Material for MkDocs static sites. Covers installation, virtual environments, project structure, responsive images, CSS, media embedding, and verification. Use for ANY Mate...
Create new Claude Code skills with proper structure and best practices. Use when the user wants to create a new skill, extend Claude's capabilities, or needs help structuring a SKILL.md file.
Download NASA's Astronomy Picture of the Day (user)
Set up custom Claude Code status line with Nerd Font icons, colors, git status, usage tracking, system info, and project context. NO EMOJIS - only Nerd Font icons and symbols. Use when configuring statusline, s...
Conventions for custom event naming, dispatching, and handling between components. Use when implementing component communication.
Strategies and patterns for testing components through unit tests and end-to-end tests. Use when implementing tests or test infrastructure.
Patterns for real-time client-side filtering, searching, and sorting of lists. Use when implementing dynamic search or filter features.
Best practices for component CSS, design system consistency, and layout patterns. Use when authoring component styles.
Scaffold and conventions to create a new UI component following project patterns (no Shadow DOM, static stylesheet registration, pixEngine templates). Use when adding a new custom element to the app.
Features and safe usage patterns for the pixEngine template engine used in the repository. Use when authoring templates to ensure security and correct rendering.
Patterns for persisting and retrieving application data. Use when implementing data persistence, caching, or session management.
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
Process expense claims by matching YNAB transactions with uploaded receipts. Use when the user mentions claims, expenses, reimbursements, receipts, or YNAB TODOs.
Workflow for analyzing and fixing GitHub issues. Use when given an issue number to investigate and resolve.
Principal Software Architect for Rainze. Use when implementing features, writing code, or creating modules. Expert in Python + Rust hybrid architecture with 9 coding commandments.
Analyze repository structure and generate comprehensive index. Use to understand codebase organization or create repo-index.md.
Run comprehensive quality checks including linting, type checking, and tests. Use before committing or when validating code changes.
Technical specification writer. Use when creating detailed technical documentation, API specifications, or architecture documents.
Build and update Rainze code using the PRD, tech stack, and module sub-PRDs. Use this when writing Python/Rust for Rainze, aligning with the architecture, method signatures, class/layout definitions, and coding...
PRD document analyst. Use when analyzing requirements, creating Interface Flow documentation, or understanding module interactions.
Code review assistant. Use to review code changes, identify issues, and provide improvement suggestions with priority levels.
Rust expert for rainze_core PyO3 module. Use when working on Rust code, performance-critical components, or Python-Rust FFI.
Git commit message assistant following Conventional Commits specification. Use after making code changes to create well-structured commit messages.
Use SvelteKit remote functions (query, form, command, prerender) for type-safe client-server communication, data fetching, form handling, and mutations.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.