open-index/open-npm huggingface dataset:
npm package: @gobolt/genesis-legacy
Description: genesis design system
Author: gobolt
Latest version: 0.3.5

# GENESIS Legacy Design System

![Rating](https://img.shields.io/badge/rating-5%2F5-brightgreen) ![License](https://img.shields.io/badge/license-MIT-green)

## Overview

GENESIS Legacy is a downgraded version of the [GENESIS Design System](https://github.com/SecondCloset/genesis) that maintains compatibility with React 17 and Ant Design 4. This version is specifically designed for applications that cannot upgrade to React 18 or Ant Design 5 due to compatibility constraints.

## Dependencies

GENESIS Legacy is built with:
- [Antd](https://ant.design/) v4.24.0
- [Styled Components](https://styled-components.com/) v5.3.0
- [Typescript](https://www.typescriptlang.org/) v4.9.5
- [React](https://react.dev/) v17

## Installation

```bash
npm install @gobolt/genesis-legacy
```

## Usage

The `GenesisProvider` must be included within your application as it supplies the Genesis Theme:

```jsx
import { Button, GenesisProvider } from '@gobolt/genesis-legacy';

const Demo = () => {
    const onClick = (value) => {
        console.log("Genesis button clicked with value: ", value);
    }

    return (
        <GenesisProvider>
            <Button onClick={onClick}>Ship</Button>
        </GenesisProvider>
    )
};
```

## Migration Path to React 18 and Ant Design 5

Once your app is ready to migrate, the only change will be to replace this [@gobolt/genesis-legacy](https://www.npmjs.com/package/@gobolt/genesis) package with the latest package from [@gobolt/genesis](https://www.npmjs.com/package/@gobolt/genesis)

If you only upgrade to React and not also upgrade Ant, then it is best to stick with this legacy version since it will still be compatible.

## Library Development

```bash
# Install dependencies
npm install --force

# Start development server
npm run storybook
```

To scaffold a new component:
```bash
npm run generate RadioGroup
```

## Testing

```bash
npm test
```

Tests are automatically run on push to Github using [husky](https://typicode.github.io/husky/).

## Publishing

This project uses [rollup](https://rollupjs.org/) for building and [changesets](https://github.com/changesets/changesets) for version management:

```bash
npx changeset
npx changeset version
npm publish
```

## Storybook

The component documentation is available in our Storybook:

```bash
# Start Storybook locally
npm start

# Build Storybook
npm run build-storybook
```

For Aiur!
npm package: @gobolt/genesis-tokens
Description: a TypeScript library for Genesis design tokens
Author: gobolt
Latest version: 0.0.10

<p align="center">
  <img src="https://storage.googleapis.com/labs-media/images/genesis-conveyor-mark.svg" width="150" alt="Genesis logo">
</p>

# Genesis Tokens

A platform-agnostic TypeScript library for Genesis design tokens.

Try this [token tool](https://genesis-tokens-jxjvzfwp2q-nn.a.run.app/) which makes it easy to find and copy them into your projects.

Genesis tokens are the foundation of our component libraries:

- [Genesis](https://www.npmjs.com/package/@gobolt/genesis) for React 18 & Ant 5
- [Genesis Legacy](https://www.npmjs.com/package/@gobolt/genesis-legacy) for React 17 and Ant 4

They provide a consistent structure for our [GoBolt](https://www.gobolt.com/) applications 

## Installation

```bash
npm install @gobolt/genesis-tokens
```

## Usage

```typescript
import { lightTheme, darkTheme } from '@gobolt/genesis-tokens';
```

You can think of the raw tokens as a Typescript tree that can compliment any library. 

### Styled components

See the [styled-components guide](./docs/styled-components-guide.md) for a full example of using Genesis tokens with styled-components.

### Tailwind

See the [Tailwind CSS guide](./docs/tailwind-guide.md) for a full example of using Genesis tokens with Tailwind.

## Theme Structure

The package exports the following:

- Theme objects (`lightTheme`, `darkTheme`)
- Individual token groups (`color`, `typography`, `sizing`, etc.) within each theme object
- Theme types and interfaces for TypeScript support

## Development

1. Clone the repository
2. Install dependencies: `npm install`
3. Develop `npm run dev`
6. Publish `npm publish`

## Prompt Guide

When using AI UI apps like lovable, we can prompt the LLM to use this genesis-tokens library

see [prompt guide](./docs/prompt-guide.md)

## Deploy the Token Tool to GCP

```
just ship
```
npm package: @gobrand/calendar-core
Description: Lightweight utility library for building calendars using the Temporal API
Latest version: 0.0.23

# Calendar Core

[![npm version](https://img.shields.io/npm/v/@gobrand/calendar-core.svg)](https://www.npmjs.com/package/@gobrand/calendar-core)
[![CI](https://github.com/go-brand/calendar/actions/workflows/ci.yml/badge.svg)](https://github.com/go-brand/calendar/actions/workflows/ci.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

**Framework-agnostic calendar utilities built with the Temporal API.** Simple, composable functions for building month, week, and day views.

👉 **[Documentation](https://eng.gobrand.app/calendar)**

- **Built on Temporal API** - No Date objects, no moment.js, no date-fns
- **Timezone-aware** - Native DST handling with IANA timezones
- **Type-safe** - Full TypeScript with proper Temporal types
- **Framework-agnostic** - Use with React, Vue, Svelte, or vanilla JS
- **Data-agnostic** - Works with any data type through accessor pattern

```typescript
import { buildMonth, createCalendarAccessor, getWeekdays } from '@gobrand/calendar-core';

const accessor = createCalendarAccessor<Event>({
  getDate: (e) => e.date,
});

const month = buildMonth(2025, 1, { weekStartsOn: 1, data: events, accessor });

month.weeks.flat().forEach(day => {
  console.log(day.date.toString(), day.items.length);
});
```

## Install

```bash
pnpm add @gobrand/calendar-core
```

## Docs

**[eng.gobrand.app/calendar](https://eng.gobrand.app/calendar)** — Full API reference, examples, and guides.

## License

MIT © [Ruben Costa](https://x.com/PonziChad) / [Go Brand](https://gobrand.app)
npm package: @gobrand/react-calendar
Description: React hooks and components for building calendars using the Temporal API
Latest version: 0.0.23

# React Calendar

[![npm version](https://img.shields.io/npm/v/@gobrand/react-calendar.svg)](https://www.npmjs.com/package/@gobrand/react-calendar)
[![CI](https://github.com/go-brand/calendar/actions/workflows/ci.yml/badge.svg)](https://github.com/go-brand/calendar/actions/workflows/ci.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

**React hooks for building calendars with the Temporal API.** Type-safe views, timezone-aware, optimized state management.

👉 **[Documentation](https://eng.gobrand.app/calendar)**

- **Built on Temporal API** - No Date objects, no moment.js, no date-fns
- **Timezone-aware** - Native DST handling with IANA timezones
- **Type-safe** - Conditional methods based on configured views
- **Multi-view** - Month, week, and day views with time slots
- **TanStack Store** - Optimized reactive state management

```tsx
import { useCreateCalendar, useView, CalendarProvider } from '@gobrand/react-calendar';

const accessor = { getDate: (e: Event) => e.date };

function App() {
  const calendar = useCreateCalendar<Event>({
    views: { month: { accessor } },
  });

  return (
    <CalendarProvider calendar={calendar}>
      <Calendar />
    </CalendarProvider>
  );
}

function Calendar() {
  const view = useView({ data: events });
  // view.data.weeks.flat().map(day => ...)
}
```

## Install

```bash
pnpm add @gobrand/react-calendar
```

**Peer dependencies:** React 18+ or 19+

## Docs

**[eng.gobrand.app/calendar](https://eng.gobrand.app/calendar)** — Full API reference, examples, and guides.

## License

MIT © [Ruben Costa](https://x.com/PonziChad) / [Go Brand](https://gobrand.app)
npm package: @gobrand/tiempo
Description: Lightweight utility functions for converting between UTC and timezone-aware datetimes using the Temporal API
Latest version: 2.8.1

# tiempo

[![npm version](https://img.shields.io/npm/v/@gobrand/tiempo.svg)](https://www.npmjs.com/package/@gobrand/tiempo)
[![CI](https://github.com/go-brand/tiempo/actions/workflows/ci.yml/badge.svg)](https://github.com/go-brand/tiempo/actions/workflows/ci.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

**Timezone conversions that don't suck.** Built on the [Temporal API](https://tc39.es/proposal-temporal/docs/).

👉 **[Documentation](https://eng.gobrand.app/tiempo)**

![tiempo banner](./tiempo_banner.png)


- **Zero timezone bugs** - Real IANA timezone support, not UTC offset hacks
- **DST-aware math** - `addDays(1)` means tomorrow, even across clock changes
- **Nanosecond precision** - When milliseconds aren't enough
- **Type-safe** - Full TypeScript, catches datetime errors at compile time
- **Familiar API** - If you've used date-fns, you already know this

```typescript
import { toZonedTime, addDays, format, toIso } from '@gobrand/tiempo';

// Backend sends UTC
const utc = "2025-03-09T07:00:00Z";

// Convert to user's timezone, manipulate, format
const userTime = toZonedTime(utc, "America/New_York");
const tomorrow = addDays(userTime, 1);  // DST transition handled correctly
const display = format(tomorrow, "EEEE 'at' h:mm a");  // "Monday at 2:00 AM"

// Send back to backend as ISO 8601 string
const payload = toIso(tomorrow);  // "2025-03-10T06:00:00Z"
```

## Install

```bash
npm install @gobrand/tiempo
```

## Docs

**[eng.gobrand.app/tiempo](https://eng.gobrand.app/tiempo)** — Full API reference, examples, and guides.

## License

MIT © [Ruben Costa](https://x.com/PonziChad) / [Go Brand](https://gobrand.app)