搜索

PythonReactSEOPDF

yanko-belov AI Skills

GitHub ↗

浏览 yanko-belov 维护的已发布 AI 技能,比较用途与说明,并通过来源仓库了解安装方式。

作者统计

已收录技能

32

收录技能的仓库 Stars 合计

192

仓库 Forks

0

平均每个技能的仓库 Stars

6

同一仓库中的多个技能可能共享 Stars,合计包含重复仓库数据。

32 个技能

全部技能

GitHub

caching

yanko-belov

Use when same data is fetched repeatedly. Use when database queries are slow. Use when implementing caching without invalidation strategy.

GitHub

keep-it-simple

yanko-belov

Use when tempted to write clever code. Use when solution feels complex. Use when showing off skills instead of solving problems.

GitHub

skill-awareness

yanko-belov

Always active. Tracks usage of code-craft skills across sessions. Log skill applications to enable analytics and identify gaps.

GitHub

race-conditions

yanko-belov

Use when multiple operations access shared state. Use when order of operations matters. Use when "it works most of the time" but occasionally fails mysteriously.

GitHub

error-boundaries

yanko-belov

Use when deciding where to catch errors. Use when errors propagate too far or not far enough. Use when designing component/service isolation.

GitHub

api-versioning

yanko-belov

Use when designing or modifying APIs. Use when adding breaking changes. Use when clients depend on API stability.

GitHub

dependency-inversion-principle

yanko-belov

Use when a class creates its own dependencies. Use when instantiating concrete implementations inside a class. Use when told to avoid dependency injection for simplicity.

GitHub

fail-fast

yanko-belov

Use when handling errors. Use when tempted to catch and swallow exceptions. Use when returning default values to hide failures.

GitHub

deadlock-prevention

yanko-belov

Use when acquiring multiple locks. Use when operations wait for each other. Use when system hangs without crashing.

GitHub

liskov-substitution-principle

yanko-belov

Use when creating subclasses or implementing interfaces. Use when tempted to override methods with exceptions or no-ops. Use when inheritance hierarchy feels wrong.

GitHub

you-aint-gonna-need-it

yanko-belov

Use when tempted to add features "for later". Use when building "production-ready" systems before needed. Use when adding flexibility that isn't required yet.

GitHub

exception-hierarchies

yanko-belov

Use when creating custom exceptions. Use when error handling feels chaotic. Use when catch blocks are too broad or too specific.

GitHub

open-closed-principle

yanko-belov

Use when adding new functionality to existing code. Use when tempted to add if/else or switch branches. Use when extending behavior of existing classes.

GitHub

separation-of-concerns

yanko-belov

Use when component does too many things. Use when mixing data fetching, logic, and presentation. Use when code is hard to test.

GitHub

lazy-loading

yanko-belov

Use when loading all data upfront. Use when initial page load is slow. Use when fetching data that might not be needed.

GitHub

immutability

yanko-belov

Use when modifying objects or arrays. Use when tempted to mutate function parameters. Use when state changes cause unexpected bugs.

GitHub

law-of-demeter

yanko-belov

Use when accessing nested object properties. Use when chaining method calls. Use when reaching through objects to get data.

GitHub

encapsulation

yanko-belov

Use when exposing internal state. Use when making fields public for convenience. Use when external code modifies object internals.

GitHub

error-responses

yanko-belov

Use when returning errors from APIs. Use when exposing internal errors. Use when error responses lack structure.

GitHub

n-plus-one-prevention

yanko-belov

Use when fetching related data in loops. Use when seeing multiple queries for one request. Use when database is slow on list endpoints.

GitHub

idempotency

yanko-belov

Use when creating mutation endpoints. Use when trusting frontend to prevent duplicates. Use when payments or critical operations can be repeated.

GitHub

rest-conventions

yanko-belov

Use when designing API endpoints. Use when using wrong HTTP methods. Use when POST is used for reads.

默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。