القائمة
Use when adding, installing, upgrading, or pinning a package/library in any language, choosing which version to use, or when install commands fail with externally-managed-environment, SSL/certificate, DNS (gaierror), or connection errors inside a sandbox.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when handed a set/batch of iterations, plans, or work slices to carry out end to end in one run — multiple iteration/story IDs to execute, ordered by blocking edges, each with review, commit, and doc-status transitions, until the whole set is done. lazyspec or any DAG-backed backlog.
Interview the user relentlessly about a plan or design. Use when the user wants to plan/design a system, break down a problem, or asks an open question.
You MUST use this skill when authoring an iteration, work slice, or "iteration document" that hands a bounded unit of work to a coding agent — drawn from a story, card, spec, or backlog. Symptoms include an iteration that bundles several acceptance criteria, restates a spec it links to, or won't finish in one agent session.
You MUST use when writing a story/user story; when decomposing a system, feature, epic, requirement, or spec into a backlog of user stories, or whenever about to write user stories or acceptance criteria during planning. Symptoms include "break this into stories", "write the backlog", "split this epic", stories that feel too big to estimate, or technical tasks masquerading as stories.
You MUST use this skill any time you are investigating a bug/unintended behaviour, before proposing fixes
Use when comparing a running web UI against its intended design (Figma mockups or reference screenshots), reviewing visual/layout/spacing/typography fidelity of a page, component, or interaction, or when a design-vs-build diff is needed before shipping or to feed a fix loop.
| name | installing-dependencies |
| description | Use when adding, installing, upgrading, or pinning a package/library in any language, choosing which version to use, or when install commands fail with externally-managed-environment, SSL/certificate, DNS (gaierror), or connection errors inside a sandbox. |
Your training data has a cutoff; package registries have moved past it. The version in your head is stale. Two rules follow: let the package manager resolve versions from the live registry (never hand-write them), and recognize when a sandbox has no network egress so you escalate instead of debugging a phantom bug.
Run the package manager's add command. It resolves the latest stable from the live registry and writes both the manifest and the lockfile. Do NOT type a version string into the manifest from memory.
| Ecosystem | Add latest stable |
|---|---|
| npm / pnpm / yarn | npm install <pkg> · pnpm add <pkg> · yarn add <pkg> |
| python | uv add <pkg> · or pip install <pkg> (into a venv) |
| rust | cargo add <pkg> |
| go | go get <pkg>@latest |
To pin or compare versions, query the registry — don't guess:
npm view <pkg> version · npm view <pkg> versions --jsonpip index versions <pkg> · uv pip index <pkg>cargo search <pkg> · go list -m -versions <pkg>Verify what landed. After install, read the manifest/lockfile. The installed version is the source of truth, not your recollection.
Installs and version queries require network egress. A no-egress sandbox fails them. These error signatures all mean no network, not a real bug — stop diagnosing, don't retry:
CERTIFICATE_VERIFY_FAILED, OSStatus -26276gaierror, nodename nor servname providedConnection refused / timeout, or Permission ... denied on curlOn a network block, escalate immediately: give the user the exact command(s) to run. They can run it inline with the ! <command> prompt prefix so output lands in the session.
externally-managed-environment is different — that's PEP 668, a policy block, not a network block. Fix with a venv (python3 -m venv). Never pip install --break-system-packages.
Don't pollute the repo. Create venvs / scratch installs under $TMPDIR, not the project root, unless the project owns that environment.
| Mistake | Do instead |
|---|---|
Writing "pkg": "^3.x.x" into manifest from memory | Run the add command; registry resolves latest |
| Retrying a failing install 5× against SSL/DNS errors | Recognize no-egress → escalate with exact command |
pip install --break-system-packages | Use a venv |
.venv / node_modules in project root for scratch work | Put scratch envs in $TMPDIR |
| Trusting the version in your head | Read the lockfile after install |