agentleFS
MicrosoftKnown publishermicrosoft/frontier-sre-agent-rvas/Student/Resources/grubify/.github/copilot-instructions.md

frontier-sre-agent-rvas / grubify

Copilot instructions7 starsChanged 17 days agoMITView on GitHub

This is a food delivery application with a React TypeScript frontend and .NET backend. Its source is retained for Azure SRE Agent investigation and remediation exercises. Source changes end at a reviewed pull request. Do not add deployment automation, Bicep/AZD infrastructure, registry credentials, or out-of-band Azure Container App updates. Prioritize user experience, maintain clean code architecture, and ensure proper error handling throughout the application.

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

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use TypeScript strict mode

    line 21
  2. Distinctive:

    Follow Material-UI design patterns

    line 22
  3. Distinctive:

    Use async/await for API calls

    line 24
  4. Distinctive:

    Follow RESTful conventions for API endpoints

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 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
<!-- Use this file to provide workspace-specific custom instructions to Copilot. For more details, visit https://code.visualstudio.com/docs/copilot/copilot-customization#_use-a-githubcopilotinstructionsmd-file -->

Grubify Food Delivery App

This is a food delivery application with a React TypeScript frontend and .NET backend. Its source is retained for Azure SRE Agent investigation and remediation exercises.

Tech Stack

  • Frontend: React 18 with TypeScript, Material-UI, React Router
  • Backend: .NET 9 Web API with Controllers
  • Runtime: Azure Container Apps provisioned by the workshop Terraform root
  • Images: canonical public grubify-api:latest and grubify-frontend:latest packages

Architecture

  • Clean separation between frontend and backend
  • RESTful API design
  • Responsive Material-UI components
  • Terraform owns runtime image references, environment variables, and replica settings

Development Guidelines

  • Use TypeScript strict mode
  • Follow Material-UI design patterns
  • Implement proper error handling
  • Use async/await for API calls
  • Follow RESTful conventions for API endpoints

API Endpoints

  • /api/restaurants - Restaurant management
  • /api/fooditems - Food item management
  • /api/cart - Shopping cart operations
  • /api/orders - Order management

UI Components

  • Modern, responsive design inspired by popular food delivery apps
  • Card-based layouts for restaurants and food items
  • Step-by-step checkout process
  • Real-time order tracking

Source changes end at a reviewed pull request. Do not add deployment automation, Bicep/AZD infrastructure, registry credentials, or out-of-band Azure Container App updates. Prioritize user experience, maintain clean code architecture, and ensure proper error handling throughout the application.

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.

Reviews can't be read right now.

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.