agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/webui/.github/skills/create-example/SKILL.md

create-example

Skill100 starsChanged 36 days agoMITView on GitHub

Create a runnable WebUI example with app structure, theme wiring, Playwright tests, demo metadata, and demo-shell registration.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 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.

  • 6

    Very specific

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

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

    Create the app folder with src/, data/state.json when SSR state is needed, package.json, tsconfig.json, and a concise demo.toml.

    line 8
  2. Very specific:

    Use the shared theme for example UI: add @microsoft/webui-examples-theme, pass --theme=@microsoft/webui-examples-theme, and inject …

    line 9
  3. Very specific:

    Keep package.json scripts consistent: build, start:client, start:server, start, test, and test:update-snapshots when Playwright applies.

    line 10
  4. Very specific:

    Add Playwright coverage in tests/ and a playwright.config.ts using the app's fixed dev port.

    line 11
  5. Very specific:

    Add demo.toml, copy the app into examples/demo/Dockerfile, and list it in examples/README.md.

    line 13
  6. Very specific:

    Run the focused app test, then cargo xtask check.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Checklist

  1. Create the app folder with src/, data/state.json when SSR state is needed, package.json, tsconfig.json, and a concise demo.toml.
  2. Use the shared theme for example UI: add @microsoft/webui-examples-theme, pass --theme=@microsoft/webui-examples-theme, and inject /*{{{tokens.light}}}*/ plus /*{{{tokens.dark}}}*/ in the entry template.
  3. Keep package.json scripts consistent: build, start:client, start:server, start, test, and test:update-snapshots when Playwright applies.
  4. Add Playwright coverage in tests/ and a playwright.config.ts using the app's fixed dev port. Prefer behavior tests over screenshots unless the UI is the point.
  5. Register the app in xtask/src/e2e.rs when it has Playwright tests. Use pre_script: Some("build") for custom build pipelines that the generic esbuild step cannot reproduce.
  6. Add demo.toml, copy the app into examples/demo/Dockerfile, and list it in examples/README.md.
  7. Run the focused app test, then cargo xtask check.

Download now (ZIP)

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. TypeCellOS/BlockNote★ 10ksame name
    2. skeletonlabs/skeleton★ 6.1ksame name
    3. liveblocks/liveblocks★ 4.8ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

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.

Check your setup, free