{
  "skills": [
    {
      "name": "no-ui-slop",
      "description": "Build UI that fits the product instead of generic AI defaults. Use whenever building, designing, redesigning, restyling, polishing or reviewing screens, pages, components, flows or design systems, including requests like \"make this UI better\", \"improve the UX\" or \"make it look less generic\": work from the existing design system, design every state, check the rendered result, and look up real app and website references with the optional UXKIN MCP tools when a decision needs evidence.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "uxkin-research",
      "description": "Research how real products handle a screen, flow or visual style before designing it. Use when the person asks how other apps do something, wants UI inspiration or comparable apps, needs examples of a flow (onboarding, sign-up, checkout, paywall, cancellation, account deletion, empty states) or a design system to start from: search the UXKIN library of real iOS screens, user journeys and website design systems, compare several and report what they share.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "build-ui",
      "description": "A step-by-step workflow for UI work that ends with a checked, working result. Use when asked to build a new screen, page, feature or app UI, a dashboard or admin view, or to polish, simplify or review an existing interface: read the project first, follow the plan for that kind of job, then render the result at phone and desktop sizes, fix what is wrong and check again. Works on its own; real app and website references from UXKIN are optional.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "ios-screens",
      "description": "Build iPhone app screens that feel native instead of like a website in an app. Use when designing or building iOS UI in SwiftUI, UIKit, React Native, Expo or Flutter: navigation and tab bars, lists, forms, sheets, onboarding, settings, paywalls, permissions and empty states. Follows Apple conventions (safe areas, Dynamic Type, dark mode, 44pt targets) and checks the result on small and large iPhones. Real iOS app screens from UXKIN are optional.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "design-md",
      "description": "Write or update a DESIGN.md for a project: the colors, type scale, spacing, corners, shadows and components it really uses, with rules an AI agent can follow so every new screen matches. Use when asked to document a design system, create a DESIGN.md or style guide, or stop an agent from inventing new styles; also to start a new project from a real website design system with UXKIN (optional).",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "ui-from-screenshot",
      "description": "Turn a screenshot, mockup or design image into working UI that matches it closely, built with the components and styles the project already has. Use when the person shares an image and asks to build it, recreate it, match it or \"make it look like this\". Measures the image first, builds, then puts the result next to the original and fixes the differences. Works on its own; real app and website references from UXKIN are optional.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "ui-states",
      "description": "Design and build the states AI-built UI usually forgets: first use and empty, loading, error with a way to recover, offline, no results, long or missing text, many items, permissions denied and success. Use when building or reviewing any screen that loads, lists, searches, submits or saves data, or when asked to make UI production-ready, handle edge cases or \"finish\" a screen. Real examples from UXKIN are optional.",
      "files": [
        "SKILL.md"
      ]
    }
  ]
}