app-design
Skill2 starsChanged 57 days agoMITView on GitHub
Audit an existing application or repository, identify verified defects, and prioritize improvements. Supports assessment-only review of web apps, services, libraries, scripts, and skill repositories.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/DataHub-App-for-Microsoft-Copilot-Agents-Cowork-and-Autopilotstheir own version, first seen Nov 8, 2026
- microsoft/fabric-apps-analytic-templatestheir own version, first seen Nov 3, 2026
- MiguelSavignano/claude-code-systemtheir own version, first seen Nov 1, 2026
- microsoft/ValueLens-for-Microsoft-Copilottheir own version, first seen Oct 25, 2026
- microsoft/ConsumptionCentral-for-Microsoft-Copilottheir own version, first seen Oct 25, 2026
- microsoft/frontiertour27-LTG291-turn-your-data-into-production-apps-with-rayfintheir own version, first seen Oct 17, 2026
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.
MicrosoftSkilldax-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
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- microsoft/rayfin★ 646same name
- microsoft/awesome-rayfin★ 108same name
- microsoft/ConsumptionCentral-for-Microsoft-Copilot★ 33same name
- microsoft/fabric-apps-analytic-templates★ 29same name
- microsoft/ValueLens-for-Microsoft-Copilot★ 23same name
- microsoft/AnalyticsHub-Dashboard★ 10same name
- microsoft/DataHub-App-for-Microsoft-Copilot-Agents-Cowork-and-Autopilots★ 10same name
- MiguelSavignano/claude-code-system★ 6same name
- microsoft/aitour27-LTG291-turn-your-data-into-production-apps-with-rayfin★ 2same name
- microsoft/frontiertour27-LTG291-turn-your-data-into-production-apps-with-rayfin★ 2same name
3 more not listed
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditSkill
- cloudflare-temporary-deploySkill
- code-reviewSkill
- codex-delegateSkill
- commit-documentorSkill
- constructorSkill
- datasecurerSkill
- dependabot-validatorSkill
- dogfoodSkill
- flask-testsSkill
- ideatorSkill
- lan-viewerSkill
- memorySkill
- ollama-delegateSkill
- pr-grill-meSkill
- rest-graphql-debugSkill
- system-oneSkill
- web-pentestSkill
- workflow-rulesSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
3
Distinctive
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
- Distinctive: line 13
Read repository instructions and supplied context.
- Very specific: line 16
Use rg and focused reads rather than an exhaustive file dump.
- Distinctive: line 19
Verify suspected defects with code paths, existing tests, or focused repros.
- Distinctive: line 22
When runtime QA is authorized and relevant, consult the test battery.
- Very specific: line 30
Default artifact: app-design-output/recommendations.md, including the app model, findings, tested/untested areas, and next steps.
“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.
Files
Existing application assessment
Understand the repository and produce evidence-backed findings appropriate to
the requested scope. Keep the public name app-design for compatibility.
For new-project scope use ideator; for architecture/specifications/milestones use
constructor. Neither is a prerequisite for assessing existing code.
- Read repository instructions and supplied context. Determine assessment-only, runtime QA, or authorized implementation scope. Reuse the user's stated intent.
- Map entry points, dependencies, data/state, build/test commands, and ownership.
Use
rgand focused reads rather than an exhaustive file dump. - State the inferred purpose and material uncertainties. Ask only when an answer changes findings or safety; continue independent static checks meanwhile.
- Verify suspected defects with code paths, existing tests, or focused repros. For assessment-only requests, do not automatically install dependencies, launch servers, run browsers, or delegate work. Label untested claims.
- When runtime QA is authorized and relevant, consult the test battery. Web UI exploration may use separately installed dogfood. A missing browser does not block static or CLI assessment; report the coverage limit.
- Rank findings by impact, evidence, effort, and dependencies. Distinguish bugs, intended behavior, and suggested improvements. Implement only within scope already authorized by the user; otherwise present the proposed work.
Default artifact: app-design-output/recommendations.md, including the app model,
findings, tested/untested areas, and next steps. Existing app-model.md and
runtime reports remain valid inputs; additional documents are optional.
Question bank: consult only for unresolved intent.
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
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.