agentleFS
MicrosoftKnown publishermicrosoft/Copilot-Managed-Runtime/plugins/copilot-managed-runtime/skills/add-backend/SKILL.md

add-backend

Skill4 starsChanged 8 days agoMITView on GitHub

Add an app backend with `ms app add backend --provider rayfin`. Currently covers database entities and client integration. Use only when the user explicitly requests a database, /add-backend, or Rayfin.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If rayfin/rayfin.yml exists, use the existing configuration.

    line 14
  2. Very specific:

    Keep the existing app layout and exclude rayfin/.temp/ from version control.

    line 21
  3. Very specific:

    Run from the app root before continuing so the declared dependencies and their version-matched docs are available in node_modules:

    line 28
  4. Distinctive:

    Use the app's existing package manager and lockfile if it does not use npm.

    line 35
  5. Distinctive:

    Read the installed package docs identified in these references, then follow them in order:

    line 42
  6. Very specific:

    When invoked from /create-app, complete data modeling in Step 9 and return the entity/client paths.

    line 48
  7. Distinctive:

    Use the normal app build and deploy workflow, not a separate Rayfin provisioning workflow.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Shared instructions: shared-instructions.md

Add an app backend

Required first: pass the Rayfin feature gate.

1. Set up the database

If rayfin/rayfin.yml exists, use the existing configuration. Otherwise, run:

ms app add backend --provider rayfin --json

This creates the backend configuration, TypeScript configuration and rayfin/data/. Keep the existing app layout and exclude rayfin/.temp/ from version control.

This prepares the app's backend definitions; it does not provision a database. Rayfin is the app backend, not an existing database to select or connect to.

2. Install dependencies

Run from the app root before continuing so the declared dependencies and their version-matched docs are available in node_modules:

npm install

Use the app's existing package manager and lockfile if it does not use npm. Report installation or peer-dependency errors; do not force-install or downgrade the app to bypass them. Add missing direct dependencies only as required by the implementation described in the references.

3. Implement and check the app

Read the installed package docs identified in these references, then follow them in order:

  • Data modeling: entities, permissions and required Copilot Managed Runtime host initialization.
  • CRUD UI: lists, forms, mutations and persistence checks.

When invoked from /create-app, complete data modeling in Step 9 and return the entity/client paths; that workflow handles UI implementation and checks in Steps 10-11. Standalone use continues through both references.

4. Follow the app lifecycle

Use the normal app build and deploy workflow, not a separate Rayfin provisioning workflow.

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.