standard-first

Guides implementation toward built-in framework features and official packages over custom code.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/azborgonovo/ai-skills --skill standard-first-azborgonovo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standard-first
Source: https://github.com/azborgonovo/ai-skills/tree/main/skills/engineering-practices/standard-first
Command: npx skills add https://github.com/azborgonovo/ai-skills --skill standard-first-azborgonovo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers and AI assistants often write custom code for problems that a framework feature or a well-maintained package already solves, leading to unnecessary maintenance burden, security gaps, and outdated patterns copied from training data. ## Core Features & Use Cases - Stack Detection: Reads project manifests like package.json, *.csproj, go.mod, and requirements.txt to pin the exact framework version before recommending anything. - Registry and Documentation Search: Searches package registries (NuGet, npm, PyPI) and fetches current official documentation via WebSearch, WebFetch, or the ctx7 CLI instead of relying on memory. - Decision Hierarchy: Ranks solutions as built-in framework feature first, official package second, and custom code only as a last resort. - Use Case: When asked to add retry logic to HTTP calls in a .NET project, the skill checks the project files, finds Polly on NuGet, reads its official docs, and implements the recommended pattern with the install command. ## Quick Start Ask the assistant to implement a feature such as logging enrichment or health checks and require it to check for an official package or built-in framework feature before writing any custom code.

Frequently Asked Questions about standard-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid writing custom code when a package already exists?▼

Search the package registry of your stack first, naming the registry in the query, such as "retry logic nuget" or "log masking npm". A well-maintained package with active updates and clear docs almost always beats hand-rolled code.

How to check which framework version a project uses before implementing?▼

Read the dependency and configuration manifests in the project, such as *.csproj, package.json, go.mod, requirements.txt, or pom.xml, plus their lockfiles. This pins the exact version so you consult the correct documentation.

Should I use a built-in framework feature or a third-party package?▼

Prefer the built-in framework feature when it covers the need, since it adds no dependency. Choose an official or well-maintained package when the built-in option is insufficient, and write custom code only when neither works.

Why is relying on AI training data for package APIs risky?▼

Official documentation changes and package APIs evolve, so training-data patterns may be outdated or superseded. Fetch the current docs from the vendor domain, such as learn.microsoft.com or pkg.go.dev, before implementing.

When is custom code the right choice over a library?▼

Custom code is appropriate only when no built-in framework feature and no well-maintained package adequately solves the problem. Even then, follow official best-practice patterns rather than minimal getting-started snippets.