Engineering Principles

azure/engineering-principles

Ingestion architecture and implementation principles. Use for design, review, meaningful refactoring, Azure integration, document security, testing, or operational changes.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

186

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Azure/GPT-RAG --skill engineering-principles

What comes with it

5 862 bytes besides the instruction

references/ingestion-architecture.md

references/python-implementation.md

references/security-data-operations.md

references/testing-and-evidence.md

The instruction itself

1 sections, as written by the author

Ingestion engineering principles

Load only the references needed for the task:

| When the task involves | Read |

| --- | --- |

| Repository purpose, pipeline boundaries, sources, chunking, jobs, or Search | Ingestion architecture |

| Python design, async behavior, modules, or maintainability | Python implementation |

| Tests, validation, compatibility, or evidence | Testing and evidence |

| Identity, ACLs, secrets, source data, audit, or operations | Security, data, and operations |

Use these principles as design questions, not dogma. Task requirements,

executable configuration, versioned contracts, and current behavior remain

the sources of truth.

How to use it

Copy the folder

Take azure/engineering-principles from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.