agentleFS
MiguelSavignanoMiguelSavignano/claude-code-system/skills/app-design/SKILL.md

app-design

Skill6 starsChanged 25 days agoNo licenceView on GitHub

How screen designs for your team's apps are made with claude.ai artifacts — one design system per product (even within the same company) and one design canvas per repo (an admin/backoffice living in the backend repo uses its product's design system on its own canvas), the canvas organized into pages by domain ("Base design" first), each screen in a "today | proposal" row with a note, and the registry of where each design system and canvas lives and which domains it has. Use before designing or redesigning a screen, when creating an app's design system, when adding a domain, or when someone asks "where is the design for X?". Invoke as /app-design [app] [screen].

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dax-authoring, query-design and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    dax-authoring

    Write and test DAX queries against Power BI semantic models. Covers DAX syntax rules, query patterns, time intelligence, and an iterative test workflow using the Fabric CLI query command.

    Also in 10 projects that use this

  • MicrosoftSkill

    query-design

    Separates DAX data-fetching from TypeScript presentation. Guides when to use DAX vs. TypeScript vs. Vega-Lite for aggregation, total rows, FORMAT(), SELECTCOLUMNS, BLANK handling, filtering, multi-grain queries, cross-filtering and cross-highlight subset/overlay queries, and format strings.

    Also in 10 projects that use this

  • +7 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.