frontier-ghcp-ttt-rvas / agent-tasks
Copilot instructions3 starsChanged 2 months agoMITView on GitHub
Small Express API with in-memory storage. Node 22 or later.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- sessions/session-m2-03-spaces-and-context/lab/solution/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m3-02-cloud-agent/lab/starter/copilot-instructions.mdCopilot instructions
- sessions/session-m4-02-iac-with-copilot/lab/solution/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m4-02-iac-with-copilot/lab/starter/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m5-03-hve-core-challenge/lab/solution/decision-api/.github/copilot-instructions.mdCopilot instructions
- baoyu-infographicSkill
- diagram-creatorSkill
- docxSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- pdfSkill
- pptxSkill
- rvap-brandSkill
- skill-creatorSkill
- xlsxSkill
- impeccableSkill
- session-format-validatorSkill
- grill-meSkill
- release-notesSkill
- decision-interviewSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Run tests with npm test. Run them after every code change.
- Very specific: line 6
Keep route handlers in src/app.js and helpers in src/utils.js.
- Distinctive: line 8
Do not add dependencies.
- Very specific: line 9
Test files use node:test and node:assert.
≈ “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.
Files
Task API
Small Express API with in-memory storage. Node 22 or later.
- Run tests with
npm test. Run them after every code change. - Keep route handlers in
src/app.jsand helpers insrc/utils.js. - Change the smallest amount of code that fixes the problem. Do not refactor.
- Do not add dependencies.
- Test files use
node:testandnode:assert.
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
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.

