Don't reinvent the wheel — use existing libraries, tools, and stdlib before building custom solutions. Every custom solution is maintenance burden.
From devkitnpx claudepluginhub 5uck1ess/devkitThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Before writing any non-trivial utility, helper, or tool — check if it already exists.
path.join(), os.path, filepath.Join() exist. Don't write your own.Only build custom when none of the above genuinely fit.
Every custom solution is code you maintain forever:
A well-maintained library handles all of this for you. The 20 minutes you "save" by writing it yourself costs hours in future maintenance.
Before adopting a dependency, check:
Before writing custom code, ask: "Am I willing to maintain this for the life of the project?" If the answer is no, find an existing solution. If no existing solution fits, keep the custom code as simple as possible — the less code you write, the less you maintain.