agentleFS
Sign inStart free
vindreshsinghvindreshsingh/engineering-skills/.github/copilot-instructions.md

engineering-skills

Copilot instructions0 starsChanged 5 months agoMITView on GitHub

GitHub Copilot reads this file as repository custom instructions. If there's even a ~1% chance a skill applies to the task, consult the router and follow the matching skill before acting — before clarifying questions, before code. Partial application counts as skipping. The user's explicit instructions always take precedence. - Router: skills/skill-router/SKILL.md maps the task to the skill that should govern it; then follow that skill's SKILL.md step by step. - Whole feature: skills/orchestrated-delivery/SKILL.md (define → plan → build →…

The file

We split this copilot-instructions.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If there's even a ~1% chance a skill applies to the task, consult the router and follow the matching skill before acting — before …

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

engineering-skills — GitHub Copilot

GitHub Copilot reads this file as repository custom instructions.

The rule

If there's even a ~1% chance a skill applies to the task, consult the router and follow the matching skill before acting — before clarifying questions, before code. Partial application counts as skipping. The user's explicit instructions always take precedence.

How to use the skills

  • Router: skills/skill-router/SKILL.md maps the task to the skill that should govern it; then follow that skill's SKILL.md step by step.
  • Whole feature: skills/orchestrated-delivery/SKILL.md (define → plan → build → verify → review → ship).
  • Personas: agents/sdlc/ and agents/marketing/.
  • Full guidance: AGENTS.md.

Skills are processes to follow, not reference docs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free