GitHub Copilot skills for design work

Install PopNow skills in GitHub Copilot. Download a skill, unzip it into the skills folder, and call it by name in your next chat.

  1. 1Copy the install prompt

    Paste it into GitHub Copilot. It downloads the skill with your API key and unzips it into the right folder.

  2. 2Ask for the result

    Call the skill and say what you need in plain words: the topic, the audience, the length.

  3. 3Review and refine

    Open the file it made, ask for changes in the chat, and ship when it looks right.

All skills

  • Brand Kit & DESIGN.md GeneratorImage

    A brand kit from a short brief: checked palette, open fonts, SVG logo, mockups and a DESIGN.md agents follow.

  • Design System ShowcaseWeb

    Explore editable color tokens, measure contrast and export a consistent CSS and JSON token set.

  • App and UI Icon GeneratorImage

    One app icon and 10-30 matching UI icons, exported for iOS, Android adaptive, PWA and favicons.

  • Developer Journal SiteWeb

    Turn structured posts into a searchable technical journal with readable code and a portable RSS feed.

  • Developer Portfolio WebsiteWeb

    A dark personal site for engineers with case studies, writing, talks, a résumé and a contact form.

  • Annotated Screen TutorialVideo

    A sourced screen walkthrough with normalized focus regions and redaction checks.

Make repository design conventions usable in GitHub Copilot

Treat a creative workflow as part of a handoff

For a GitHub Copilot project, a skill can make the intended design output explicit alongside the implementation work. A useful starting point is a small brand foundation that contributors can inspect. Brand Kit & DESIGN.md Generator produces written guidance and token files; Design System Showcase lets a reviewer examine tokens, contrast and component specimens. They solve adjacent problems: the brand kit describes identity and usage, while the showcase makes a token system easier to test visually. Use approved existing assets when the project already has an established identity.

Keep project and personal scope distinct

GitHub Copilot's project location in the PopNow table is .github/skills, while its personal location is ~/.copilot/skills. Keep each downloaded skill in a separate folder and retain its SKILL.md plus bundled resources. The listed invocation is slash-prefixed, such as /popnow-brand-kit-design-md. Cursor also uses a slash form, but its repository location is .cursor/skills. A shared command shape does not make the folder names equivalent. When teammates cannot reproduce a workflow, compare the installed package and selected scope before assuming the source code is responsible.

Review consistency across the deliverables

One possible Copilot assignment is to prepare a visual foundation, build a showcase from the agreed tokens, and create matching application icons. App and UI Icon Generator is suited to that final asset task, with outputs for application and web contexts described on its detail page. Give it a real list of interface actions rather than asking for a random collection of symbols. Review each artifact against the same color and typography decisions. Keep credentials outside shared instructions, check optional generation separately, and record which files a teammate should inspect. A concise handoff explaining the approved decisions is more useful than a large folder of unrelated visual experiments.

Three ways to install

Install guides by agent

Same skills everywhere; only the folder changes.

Frequently asked questions

Why does the Copilot project path start with .github?

That is the repository skills directory recorded in PopNow's agent data: .github/skills. It differs from the personal ~/.copilot/skills location and from other assistants' project folders. Choose the listed scope and verify the extracted skill structure before diagnosing a discovery problem.

What should a teammate review in a brand kit?

Ask them to inspect the written DESIGN.md, the token exports and the visual brand board together. Confirm that the logo assets and usage guidance agree. Existing brand decisions should be supplied as constraints so a proposed identity does not accidentally replace an already approved one.

How does a showcase differ from an icon generator?

Design System Showcase focuses on tokens, contrast and live component specimens. App and UI Icon Generator focuses on application identity and matching interface symbols. They can support the same product, but reviewing color accessibility does not replace checking whether an icon communicates its intended action.

Can the same package be used with Cursor?

Both agents are listed as skill hosts, but their installation directories differ. Follow Cursor's own card when placing the package there. Retain the complete resources, use the invocation shown for that host, and test a small brief before relying on the workflow across a team.

Start building in minutes

One key for every model, a USD balance you top up when you need to, and an exact price before every run.