Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Export: add a shadcn/ui theme format

Open
  • Is something wrong?
#175 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
74/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
css, typescript
Domain
design

Research direction

Start with the "Adding a new export format" section of CONTRIBUTING.md, then read the bootstrap and chakra entries in lib/tokens/formats.ts and their tests in lib/tokens/formats.test.ts. Use roleColor() in lib/tokens/native.ts for the light and dark values, and emit the shadcn variables under :root and .dark in OKLCH. Done when the format appears in the Export Engine and the all-formats ZIP, and a unit test covers both selectors.

Written by the indexing model from the issue text.

Description

area: export difficulty: easy enhancement good first issue

Summary

Add a shadcn/ui export (globals.css snippet): the CSS variables shadcn components read (--background, --foreground, --primary, --primary-foreground, --muted, --accent, --border, --ring, --radius and so on) for :root and .dark, from the brand roles.

Where to look

  • CONTRIBUTING.md, "Adding a new export format"
  • lib/tokens/formats.ts: the bootstrap and chakra formats are recent examples
  • lib/tokens/formats.test.ts
  • lib/tokens/native.ts: roleColor() for light and dark

Behaviour

  • Use OKLCH values, like current shadcn themes do.

Acceptance criteria

  • The format shows up in the Export Engine and in the all-formats ZIP.
  • Pasted into a fresh shadcn project, buttons, inputs and cards pick up the brand (a screenshot in the PR).
  • A unit test covers both :root and .dark.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build. See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
7h 36m
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.