### Add Command Example with CAC

Source: https://github.com/blackriis/test/blob/main/node_modules/cac/README.md

Shows how to add an example usage for a command, which will be displayed in the help message to guide users.

```javascript
command.example('build --watch src/**/*.js')
```

--------------------------------

### Given-When-Then Documentation Example

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Illustrates the use of Given-When-Then structure for documenting test cases. This format clarifies the test setup (Given), action (When), and assertion (Then), aiding in clear communication of test objectives.

```text
**Given**: The initial context the test sets up

- What state/data the test prepares
- User context being simulated
- System preconditions

**When**: The action the test performs

- What the test executes
- API calls or user actions tested
- Events triggered

**Then**: What the test asserts

- Expected outcomes verified
- State changes checked
- Values validated

**Note**: This is for documentation only. Actual test code follows your project's standards (e.g., describe/it blocks, no BDD syntax).
```

--------------------------------

### Setup Test Payroll Data

Source: https://github.com/blackriis/test/blob/main/PAYROLL_SETUP_GUIDE.md

A Node.js script to populate the database with test employee and time entry data. This is useful for local development and testing payroll calculation logic.

```javascript
node setup-test-payroll-data.js
```

--------------------------------

### GET/POST /api/admin/payroll-cycles

Source: https://github.com/blackriis/test/blob/main/PAYROLL_SETUP_GUIDE.md

Retrieves or creates payroll cycles. This endpoint is working with proper error handling.

```APIDOC
## GET /api/admin/payroll-cycles

### Description
Retrieves a list of payroll cycles.

### Method
GET

### Endpoint
/api/admin/payroll-cycles

### Parameters
#### Query Parameters
- **id** (string) - Optional - The ID of the payroll cycle to retrieve.

### Response
#### Success Response (200)
- **cycles** (array) - A list of payroll cycle objects.

#### Response Example
```json
{
  "cycles": [
    {
      "id": "cycle-123",
      "name": "January Payroll",
      "start_date": "2023-01-01",
      "end_date": "2023-01-31"
    }
  ]
}
```
```

```APIDOC
## POST /api/admin/payroll-cycles

### Description
Creates a new payroll cycle.

### Method
POST

### Endpoint
/api/admin/payroll-cycles

### Parameters
#### Request Body
- **name** (string) - Required - The name of the payroll cycle.
- **start_date** (string) - Required - The start date of the payroll cycle (YYYY-MM-DD).
- **end_date** (string) - Required - The end date of the payroll cycle (YYYY-MM-DD).

### Request Example
```json
{
  "name": "February Payroll",
  "start_date": "2023-02-01",
  "end_date": "2023-02-28"
}
```

### Response
#### Success Response (201)
- **id** (string) - The ID of the newly created payroll cycle.
- **message** (string) - Success message.

#### Response Example
```json
{
  "id": "cycle-456",
  "message": "Payroll cycle created successfully."
}
```
```

--------------------------------

### Configuration Management Examples (TypeScript)

Source: https://github.com/blackriis/test/blob/main/BYTEROVER_HANDBOOK_backup_20250909_100721.md

Illustrates how environment variables are used for Supabase connection details and how database types and shared UI components are imported. This setup facilitates a modular and configurable application.

```typescript
// Environment Variables (via packages/config)
NEXT_PUBLIC_SUPABASE_URL=https://your-project-ref.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
SUPABASE_SERVICE_ROLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

// Database Types (via packages/database)
import { User, Branch, WorkShift } from '@employee-management/database'

// Shared UI Components (via packages/ui)
import { Button, Form, Input } from '@employee-management/ui'
```

--------------------------------

### Run Database Migrations

Source: https://github.com/blackriis/test/blob/main/PAYROLL_SETUP_GUIDE.md

Executes database migration scripts using Node.js. This command is essential for applying schema changes to your Supabase database.

```bash
node run-migration-direct.cjs
```

--------------------------------

### Update .env.local for Supabase Credentials

Source: https://github.com/blackriis/test/blob/main/PAYROLL_SETUP_GUIDE.md

Configuration for Supabase API URL and keys. These values are used to connect to the Supabase backend. Ensure these are updated with your project's specific credentials for full functionality.

```env
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your-real-anon-key
SUPABASE_SERVICE_ROLE_KEY=your-real-service-role-key
```

--------------------------------

### Project Setup and Build with Chomp

Source: https://github.com/blackriis/test/blob/main/node_modules/es-module-lexer/README.md

This snippet demonstrates the steps to set up the project environment, including cloning repositories, installing dependencies like Chomp, and running tests using Chomp. It assumes specific versions and paths for Emscripten and WASI SDK.

```bash
git clone https://github.com:guybedford/es-module-lexer
git clone https://github.com/emscripten-core/emsdk
cd emsdk
git checkout 1.40.1-fastcomp
./emsdk install 1.40.1-fastcomp
cd ..
wget https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-12/wasi-sdk-12.0-linux.tar.gz
gunzip wasi-sdk-12.0-linux.tar.gz
tar -xf wasi-sdk-12.0-linux.tar
mv wasi-sdk-12.0-linux.tar wasi-sdk-12.0
cargo install chompbuild
cd es-module-lexer
chomp test
```

--------------------------------

### Install min-indent using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/min-indent/readme.md

Installs the min-indent package as a project dependency using npm.

```bash
npm install --save min-indent
```

--------------------------------

### Install postgrest-js

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/postgrest-js/README.md

Installs the postgrest-js library using npm. This is the initial step to use the client in your JavaScript project.

```bash
npm install @supabase/postgrest-js
```

--------------------------------

### Add Example to Command with Callback

Source: https://github.com/blackriis/test/blob/main/node_modules/cac/README.md

Shows how to add a dynamic example to a command, where the example string is generated by a callback function.

```javascript
command.example(name => `${name} --force`)
```

--------------------------------

### Workflow Management Commands

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Commands for initiating, planning, and tracking workflows. This includes starting specific workflows, getting guidance on workflow selection, creating, and updating workflow plans.

```shell
Workflow Commands:
*workflow [name] .... Start specific workflow (list if no name)
*workflow-guidance .. Get personalized help selecting the right workflow
*plan ............... Create detailed workflow plan before starting
*plan-status ........ Show current workflow plan progress
*plan-update ........ Update workflow plan status
```

--------------------------------

### Install Dependencies with npm

Source: https://github.com/blackriis/test/blob/main/node_modules/data-urls/node_modules/whatwg-url/README.md

Fetches the project's dependencies using npm. Ensure Node.js is installed first.

```shell
npm install
```

--------------------------------

### Supabase Realtime Client - Installation

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/realtime-js/README.md

Instructions on how to install the Supabase Realtime client package using npm.

```APIDOC
## Installing the Package

```bash
npm install @supabase/realtime-js
```
```

--------------------------------

### Install auth-js

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/auth-js/README.md

Installs the `@supabase/auth-js` package using npm.

```bash
npm install --save @supabase/auth-js
```

--------------------------------

### POST /api/admin/payroll-cycles/[id]/calculate

Source: https://github.com/blackriis/test/blob/main/PAYROLL_SETUP_GUIDE.md

Calculates payroll for a specific cycle. This endpoint works with improved error messages for cases where employee rate data is missing.

```APIDOC
## POST /api/admin/payroll-cycles/[id]/calculate

### Description
Initiates the payroll calculation for a given payroll cycle ID. Provides enhanced error messages if employee rate data is absent.

### Method
POST

### Endpoint
/api/admin/payroll-cycles/[id]/calculate

### Parameters
#### Path Parameters
- **id** (string) - Required - The ID of the payroll cycle to calculate.

### Response
#### Success Response (200)
- **status** (string) - Indicates the status of the payroll calculation.
- **message** (string) - A message confirming the calculation process has started or completed.

#### Response Example
```json
{
  "status": "Processing",
  "message": "Payroll calculation initiated for cycle [id]."
}
```

#### Error Response (400)
- **error** (string) - Description of the error, e.g., "No employee rate data found. Please ensure employees have hourly or daily rates set up."
```

--------------------------------

### Install NWSAPI for Node.js

Source: https://github.com/blackriis/test/blob/main/node_modules/nwsapi/README.md

This command demonstrates how to install NWSAPI using npm for use in a Node.js environment.

```bash
$ npm install nwsapi
```

--------------------------------

### Install Tinybench

Source: https://github.com/blackriis/test/blob/main/node_modules/tinybench/README.md

This command installs Tinybench as a development dependency using npm.

```bash
npm install -D tinybench
```

--------------------------------

### Install Zustand

Source: https://github.com/blackriis/test/blob/main/node_modules/zustand/README.md

Installs the Zustand library using npm. This is the first step to using Zustand in a project.

```bash
npm install zustand
```

--------------------------------

### Install parse5 using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/parse5/README.md

This command installs the parse5 library as a dependency for your project using npm. Ensure you have Node.js and npm installed.

```bash
npm install --save parse5
```

--------------------------------

### Install storage-js Module

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/storage-js/README.md

Installs the @supabase/storage-js npm package using npm.

```bash
npm install @supabase/storage-js
```

--------------------------------

### Command Example

Source: https://github.com/blackriis/test/blob/main/node_modules/cac/README.md

Adds an example usage for a command, which will be displayed in the help message.

```APIDOC
## Command Example

### Description
Add an example which will be displayed at the end of the help message.

### Method
`command.example(example)`

### Parameters
* **example** (CommandExample) - The example usage string or a function returning the example string.
  * **CommandExample** Type: `((name: string) => string) | string`

### Request Example
```javascript
command.example('build --watch')
// Or using a function:
// command.example(name => `${name} --watch --verbose`)
```
```

--------------------------------

### Correct Course Task Setup and Mode Selection

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Instructions for initiating the 'Correct Course Task', including acknowledging the task, verifying inputs, and selecting an interaction mode (Incremental or YOLO/Batch).

```markdown
# Correct Course Task

## Purpose

- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
- Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
- Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
- Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
- Produce a consolidated "Sprint Change Proposal" document that contains the impact analysis and the clearly drafted proposed edits for user review and approval.
- Ensure a clear handoff path if the nature of the changes necessitates fundamental replanning by other core agents (like PM or Architect).

## Instructions

### 1. Initial Setup & Mode Selection

- **Acknowledge Task & Inputs:**
  - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
  - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
- **Establish Interaction Mode:**
  - Ask the user their preferred interaction mode for this task:
    - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
    - **"YOLO Mode (Batch Processing):** Or, would you prefer I conduct a more batched analysis based on the checklist and then present a consolidated set of findings and proposed changes for a broader review? This can be quicker for initial assessment but might require more extensive review of the combined proposals."
  - Once the user chooses, confirm the selected mode and then inform the user: "We will now use the change-checklist to analyze the change and draft proposed updates. I will guide you through the checklist items based on our chosen interaction mode."
```

--------------------------------

### Install @types/babel__traverse using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/@types/babel__traverse/README.md

This command installs the @types/babel__traverse package as a development dependency in your Node.js project. It ensures TypeScript can correctly type-check your Babel traversal code.

```bash
npm install --save-dev @types/babel__traverse
```

--------------------------------

### Install @types/node using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/@types/node/README.md

This command installs the @types/node package as a development dependency. This package provides type definitions for Node.js, which are essential for using Node.js APIs with TypeScript.

```bash
npm install --save @types/node
```

--------------------------------

### Onboarding Workflow: Handbook and Module Management

Source: https://github.com/blackriis/test/blob/main/CLAUDE.md

This snippet covers the initial steps of the onboarding workflow, including checking handbook existence, creating it if necessary, synchronizing with the codebase, and managing project modules.

```bash
byterover-check-handbook-existence
byterover-create-handbook
byterover-check-handbook-sync
byterover-update-handbook
byterover-list-modules
byterover-store-modules
byterover-update-modules
byterover-store-knowledge
```

--------------------------------

### Install @types/babel__template using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/@types/babel__template/README.md

This command installs the @types/babel__template package as a development dependency. This package provides TypeScript type definitions for the @babel/template library, which is used for creating Babel templates.

```bash
npm install --save @types/babel__template

```

--------------------------------

### Setting up Project and Contributing

Source: https://github.com/blackriis/test/blob/main/node_modules/expect-type/README.md

Illustrates the initial steps for contributing to the project, including installing pnpm and running linting and testing commands to update documentation and snapshots. This ensures consistency and up-to-date project information.

```shell
# Install pnpm globally
npm install --global pnpm

# Run linting to update documentation
npm run lint -- --fix

# Update snapshots for error tests
npm test -- --updateSnapshot

```

--------------------------------

### Install @types/ws with npm

Source: https://github.com/blackriis/test/blob/main/node_modules/@types/ws/README.md

This command installs the @types/ws package as a development dependency using npm. This package provides TypeScript type definitions for the 'ws' library, enhancing code quality and developer experience.

```bash
npm install --save @types/ws
```

--------------------------------

### Build and Run Live Viewer with npm

Source: https://github.com/blackriis/test/blob/main/node_modules/data-urls/node_modules/whatwg-url/README.md

Prepares and builds the live viewer application, then serves its contents. Assumes any web server can be used.

```shell
npm run prepare
npm run build-live-viewer
```

--------------------------------

### Execute a locally installed Node binary (TypeScript)

Source: https://github.com/blackriis/test/blob/main/node_modules/tinyexec/README.md

Shows how tinyexec automatically finds and executes binaries installed in the project's `node_modules`. This example uses `eslint`.

```ts
await x('eslint', ['.']);
```

--------------------------------

### Help Command for Test Project

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

The 'help' command displays a numbered list of available commands, allowing users to select and execute specific testing tasks.

```yaml
commands:
  - help: Show numbered list of the following commands to allow selection
```

--------------------------------

### Clone JSON5 repository and install dependencies - Shell

Source: https://github.com/blackriis/test/blob/main/node_modules/json5/README.md

Steps to clone the JSON5 project from GitHub and install its Node.js dependencies using npm. This is the starting point for contributing to the project.

```shell
git clone https://github.com/json5/json5
cd json5
npm install
```

--------------------------------

### Basic Tinybench Usage

Source: https://github.com/blackriis/test/blob/main/node_modules/tinybench/README.md

Demonstrates how to instantiate the Bench class, add benchmark tasks, run warmup and execution, and display results using console.table. It includes examples of synchronous and asynchronous tasks.

```javascript
import { Bench } from 'tinybench';

const bench = new Bench({ time: 100 });

bench
  .add('faster task', () => {
    console.log('I am faster')
  })
  .add('slower task', async () => {
    await new Promise(r => setTimeout(r, 1)) // we wait 1ms :)
    console.log('I am slower')
  })
  .todo('unimplemented bench')

await bench.warmup(); // make results more reliable, ref: https://github.com/tinylibs/tinybench/pull/50
await bench.run();

console.table(bench.table());

// Output:
// ┌─────────┬───────────────┬──────────┬────────────────────┬───────────┬─────────┐
// │ (index) │   Task Name   │ ops/sec  │ Average Time (ns)  │  Margin   │ Samples │
// ├─────────┼───────────────┼──────────┼────────────────────┼───────────┼─────────┤
// │    0    │ 'faster task' │ '41,621' │ 24025.791819761525 │ '±20.50%' │  4257   │
// │    1    │ 'slower task' │  '828'   │ 1207382.7838323202 │ '±7.07%'  │   83    │
// └─────────┴───────────────┴──────────┴────────────────────┴───────────┴─────────┘

console.table(
  bench.table((task) => ({'Task name': task.name}))
);

// Output:
// ┌─────────┬───────────────────────┐
// │ (index) │       Task name       │
// ├─────────┼───────────────────────┤
// │    0    │ 'unimplemented bench' │
// └─────────┴───────────────────────┘
```

--------------------------------

### Install CSS Parser Algorithms and Tokenizer

Source: https://github.com/blackriis/test/blob/main/node_modules/@csstools/css-parser-algorithms/README.md

Installs the necessary packages for using CSS Parser Algorithms and CSS Tokenizer in a project.

```bash
npm install @csstools/css-parser-algorithms @csstools/css-tokenizer --save-dev
```

--------------------------------

### Development and Build Commands

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Common npm scripts for managing the development server, building for production, running database migrations, and seeding test data.

```bash
npm run dev         # Start development server
npm run build       # Production build
npm run migrate     # Run database migrations
npm run seed        # Seed test data
```

--------------------------------

### onIgnore Callback Example

Source: https://github.com/blackriis/test/blob/main/node_modules/picomatch/README.md

Illustrates the 'onIgnore' callback option, which is triggered when a pattern is ignored. This example sets up an ignore pattern 'f*' and logs details whenever a string starting with 'f' is encountered and ignored.

```javascript
const picomatch = require('picomatch');
const onIgnore = ({ glob, regex, input, output }) => {
  console.log({ glob, regex, input, output });
};

const isMatch = picomatch('*', { onIgnore, ignore: 'f*' });
isMatch('foo');
isMatch('bar');
isMatch('baz');
```

--------------------------------

### Install tslib using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/tslib/README.md

These commands show how to install the tslib library using npm, with specific versions recommended for different TypeScript versions. This ensures compatibility with your project's TypeScript setup.

```bash
# TypeScript 3.9.2 or later
npm install tslib

# TypeScript 3.8.4 or earlier
npm install tslib@^1

# TypeScript 2.3.2 or earlier
npm install tslib@1.6.1

```

--------------------------------

### QA Agent Activation and Core Configuration

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

This section outlines the essential steps for activating the QA agent, including reading its configuration file, adopting its persona, and loading the project's core configuration. It emphasizes adhering to specific activation protocols and interaction rules.

```yaml
activation-instructions:
  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
  - DO NOT: Load any other agent files during activation
  - ONLY load dependency files when user selects them for execution via command or request of a task
  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
  - STAY IN CHARACTER!
  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
```

--------------------------------

### Project Structure Overview

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Illustrates the directory layout of the project, highlighting key directories such as src for source code, tests for testing files, scripts for build/deployment, and config for environment configurations. It also notes specific subdirectories like controllers, services, models, utils, and a legacy directory.

```text
project-root/
├── src/
│   ├── controllers/     # HTTP request handlers
│   ├── services/        # Business logic (NOTE: inconsistent patterns between user and payment services)
│   ├── models/          # Database models (Sequelize)
│   ├── utils/           # Mixed bag - needs refactoring
│   └── legacy/          # DO NOT MODIFY - old payment system still in use
├── tests/               # Jest tests (60% coverage)
├── scripts/             # Build and deployment scripts
└── config/              # Environment configs

```

--------------------------------

### Fetch Plain Text or HTML

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/node-fetch/README.md

An example of making a GET request to a URL and processing the response body as plain text or HTML. It uses the `.then()` method to handle the Promise returned by `fetch` and `.text()` to get the response body.

```javascript
fetch('https://github.com/')
    .then(res => res.text())
    .then(body => console.log(body));
```

--------------------------------

### React Hook Form Quickstart Example

Source: https://github.com/blackriis/test/blob/main/node_modules/react-hook-form/README.md

A basic React component demonstrating the usage of React Hook Form. It includes form registration, submission handling, and basic validation for input fields. The `useForm` hook is central to this example.

```jsx
import { useForm } from 'react-hook-form';

function App() {
  const {
    register,
    handleSubmit,
    formState: { errors },
  } = useForm();

  return (
    <form onSubmit={handleSubmit((data) => console.log(data))}>
      <input {...register('firstName')} />
      <input {...register('lastName', { required: true })} />
      {errors.lastName && <p>Last name is required.</p>}
      <input {...register('age', { pattern: /\d+/ })} />
      {errors.age && <p>Please enter number for age.</p>}
      <input type="submit" />
    </form>
  );
}
```

--------------------------------

### Getting the process ID (API example)

Source: https://github.com/blackriis/test/blob/main/node_modules/tinyexec/README.md

Demonstrates how to retrieve the Process ID (PID) of the currently running child process using the `pid` property.

```ts
const proc = x('ls');

proc.pid; // number
```

--------------------------------

### Brownfield Task Generation Example

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

An example of how to structure implementation tasks for a brownfield project, including analysis, implementation, verification of existing functionality, and test addition.

```markdown
## Tasks / Subtasks

- [ ] Task 1: Analyze existing {{component/feature}} implementation
  - [ ] Review {{specific files}} for current patterns
  - [ ] Document integration points
  - [ ] Identify potential impacts

- [ ] Task 2: Implement {{new functionality}}
  - [ ] Follow pattern from {{example file}}
  - [ ] Integrate with {{existing component}}
  - [ ] Maintain compatibility with {{constraint}}

- [ ] Task 3: Verify existing functionality
  - [ ] Test {{existing feature 1}} still works
  - [ ] Verify {{integration point}} behavior unchanged
  - [ ] Check performance impact

- [ ] Task 4: Add tests
  - [ ] Unit tests following {{project test pattern}}
  - [ ] Integration test for {{integration point}}
  - [ ] Update existing tests if needed
```

--------------------------------

### Getting the process exit code (API example)

Source: https://github.com/blackriis/test/blob/main/node_modules/tinyexec/README.md

Demonstrates accessing the `exitCode` property, which holds the numerical exit code returned by the process upon completion.

```ts
const proc = x('ls');

proc.exitCode; // number (e.g. 1)
```

--------------------------------

### Development Server Command

Source: https://github.com/blackriis/test/blob/main/docs/architecture/nextjs15-compatibility-guide.md

Command to start the development server in Next.js, allowing for manual verification of console errors, particularly related to cookies.

```bash
npm run dev
```

--------------------------------

### Deployment Extensions and Environment Management

Source: https://github.com/blackriis/test/blob/main/BYTEROVER_HANDBOOK_backup_20250908_014828.md

Describes deployment strategies using Vercel, environment management for different configurations (development/production), and automated database migrations via the Supabase CLI.

```typescript
🚀 Deployment Extensions
├── Vercel Platform: Serverless deployment
├── Environment Management: Development/Production configs
└── Database Migrations: Automated via Supabase CLI
```

--------------------------------

### Accessing the underlying Node ChildProcess (API example)

Source: https://github.com/blackriis/test/blob/main/node_modules/tinyexec/README.md

Illustrates how to get the raw Node.js `ChildProcess` object from a tinyexec process. This allows access to all properties and methods of the native ChildProcess.

```ts
const proc = x('ls');

proc.process; // ChildProcess;
```

--------------------------------

### BMAD Task: Facilitate Brainstorming Session

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Provides instructions on using the 'facilitate-brainstorming-session' task within the BMAD Core. It outlines the process, starting with setup questions and progressing to approach options for brainstorming.

```markdown
## <!-- Powered by BMAD™ Core -->

docOutputLocation: docs/brainstorming-session-results.md
template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'

---

# Facilitate Brainstorming Session Task

Facilitate interactive brainstorming sessions with users. Be creative and adaptive in applying techniques.

## Process

### Step 1: Session Setup

Ask 4 context questions (don't preview what happens next):

1. What are we brainstorming about?
2. Any constraints or parameters?
3. Goal: broad exploration or focused ideation?
4. Do you want a structured document output to reference later? (Default Yes)

### Step 2: Present Approach Options

After getting answers to Step 1, present 4 approach options (numbered):

1. User selects specific techniques
2. Analyst recommends techniques based on context
3. Random technique selection for creative variety
4. Progressive technique flow (start broad, narrow down)
```

--------------------------------

### Deployment Extensions and Workflow

Source: https://github.com/blackriis/test/blob/main/BYTEROVER_HANDBOOK_backup_20250908_000459.md

Details deployment extensions, focusing on the Vercel platform for serverless deployment, environment management, and automated database migrations using the Supabase CLI.

```typescript
├── Vercel Platform: Serverless deployment
├── Environment Management: Development/Production configs
└── Database Migrations: Automated via Supabase CLI
```

--------------------------------

### Build Docs with verb

Source: https://github.com/blackriis/test/blob/main/node_modules/picomatch/README.md

Installs the verb CLI and the verb-generate-readme plugin globally, then generates the project's README file. This process relies on a .verb.md template.

```sh
npm install -g verbose/verb#dev verb-generate-readme && verb
```

--------------------------------

### Install tinyexec using npm

Source: https://github.com/blackriis/test/blob/main/node_modules/tinyexec/README.md

Demonstrates how to install the tinyexec package using npm. This is the initial step before using the library in a Node.js project.

```sh
$ npm i -S tinyexec
```

--------------------------------

### Get Tree Iterator (JavaScript)

Source: https://github.com/blackriis/test/blob/main/node_modules/symbol-tree/README.md

Returns an iterator for the entire tree starting from a root node, with configurable options. This operation has a time complexity of O(1).

```javascript
symbolTree.treeIterator(root, options)
```

--------------------------------

### semver Node.js Module Usage Examples

Source: https://github.com/blackriis/test/blob/main/node_modules/semver/README.md

Demonstrates various functionalities of the semver module in Node.js. It covers validating, cleaning, comparing, checking ranges, and coercing versions. Requires the 'semver' package to be installed.

```javascript
const semver = require('semver')

semver.valid('1.2.3') // '1.2.3'
semver.valid('a.b.c') // null
semver.clean('  =v1.2.3   ') // '1.2.3'
semver.satisfies('1.2.3', '1.x || >=2.5.0 || 5.0.0 - 7.2.3') // true
semver.gt('1.2.3', '9.8.7') // false
semver.lt('1.2.3', '9.8.7') // true
semver.minVersion('>=1.0.0') // '1.0.0'
semver.valid(semver.coerce('v2')) // '2.0.0'
semver.valid(semver.coerce('42.6.7.9.3-alpha')) // '42.6.7'
```

--------------------------------

### BMad Master Activation Instructions

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Provides a step-by-step guide for activating the BMad Master agent. It details the order of operations, including reading the file, adopting the persona, loading core configuration, greeting the user, and running the initial '*help' command.

```yaml
activation-instructions:
  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
  - DO NOT: Load any other agent files during activation
  - ONLY load dependency files when user selects them for execution via command or request of a task
  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
  - STAY IN CHARACTER!
  - 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read bmad-core/core-config.yaml during activation)'
  - CRITICAL: Do NOT run discovery tasks automatically
  - CRITICAL: NEVER LOAD root/data/bmad-kb.md UNLESS USER TYPES *kb
  - CRITICAL: On activation, ONLY greet user, auto-run *help, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
```

--------------------------------

### Deployment Extensions (Shell/YAML)

Source: https://github.com/blackriis/test/blob/main/BYTEROVER_HANDBOOK_backup_20250909_100721.md

Covers deployment strategies, including using Vercel for serverless deployment, managing environment configurations, and automating database migrations with the Supabase CLI.

```shell
// Vercel Platform: Serverless deployment
// Environment Management: Development/Production configs
// Database Migrations: Automated via Supabase CLI
```

--------------------------------

### Example Cookie State and `Set-Cookie` Headers (TypeScript/HTTP)

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/ssr/docs/design.md

Illustrates a scenario with chunked cookies in a request and the corresponding `Set-Cookie` headers required for updating and clearing stale cookie data. This highlights the need for `getAll` to inspect all cookie versions.

```typescript
{
   'storage-item': 'value',
   'storage-item.0': 'value',
   'storage-item.1': 'value',
   'storage-item.5': 'value',
}
```

```http
Set-Cookie: storage-item.0=val; Max-Age=<many seconds>
Set-Cookie: storage-item.1=ue;  Max-Age=<many seconds>
Set-Cookie: storage-item=;   Max-Age=0
Set-Cookie: storage-item.5=; Max-Age=0
```

--------------------------------

### Install react-is using Yarn or NPM

Source: https://github.com/blackriis/test/blob/main/node_modules/react-is/README.md

Instructions for installing the react-is package using either Yarn or NPM package managers. This is the first step before using the library in a project.

```sh
# Yarn
yarn add react-is

# NPM
npm install react-is
```

--------------------------------

### Configuring React Refresh Host for Module Federation

Source: https://github.com/blackriis/test/blob/main/node_modules/@vitejs/plugin-react/README.md

This example shows how to set the reactRefreshHost option in @vitejs/plugin-react. This is crucial for module federation setups to ensure Hot Module Replacement (HMR) works correctly between host and remote applications by specifying the host origin.

```javascript
react({ reactRefreshHost: 'http://localhost:3000' })
```

--------------------------------

### Test Environment Configuration (YAML)

Source: https://github.com/blackriis/test/blob/main/docs/qa/database-setup-completion-report.md

This YAML block details the test environment setup, including the Next.js version, Playwright configuration, granted permissions, authentication method, and network details.

```yaml
Application: Next.js 15.5.2 with Turbopack
Test Framework: Playwright with Chromium
Permissions: Camera and Geolocation granted
Authentication: Real Supabase auth with test users
Network: Local development server on localhost:3000
```

--------------------------------

### Parse CSS with Source Tracking in @adobe/css-tools

Source: https://github.com/blackriis/test/blob/main/node_modules/@adobe/css-tools/docs/EXAMPLES.md

Illustrates how to enable source tracking during CSS parsing with the `parse` function from `@adobe/css-tools` by providing a `source` option. This adds position information (source file, start, and end lines/columns) to AST nodes, aiding in debugging and source mapping.

```javascript
import { parse } from '@adobe/css-tools';

const css = 'body { color: red; }';
const ast = parse(css, { source: 'styles.css' });

// Position information is available
const rule = ast.stylesheet.rules[0];
console.log(rule.position?.source); // "styles.css"
console.log(rule.position?.start); // { line: 1, column: 1 }
console.log(rule.position?.end); // { line: 1, column: 20 }
```

--------------------------------

### AI Prompting Principles for Frontend Development

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Outlines key principles for interacting with AI code generation tools to create frontend prompts, including being detailed, iterating, providing context, and adopting a mobile-first approach.

```markdown
# Create AI Frontend Prompt Task

## Purpose

To generate a masterful, comprehensive, and optimized prompt that can be used with any AI-driven frontend development tool (e.g., Vercel v0, Lovable.ai, or similar) to scaffold or generate significant portions of a frontend application.

## Inputs

- Completed UI/UX Specification (`front-end-spec.md`)
- Completed Frontend Architecture Document (`front-end-architecture`) or a full stack combined architecture such as `architecture.md`
- Main System Architecture Document (`architecture` - for API contracts and tech stack to give further context)

## Key Activities & Instructions

### 1. Core Prompting Principles

Before generating the prompt, you must understand these core principles for interacting with a generative AI for code.

- **Be Explicit and Detailed**: The AI cannot read your mind. Provide as much detail and context as possible. Vague requests lead to generic or incorrect outputs.
- **Iterate, Don't Expect Perfection**: Generating an entire complex application in one go is rare. The most effective method is to prompt for one component or one section at a time, then build upon the results.
- **Provide Context First**: Always start by providing the AI with the necessary context, such as the tech stack, existing code snippets, and overall project goals.
- **Mobile-First Approach**: Frame all UI generation requests with a mobile-first design mindset. Describe the mobile layout first, then provide separate instructions for how it should adapt for tablet and desktop.

```

--------------------------------

### Install Playwright and Browsers (npm)

Source: https://github.com/blackriis/test/blob/main/node_modules/playwright/README.md

Installs Playwright test runner as a development dependency and downloads supported browsers. Optionally, only specific browsers can be installed, or no browsers can be installed to use existing browser channels.

```Shell
npm i -D @playwright/test
npx playwright install
```

--------------------------------

### Structured Prompting Framework for AI

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

Details a four-part framework for structuring AI prompts to ensure high-quality output. It covers defining goals, providing detailed instructions, including examples and constraints, and specifying the scope.

```markdown
### 2. The Structured Prompting Framework

To ensure the highest quality output, you MUST structure every prompt using the following four-part framework.

1. **High-Level Goal**: Start with a clear, concise summary of the overall objective. This orients the AI on the primary task.
   - _Example: "Create a responsive user registration form with client-side validation and API integration."
2. **Detailed, Step-by-Step Instructions**: Provide a granular, numbered list of actions the AI should take. Break down complex tasks into smaller, sequential steps. This is the most critical part of the prompt.
   - _Example: "1. Create a new file named `RegistrationForm.js`. 2. Use React hooks for state management. 3. Add styled input fields for 'Name', 'Email', and 'Password'. 4. For the email field, ensure it is a valid email format. 5. On submission, call the API endpoint defined below."
3. **Code Examples, Data Structures & Constraints**: Include any relevant snippets of existing code, data structures, or API contracts. This gives the AI concrete examples to work with. Crucially, you must also state what _not_ to do.
   - _Example: "Use this API endpoint: `POST /api/register`. The expected JSON payload is `{ "name": "string", "email": "string", "password": "string" }`. Do NOT include a 'confirm password' field. Use Tailwind CSS for all styling."
4. **Define a Strict Scope**: Explicitly define the boundaries of the task. Tell the AI which files it can modify and, more importantly, which files to leave untouched to prevent unintended changes across the codebase.
   - _Example: "You should only create the `RegistrationForm.js` component and add it to the `pages/register.js` file. Do NOT alter the `Navbar.js` component or any other existing page or component."

### 3. Assembling the Master Prompt

You will now synthesize the inputs and the above principles into a final, comprehensive prompt.

1. **Gather Foundational Context**:
   - Start the prompt with a preamble describing the overall project purpose, the full tech stack (e.g., Next.js, TypeScript, Tailwind CSS), and the primary UI component library being used.
2. **Describe the Visuals**:
   - If the user has design files (Figma, etc.), instruct them to provide links or screenshots.
   - If not, describe the visual style: color palette, typography, spacing, and overall aesthetic (e.g., "minimalist", "corporate", "playful").
3. **Build the Prompt using the Structured Framework**:
   - Follow the four-part framework from Section 2 to build out the core request, whether it's for a single component or a full page.
4. **Present and Refine**:
   - Output the complete, generated prompt in a clear, copy-pasteable format (e.g., a large code block).
   - Explain the structure of the prompt and why certain information was included, referencing the principles above.
   - <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>
```

--------------------------------

### Install pathe using npm, yarn, or pnpm

Source: https://github.com/blackriis/test/blob/main/node_modules/pathe/README.md

Demonstrates how to install the pathe package using common package managers like npm, yarn, and pnpm. This is the initial step to integrate the library into a project.

```bash
# npm
npm i pathe

# yarn
yarn add pathe

# pnpm
pnpm i pathe
```

--------------------------------

### Install @types/babel__generator

Source: https://github.com/blackriis/test/blob/main/node_modules/@types/babel__generator/README.md

Installs the type definitions for the @babel/generator package using npm. This is a prerequisite for using @babel/generator effectively in TypeScript projects.

```bash
npm install --save @types/babel__generator
```

--------------------------------

### Install Supabase Realtime Client

Source: https://github.com/blackriis/test/blob/main/node_modules/@supabase/realtime-js/README.md

Installs the Supabase Realtime JavaScript client package using npm. This is the initial step to integrate Supabase Realtime features into a project.

```bash
npm install @supabase/realtime-js
```

--------------------------------

### Install Playwright and Browsers (npm)

Source: https://github.com/blackriis/test/blob/main/node_modules/@playwright/test/README.md

Installs the Playwright test dependency and downloads the supported browsers. You can also install specific browsers or rely on existing browser channels.

```Shell
npm i -D @playwright/test
# install supported browsers
npx playwright install
```

--------------------------------

### BMad Orchestrator Activation and Persona

Source: https://github.com/blackriis/test/blob/main/AGENTS.md

This section outlines the activation steps and persona definition for the BMad Orchestrator. It emphasizes reading the entire file, adopting the persona, loading core configurations, and initiating with a greeting and the `*help` command. It also details interaction guidelines, such as using numbered lists for options and always reminding users about the command prefix.

```yaml
activation-instructions:
  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
  - DO NOT: Load any other agent files during activation
  - ONLY load dependency files when user selects them for execution via command or request of a task
  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to select or execute
  - STAY IN CHARACTER!
  - Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
  - IMPORTANT: Tell users that all commands start with * (e.g., `*help`, `*agent`, `*workflow`)
  - Assess user goal against available agents and workflows in this bundle
  - If clear match to an agent's expertise, suggest transformation with *agent command
  - If project-oriented, suggest *workflow-guidance to explore options
  - Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation)
  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
agent:
  name: BMad Orchestrator
  id: bmad-orchestrator
  title: BMad Master Orchestrator
  icon: 🎭
  whenToUse: Use for workflow coordination, multi-agent tasks, role switching guidance, and when unsure which specialist to consult
persona:
  role: Master Orchestrator & BMad Method Expert
  style: Knowledgeable, guiding, adaptable, efficient, encouraging, technically brilliant yet approachable. Helps customize and use BMad Method while orchestrating agents
  identity: Unified interface to all BMad-Method capabilities, dynamically transforms into any specialized agent
  focus: Orchestrating the right agent/capability for each need, loading resources only when needed
  core_principles:
    - Become any agent on demand, loading files only when needed
    - Never pre-load resources - discover and load at runtime
    - Assess needs and recommend best approach/agent/workflow
    - Track current state and guide to next logical steps
    - When embodied, specialized persona's principles take precedence
    - Be explicit about active persona and current task
    - Always use numbered lists for choices
    - Process commands starting with * immediately
    - Always remind users that commands require * prefix
```