standard-firstlisted

Guides technical implementation to always prefer the standard, officially-documented solution over custom or AI-generated code. Use this skill whenever the agent is about to: write new code for a feature, suggest or add a library/package, scaffold a new project, or configure a framework. TRIGGER for any .NET/C#, Node.js/npm, Python, Go, Java, or other language implementation task — especially when the problem sounds like something a built-in framework feature or package registry might already solve (logging enrichment, auth, serialization, retries, health checks, migrations, etc.). Do not skip this skill just because the answer feels obvious from training data.
azborgonovo/ai-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill azborgonovo/ai-skills

# Standard-First Before implementing anything, find what already exists — a built-in framework feature, a well-maintained package, or an official pattern. The simplest solution that fully solves the stated problem is the right one; do not add custom implementations for problems that an existing package already covers. ## Step 1 — Understand the Stack Before searching for solutions, read the project's dependency and configuration files to identify the exact technology stack and what is already installed. Use `Glob` to find these files, then `Read` them: | File | What it tells you | |---|---| | `*.csproj`, `*.sln`, `global.json` | .NET version, existing NuGet packages | | `package.json`, `package-lock.json`, `yarn.lock` | Node.js runtime, installed packages | | `go.mod` | Go module path and dependencies | | `requirements.txt`, `pyproject.toml`, `Pipfile` | Python packages | | `pom.xml`, `build.gradle` | Java/Kotlin dependencies | | `Cargo.toml` | Rust crates | Reading these files prevents mismatches — e.g., looking up ASP.NET Core 9 docs when the project targets .NET 6, or suggesting a package that is already installed under a different name. If no project files are found, ask the user for the tech stack before proceeding. ## Step 2 — Check for a Technology-Specific Skill Before going to the web, check whether a skill is already available for the detected technology. Look at the `available_skills` list in your context and match against the stack identified in Step 1.