security-patterns
Use when working with Electron - IPC security, renderer isolation, Node API access
Browse published AI skills maintained by andyngdz. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
13Repository stars across indexed skills
51Repository forks
0Average repository stars per indexed skill
4Repository stars may repeat across skills from the same repository.
Use when working with Electron - IPC security, renderer isolation, Node API access
Use when refactoring or implementing features - validation, component design, API research
Use when writing tests - test structure, verification steps, coverage goals
Use always - non-negotiable rules for TypeScript safety, socket events, and React patterns
Use when starting work - guidelines for asking questions and commit policies
Use when writing tests - test structure, mocking patterns, pre-commit checks
Use when exiting plan mode - where to save implementation plans
Use when adding error handling - exception patterns, HTTP codes, domain exceptions
Use when starting work - guidelines for asking questions and commit policies
Apply Martin Fowler's refactoring patterns - extract variables to eliminate repetition, split temporary variables, replace temp with query for cleaner, more maintainable code
Master code organization - encapsulation with wrapper methods, file modularity (split >150 lines), one function one responsibility, descriptive naming, minimal comments
Master type safety patterns - fix type errors at source, never use type: ignore or any, prefer Pydantic models, use type stubs for external libraries
Use when adding logging to features - structured logging with LoggerService categories
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.