open-index/open-npm huggingface dataset:
npm package: @parentos/cli
Description: CLI interface for ParentOS - connect AI assistants to family context
Author: ParentOS Team
Latest version: 1.0.3

# @parentos/cli

Connect AI assistants (Claude, ClawdBot) to ParentOS family context.

## Installation

```bash
npm install -g @parentos/cli
```

## Quick Start

```bash
# 1. Get your token from ParentOS Settings → Integrations
# 2. Login
parentos login --token agt_your_token_here

# 3. Install skill for your AI assistant
parentos install-skill clawdbot

# 4. Test connection
parentos ping
```

## Commands

### Family Context

```bash
parentos context
```

Get current day state, event count, and family bandwidth.

### Budget Check

```bash
parentos budget check 150
```

Check if spending $150 is within budget. Returns `approved: true/false`.

### Schedule Capacity

```bash
parentos schedule check --duration 60
```

Check if there's capacity for a 60-minute activity.

### Health Summary

```bash
parentos health
```

Get health tracking status (medication count, no sensitive details).

### Log Activity

```bash
parentos log "Booked dinner reservation"
```

Log an action for the family audit trail.

## For AI Agents

Set `PARENTOS_OUTPUT=json` for machine-readable output:

```bash
export PARENTOS_OUTPUT=json
parentos context
# Returns clean JSON for parsing
```

## Environment Variables

| Variable | Description |
|----------|-------------|
| `PARENTOS_API_KEY` | Agent token (alternative to `parentos login`) |
| `PARENTOS_API_URL` | API endpoint (default: https://parentos.ai/api) |
| `PARENTOS_OUTPUT` | Output format: `json` for AI agents |

## Security

ParentOS returns **metadata only**:
- Day state (calm/busy/full)
- Event counts (not titles)
- Financial health score (not amounts)
- Medication count (not names)

No PII or sensitive details are ever exposed.

## License

MIT
npm package: @pareshshifl/grid
Description: Shifl Grid - JSON-driven Vue 3 data grid for Shifl UI.
Latest version: 0.1.0

# Shifl Grid (Vue 3)

JSON-driven data grid for Shifl UI, built with Vue 3 + TypeScript. Library-first output via Vite (library mode) with Tailwind + CSS variables for theming.

## Status

- ✅ Minimal grid (column visibility toggle, client-side sorting, global filter)
- 🚧 Everything else scaffolded/stubbed for incremental delivery (editing, virtual scroll, tours, views)

## Requirements

- Node `>=20.11.0` (matches Shifl UI constraint)
- Peer deps: `vue@^3.4.0`, `pinia@^2.2.0`

## Install

```bash
npm install @shifl/grid
# peer deps
npm install vue pinia
```

## Usage

```ts
// main.ts
import { createApp } from "vue";
import App from "./App.vue";
import { ShiflGridPlugin } from "@shifl/grid";
import "@shifl/grid/style.css";

const app = createApp(App);
app.use(ShiflGridPlugin);
app.mount("#app");
```

```vue
<script setup lang="ts">
import { ShiflGrid } from "@shifl/grid";
import type { GridConfig } from "@shifl/grid";

const config: GridConfig = {
  name: "My Preferred Shipments",
  columns: [
    { key: "shifl_ref", label: "Shifl Ref #", sortable: true, frozen: true },
    { key: "company_name", label: "Customer", sortable: true },
  ],
  search: ["shifl_ref", "company_name"],
  sort: { key: "shifl_ref", order: "asc" },
  rows: [
    { shifl_ref: "SF-1001", company_name: "GMA Inc" },
    { shifl_ref: "SF-1002", company_name: "Walads Autowash" },
  ],
};
</script>

<template>
  <ShiflGrid :config="config" />
</template>
```

## Scripts

- `npm run dev` — Vite dev server
- `npm run build` — Library build + d.ts via `vite-plugin-dts`
- `npm run lint` — ESLint (Vue + TS) flat config
- `npm run test` — Vitest (jsdom)
- `npm run storybook` — Storybook dev
- `npm run storybook:build` — Storybook static build

## Project structure (high level)

- `src/components/grid` — `ShiflGrid.vue` (minimal implementation)
- `src/composables` — Core behaviors (sort/filter/columns implemented, others stubbed/TODO)
- `src/types` — Grid + theme contracts
- `src/theme` — CSS tokens
- `src/styles` — Tailwind entry + component styles
- `src/utils` — Helpers (config normalization)
- `src/plugins` — Vue install plugin
- `stories/` — Storybook stories
- `.storybook/` — Storybook configuration

## Notes

- Config normalization supports both `frozen` and legacy `fixed` flags.
- Virtual scroll, editing, tours, saved/recommended views, telemetry are intentionally stubbed for later milestones.
npm package: @paretio/tsconfig
Description: Shareable TypeScript configurations for Paretio projects.
Latest version: 0.4.2

# @paretio/tsconfig

Shareable TypeScript configurations for Paretio projects.

## Create New Beta Release

Create a beta release on a feature branch for testing before merging to main. Beta releases are published to npm with the `@beta` tag.

### Commands

```sh
npm run release:beta
```

### Example

```sh
# On feature branch
git checkout -b feature/add-jsx-support
git add .
git commit -m "feat: add JSX support"

# Create beta release (automatically runs tests, tags, and pushes)
npm run release:beta

# Test the beta version
cd ../other-project
npm install @paretio/tsconfig@beta

# If changes needed, create another beta
cd ../tsconfig
git add .
git commit -m "fix: address feedback"
npm run release:beta  # Creates 0.5.0-beta.1
```

## Create New Stable Release

Create a stable release on the main branch after a PR has been merged. Stable releases are published to npm with the `@latest` tag.

### Commands

```sh
# Patch release (0.5.0 → 0.5.1)
npm run release:patch

# Minor release (0.5.0 → 0.6.0)
npm run release:minor

# Major release (0.5.0 → 1.0.0)
npm run release:major

# Promote beta to stable (0.5.0-beta.1 → 0.5.0)
npm version 0.5.0
```

### Example

```sh
# After PR merged to main
git checkout main
git pull

# Create patch release
npm run release:patch

# Or promote beta to stable
npm version 0.5.0
```

## What Happens Automatically

When you run `npm version` or `npm run release:*`, the following happens automatically:

| Step | Where          | What Happens                                                          |
|------|----------------|-----------------------------------------------------------------------|
| 1    | Local          | `npm run release:beta` runs tests, updates package.json, creates tag  |
| 2    | Local          | `postversion` hook pushes commit + tag to GitHub                      |
| 3    | GitHub         | Detects tag push matching workflow pattern                            |
| 4    | GitHub Actions | Checks out code, verifies version, runs tests                         |
| 5    | GitHub Actions | Determines correct npm dist-tag (beta/latest)                         |
| 6    | GitHub Actions | Publishes to npm with provenance                                      |
| 7    | GitHub Actions | Creates GitHub Release                                                |
| 8    | NPM            | Package available for installation                                    |

**Never manually create git tags.** Always use `npm version` commands.
npm package: @pareto-engineering/generator-front
Description: Yeoman is a client-side scaffolding tool for web applications. We use this to quickly scaffold a component, module, page and story.
Author: advl
Latest version: 2.0.0

# Generator-front (`Yeoman`) <code><img height="30" src="https://avatars.githubusercontent.com/u/1714870?s=200&v=4"></code>

Yeoman is a client-side scaffolding tool for web applications. We use this to quickly scaffold a component, module, page and story.

## Project Installation and Setup

```sh
# If you have configured the SSH protocol, use
$ git clone git@github.com:HelloPareto/generator-front.git

cd generator-front

npm install
```

## Usage
* Install the `@pareto-engineering/generator-front` package globally
    ```sh
    $ npm i -g yo @pareto-engineering/generator-front # you might need an older version of yo
    ```


* Navigate to the folder you want to scaffold either a component, story, module, or page
    ```sh
    // For a component
    $ yo @pareto-engineering/front component [name] # this creates a folder with [name] as it's name with three files in it --> [name].jsx, index.js, styles.scss

    // For a story
    $ yo @pareto-engineering/front story [name] # this creates a [name].stories.jsx file --> A story captures the rendered state of a UI component and describes all the states a component can support

    // For a page
    $ yo @pareto-engineering/front page [name] # this creates a [name].jsx file

    // For a module
    $ yo @pareto-engineering/front module [name] # this creates a folder with [name] as it's name. The folder has urls.js and routes.js files, component and pages folders both having an index.js file
    ```