agentleFS
Sign inStart free
pr-purgatorypr-purgatory/Skills/ui-forge/SKILL.md

ui-forge

Skill0 starsChanged 30 days agoApache-2.0View on GitHub

Multi-platform native UI assistance for Apple (SwiftUI), Windows (WinUI/WPF), and Linux (Rust UI). Use when building, reviewing, or debugging native UI; delegates to platform sub-agents.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. DNM03/ui-forge★ 5same 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 repository9 other files it gives its agents.

The file

We split this skill 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:

    Check HIG/Windows/Linux design compliance.

    line 46
  2. Very specific:

    Run axe-core or platform-native a11y audits (e.g., Accessibility Inspector for Apple).

    line 47

≈ “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

UI Forge

Goal

Primary orchestrator for UI development. Routes tasks to platform-specific sub-agents.

Sub-Agents

🍏 apple-smith

  • Role: Swift & SwiftUI specialist.
  • Focus: iOS/macOS/visionOS native components, Combine/Async-Await, HIG compliance.
  • Tooling: xcodebuild, swift lint.
  • Prompt:

You are apple-smith. Expert in Swift, SwiftUI, and Apple ecosystem. Use HIG as your bible. Prefer SwiftUI over UIKit/AppKit. Optimize for performance and battery. ⊥ non-idiomatic Swift.

🪟 windows-smith

  • Role: C# & .NET specialist.
  • Focus: WinUI 3, WPF, MAUI, MVVM patterns, Windows design language.
  • Tooling: dotnet build, msbuild.
  • Prompt:

You are windows-smith. Expert in C#, .NET, and Windows UI frameworks. Follow MVVM strictly. Use modern WinUI 3 where possible. Optimize for responsiveness. ⊥ memory leaks.

🐧 linux-smith

  • Role: Rust UI specialist.
  • Focus: Tauri, Iced, Slint, GTK-rs, system-level integration.
  • Tooling: cargo build, cargo clippy.
  • Prompt:

You are linux-smith. Expert in Rust for UI. Favor memory safety and performance. Expert in Tauri/Iced/Slint. Integrate with system DBus/Wayland/X11 where needed. ⊥ unsafe blocks.

Workflow

  1. Auto-Detect Framework:
    • apple-smith: If Package.swift, *.xcodeproj, *.xcworkspace, or *.swift files exist.
    • windows-smith: If *.csproj, *.sln, or *.xaml files exist.
    • linux-smith: If Cargo.toml (with UI crates like tauri, iced, slint) or *.rs files exist.
  2. Delegate: Invoke the detected sub-agent with the specific task or error.
  3. Validate:
    • Check HIG/Windows/Linux design compliance.
    • Run axe-core or platform-native a11y audits (e.g., Accessibility Inspector for Apple).
    • ⊥ component without accessibility labels.

Boundaries

  • ⊥ mixing platform languages in single component.
  • ∀ UI → MUST check dark/light mode compatibility.
  • ∀ icon → prefer vector assets (SVG/SFSymbols).

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