open-index/open-npm huggingface dataset:
npm package: @furudean/svelte-persistent-store
Description: Svelte store that saves and loads data from localStorage or sessionStorage
Author: Merilynn Bandy
Latest version: 0.9.0

<img src="iky.png"
  height="76"
  width="62"
  align="right"
  alt="A girl" />

# [svelte-persistent-store](https://www.npmjs.com/package/@furudean/svelte-persistent-store)

This is a
[writable svelte store](https://svelte.dev/docs#run-time-svelte-store-writable)
that saves and loads data from `Window.localStorage` or `Window.sessionStorage`.
Works with Svelte Kit out of the box.

The store listens to events from the `Storage` interface and will sync its
internal state upon changes. This makes debugging using the developer console
easy, and it will update across sessions as well.

## Install

```bash
npm install @furudean/svelte-persistent-store
```

## Use

> **Note**: By default only
> [JSON serializable values](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#description)
> are handled, but [custom serialization and deserialization functions can be
> provided](#custom-serialization-functions).

```js
import { persistent } from "@furudean/svelte-persistent-store"

const preferences = persistent({
	start_value: {
		foo: "bar"
	},
	key: "preferences", // key to save as in Storage
	storage_type: "localStorage" // Storage object to use
})
```

## Custom serialization functions

Since the `Storage` interface only supports strings, data needs to be converted
to strings before saving. By default `JSON.stringify` and `JSON.parse` is used.

You can pass custom serializer and deserializer functions if you require
specific behavior when loading or saving data from `Storage`. For example, you
can handle `Date`s like this:

```js
const persistent_date = persistent({
	start_value: new Date(),
	key: "my-persistent-date",
	storage_type: "localStorage",
	serialize: (date) => date.toISOString(), // transform before saving
	deserialize: (str) => new Date(str) // transform after loading
})
```
npm package: @furugen/testactics-mcp-server
Description: MCP Server for Testactics AI Agent Orchestration - File-based communication with SQLite support
Author: Yuu Furugen
Latest version: 2.1.0

# Testactics MCP Server

Testactics AIエージェントオーケストレーション用のMCP（Model Context Protocol）サーバー実装です。

## 🚀 インストール

### npmからインストール（推奨）

```bash
npm install -g @yfurugen/testactics-mcp-server
```

### npxで直接実行

```bash
npx @yfurugen/testactics-mcp-server --help
```

## 📋 Claude Desktopでの設定

`~/.config/claude/claude_desktop_config.json` に以下を追加:

```json
{
  "mcpServers": {
    "testactics": {
      "command": "npx",
      "args": [
        "@yfurugen/testactics-mcp-server",
        "--db", "/path/to/your/testactics.db",
        "--project-root", "/path/to/your/project"
      ]
    }
  }
}
```

または環境変数を使用:

```json
{
  "mcpServers": {
    "testactics": {
      "command": "npx",
      "args": ["@yfurugen/testactics-mcp-server"],
      "env": {
        "MCP_DATABASE_PATH": "/path/to/your/testactics.db",
        "MCP_PROJECT_ROOT": "/path/to/your/project"
      }
    }
  }
}
```

## 🔧 コマンドライン引数

```
Usage: testactics-mcp-server [options]

Options:
  --db, --database <path>    SQLiteデータベースファイルのパス
  --project-root <path>      プロジェクトルートディレクトリ
  --project-name <name>      プロジェクト名
  --task-id <id>             タスクID
  --agents-dir <path>        エージェントディレクトリ
  --executing-agent <id>     実行エージェントID（デフォルト: user）
  -h, --help                 ヘルプを表示
```

## 🔗 環境変数

| 環境変数 | CLI引数 | 説明 |
|---------|--------|------|
| `MCP_DATABASE_PATH` | `--db` | SQLiteデータベースファイルのパス |
| `MCP_PROJECT_ROOT` | `--project-root` | プロジェクトルートディレクトリ |
| `MCP_PROJECT_NAME` | `--project-name` | プロジェクト名 |
| `MCP_TASK_ID` | `--task-id` | タスクID |
| `MCP_AGENTS_DIR` | `--agents-dir` | エージェントディレクトリ |
| `MCP_EXECUTING_AGENT` | `--executing-agent` | 実行エージェントID |

**優先順位**: CLI引数 > 環境変数 > 自動検出

## 🔧 利用可能なツール

### エージェント操作

#### `instruct_agents`
1つ以上のエージェントに作業指示を出します。

```typescript
{
  instructions: [
    {
      agent_id: string,      // エージェントID
      instruction: string,   // 指示内容
      priority?: string      // 優先度（high/normal/low）
    }
  ]
}
```

#### `get_agent_status`
エージェントの現在の状態を取得します。

```typescript
{
  agent_id: string  // エージェントID
}
```

### TODO管理

#### `create_todo`
新しいTODOを作成します（WBS/ガントチャート対応）。

#### `update_todo`
既存のTODOを更新します。

#### `get_todos`
TODO一覧を取得します。

#### `complete_todo`
TODOを完了としてマークします。

### タスク管理

#### `create_task`
新しいタスクを作成します（親子関係・依存関係対応）。

#### `update_task`
既存のタスクを更新します。

#### `get_tasks`
タスク一覧を取得します。

#### `complete_task`
タスクを完了としてマークします。

#### `delete_task`
タスクを削除します。

#### `check_task_dependencies`
タスクの依存関係をチェックし、開始可能か確認します。

## 📁 ローカル開発

### セットアップ

```bash
cd mcp-server
npm install
npm run build
```

### ウォッチモード

```bash
npm run dev
```

### ローカルテスト

```bash
node dist/index.js --help
```

## 📚 関連資料

- [MCP公式ドキュメント](https://modelcontextprotocol.io/)
- [MCP SDK for TypeScript](https://github.com/modelcontextprotocol/typescript-sdk)
- [Testactics](https://github.com/yfurugen/testactics)

---

**バージョン**: 2.1.0
**ライセンス**: MIT
**作者**: Yuu Furugen
npm package: @furugomu/aikatsu-scraper
Description: ```js async () => {   const fetch = require("node-fetch");   const { scrapeFriends } = require("@furugomu/aikatsu-scraper");   const html = (await fetch(     "http://www.aikatsu.com/friends/cardlist/detail.php?id=137233"   )).text();   console.log(scrapeF
Author: furugomu@gmail.com
Latest version: 1.0.0

# aikatsu scraper

```js
async () => {
  const fetch = require("node-fetch");
  const { scrapeFriends } = require("@furugomu/aikatsu-scraper");
  const html = (await fetch(
    "http://www.aikatsu.com/friends/cardlist/detail.php?id=137233"
  )).text();
  console.log(scrapeFriends(html));
};
```
npm package: @furugomu/eslint-plugin
Description: my eslint plugin
Author: furugomu@gmail.com
Latest version: 0.9.1

# @furugomu/eslint-plugin

## つかいかた

.eslintrc.js

```js
module.exports = {
  plugins: ['@furugomu/eslint-plugin'],
  extends: ['plugin:@furugomu/recommended']
}
```
npm package: @furvester/upstream-sync
Description: Sync from upstream via RabbitMQ
Author: Ben Scholzen 'DASPRiD'
Latest version: 2.1.6

# Upstream Sync

[![Release](https://github.com/Furvester/upstream-sync/actions/workflows/release.yml/badge.svg)](https://github.com/Furvester/upstream-sync/actions/workflows/release.yml)

Sync from upstream via RabbitMQ.
npm package: @fury90723/bridge-util
Description: JavaScript library to interact with Sygna Bridge Server.
Author: mt
Latest version: 1.0.1

# bridge-util

This is a Javascript library to help you build servers/servies within Sygna Bridge Ecosystem. For more detail information, please see [Sygna Bridge](https://www.sygna.io/).

## Installation

```shell
npm i @fury90723/bridge-util
```
npm package: @furyahub-app/react-components
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Author: joe
Latest version: 1.6.2

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `yarn start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `yarn eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @furyahub/react-components
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Author: joe
Latest version: 1.6.0

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `yarn start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `yarn eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @furyahubapp/react-components
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Author: joe
Latest version: 1.6.1

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `yarn start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `yarn test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `yarn build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `yarn eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @furyanetwork/root
Description: ## Generate code and docs
Latest version: 1.0.2

# Furya Orderbook SDK

## Generate code and docs

```bash
# build code:
cwtools build ../furyswap/contracts/* ../furydex-listing-contract ../co-harvest-contracts/contracts/* ../cw20-staking/contracts/* -o packages/contracts-build/data
# gen code:
cwtools gents ../furyswap/contracts/* ../furydex-listing-contract ../co-harvest-contracts/contracts/* ../cw20-staking/contracts/* -o packages/contracts-sdk/src
# gen doc:
yarn docs

# update comments:
git apply patches/contracts-sdk.patch
# edit contracts-sdk
git diff packages/contracts-sdk > patches/contracts-sdk.patch
# rollback
git checkout packages/contracts-sdk
```

## Run sample with CosmwasmSimulate

```bash
NODE_ENV=test yarn --cwd packages/market-maker start
```

# FURYDEX BACKEND

Furydex backend is a nodejs server that provides a REST API for aggreated events from a furydex contracts.

Features:

- Syncronize events from a furydex smart contract on-chain to a database
- Provide a REST API to query events from the database

## HOW TO RUN

### Local

```sh
cp .env.example .env
yarn && yarn build
cd packages/furydex-server
node dist/index.js
```

### Docker

```
docker build . -t furya/defi_furydex-backend
docker run -it --rm \
-v $(pwd)/.env:/app/.env \
-v your-db-file.db:/app/your-db-file.db \
furya/defi_furydex-backend

```

## RUN UNIT TESTS

```sh
yarn test
```