agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/Copilot-Managed-Runtime/samples/TaskManager/AGENTS.md

Copilot-Managed-Runtime / TaskManager

AGENTS.md4 starsChanged 8 days agoMITView on GitHub

Guidance for coding agents working in this repository. Task Manager: a React 19 + Vite + TypeScript sample app hosted on Copilot Managed Runtime (Windows 95 styling, shadcn/ui, Tailwind v4, TanStack Query). Work items come from Azure DevOps; the app's own data goes through the storage interface. See README.md for features and configuration. - src/pages/home.tsx — thin shell only. Put tab UI in src/features/<tab>/. - src/lib/ — domain logic (Azure DevOps queries and writes, trackers, tags, retro, notes, feedback). -…

  • Reads credentials

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All app-owned data goes through src/storage (collections or provider.kv(...)).

    line 23
  2. Very specific:

    Use withConflictRetry + ifVersion for read-modify-write updates.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md

Guidance for coding agents working in this repository.

What this is

Task Manager: a React 19 + Vite + TypeScript sample app hosted on Copilot Managed Runtime (Windows 95 styling, shadcn/ui, Tailwind v4, TanStack Query). Work items come from Azure DevOps; the app's own data goes through the storage interface. See README.md for features and configuration.

Structure

  • src/pages/home.tsx — thin shell only. Put tab UI in src/features/<tab>/.
  • src/lib/ — domain logic (Azure DevOps queries and writes, trackers, tags, retro, notes, feedback).
  • src/connectors/ — adapters over the generated connector clients. Only these files may import generated/ (ESLint enforces it). Everything else calls connectors() from src/connectors.
  • src/storage/ — core/ is shared code synced from elsewhere: never edit it. collections.ts defines this app's collections (zod), index.ts the provider registry.
  • src/config.ts — the only place that reads import.meta.env.

Rules

  • All app-owned data goes through src/storage (collections or provider.kv(...)). Never use localStorage, sessionStorage or indexedDB directly (ESLint enforces it).
  • Use withConflictRetry + ifVersion for read-modify-write updates.
  • The only role concept is admins.json (root), read by src/lib/admins.ts (useIsAdmin) to hide the admin tabs listed in ADMIN_TABS (src/hooks/use-app-tab.ts). It is a UI convenience, not security: Azure DevOps and the storage backend authorize writes. Don't add other role checks.
  • Route every external or user-entered link through safeUrl(); render HTML only via SafeRichText.
  • Log with src/lib/logger.ts (no-op in production); never log payloads or identities.
  • generated/ and .ms/ are produced by npx ms app add data-source in the user's copy and committed to their own app repository, never to this sample.

Skills

  • .github/skills/setup-taskmanager/ — first-time setup (app creation, connectors, .env.local).
  • .github/skills/add-data-source/ — move app data to SharePoint, Dataverse or another backend.

Commands

npm test             # unit tests (no setup needed)
npm run lint         # includes storage/connector boundary rules
npm run typecheck    # requires generated/ (after setup)
npm run check-setup  # verifies ms.config.json and generated connector services
npm run dev          # dev server (runs check-setup first)

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