template-engine
Features and safe usage patterns for the pixEngine template engine used in the repository. Use when authoring templates to ensure security and correct rendering.
Découvrez les skills Développement, comparez leurs dépôts et consultez leurs instructions.
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.
Use the Svelte MCP server tools for Svelte 5 and SvelteKit documentation, code analysis, and playground links
Apply the 100 Hours Tracker "Lazy Lofi" brand styling to UI components, pages, and design elements. Use when creating or modifying any visual elements in the application.
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Trigg...
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
Resume interrupted flow:work session from last checkpoint. Reads flow-progress.txt to restore context and continue work.
John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review...
Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture revi...
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executin...
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.