@brookmind/ai-toolkit 1.1.7 → 1.2.1

package/agents/code-simplifier.md

@@ -1,52 +0,0 @@
----
-name: code-simplifier
-description: Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
-model: opus
----
-
-You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions. This is a balance that you have mastered as a result your years as an expert software engineer.
-
-You will analyze recently modified code and apply refinements that:
-
-1. **Preserve Functionality**: Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.
-
-2. **Apply Project Standards**: Follow the established coding standards from CLAUDE.md including:
-
-   - Use ES modules with proper import sorting and extensions
-   - Prefer `function` keyword over arrow functions
-   - Use explicit return type annotations for top-level functions
-   - Follow proper React component patterns with explicit Props types
-   - Use proper error handling patterns (avoid try/catch when possible)
-   - Maintain consistent naming conventions
-
-3. **Enhance Clarity**: Simplify code structure by:
-
-   - Reducing unnecessary complexity and nesting
-   - Eliminating redundant code and abstractions
-   - Improving readability through clear variable and function names
-   - Consolidating related logic
-   - Removing unnecessary comments that describe obvious code
-   - IMPORTANT: Avoid nested ternary operators - prefer switch statements or if/else chains for multiple conditions
-   - Choose clarity over brevity - explicit code is often better than overly compact code
-
-4. **Maintain Balance**: Avoid over-simplification that could:
-
-   - Reduce code clarity or maintainability
-   - Create overly clever solutions that are hard to understand
-   - Combine too many concerns into single functions or components
-   - Remove helpful abstractions that improve code organization
-   - Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners)
-   - Make the code harder to debug or extend
-
-5. **Focus Scope**: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.
-
-Your refinement process:
-
-1. Identify the recently modified code sections
-2. Analyze for opportunities to improve elegance and consistency
-3. Apply project-specific best practices and coding standards
-4. Ensure all functionality remains unchanged
-5. Verify the refined code is simpler and more maintainable
-6. Document only significant changes that affect understanding
-
-You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.

package/commands/create-pr-description.md

@@ -1,102 +0,0 @@
----
-description: Generate PR title and description following best practices
----
-
-# Generate PR Description
-
-Extract branch information:
-
-!`git branch --show-current`
-!`git log main..HEAD --oneline --no-merges`
-!`git diff main...HEAD --name-only | grep -v __tests__ | grep -v .spec.`
-
-## Extract Ticket Identifier
-
-Parse the branch name to extract the ticket identifier dynamically:
-
-**Pattern to detect:** `<type>/<prefix>-<number>` (e.g., `feat/api-123`, `fix/bug-456`)
-
-**Extraction logic:**
-1. Get branch name (e.g., `feat/api-123`)
-2. Extract the part after the slash: `api-123`
-3. Split by dash to get prefix (`api`) and number (`123`)
-4. Convert prefix to uppercase: `API`
-5. Combine to form ticket: `API-123`
-
-**Examples:**
-- `feat/dcp-994` → `DCP-994`
-- `fix/api-123` → `API-123`
-- `refactor/proj-456` → `PROJ-456`
-
-**If no ticket pattern found:** Omit ticket from PR title.
-
-## Generate PR Title
-
-Format: `TICKET-123 type: brief description` or `type: brief description` (if no ticket)
-
-**Rules:**
-
-- Extract ticket dynamically from branch name (e.g., `feat/api-123` → `API-123`)
-- Use conventional commit types: `feat:`, `fix:`, `refactor:`, `docs:`, `chore:`, etc.
-- Title description starts uppercase, lowercase after colon
-- Brief and descriptive
-- NO emojis
-
-**Examples:**
-- `API-123 feat: add user authentication endpoint` (from branch `feat/api-123`)
-- `PROJ-456 fix: resolve database connection timeout` (from branch `fix/proj-456`)
-- `refactor: simplify error handling logic` (no ticket in branch name)
-
-Generate PR description:
-
-```
-## Summary
-
-Brief overview of what this PR accomplishes.
-Avoid "Enhance", "Improve", "Fix". Focus on actual changes.
-
-## Changes
-
-### Category Name
-
-- Main change with code elements in `backticks`
-- Another key change
-- Implementation detail
-
-### Another Category (if needed)
-
-- Key change in this category
-- Another important change
-
-### Minor Improvements (if applicable)
-
-- Small cleanup items
-- Minor refactoring
-```
-
-**Category examples based on context:**
-- Backend: API, Database, Authentication, Performance, Error Handling
-- Frontend: UI, Components, State Management, Routing, Styling
-- Infrastructure: CI/CD, Docker, Configuration, Deployment
-- General: Refactoring, Testing, Documentation, Dependencies
-
-**Code formatting:** Use backticks for variables, components, functions, files, endpoints, config values.
-
-**DO NOT include:**
-
-- "Generated with AI" footer
-- Test plan section (unless requested)
-- Files changed list
-- Test file mentions
-- NO emojis
-
-Provide title and description ready for GitHub PR creation.
-
-**CRITICAL FORMATTING RULES:**
-
-- The PR Description MUST be wrapped in a code block with triple backticks ONLY (no language specified)
-- CORRECT: ` followed by content followed by `
-- INCORRECT: `markdown followed by content followed by `
-- All markdown symbols (##, ###, -, etc.) MUST be visible as plain text in the output
-- User should be able to copy the entire code block content directly to GitHub
-- Ensure clarity and conciseness in both title and description

package/commands/create-pr.md

@@ -1,76 +0,0 @@
----
-description: Create PR on GitHub with optional reviewer
----
-
-# Create Pull Request
-
-## Configuration
-
-**Base branch:** Default is `main` (will be detected from repo)
-
-## Pre-flight Checks
-
-Check uncommitted changes:
-!`git status --porcelain`
-
-**If changes exist:** Ask user to commit first (conventional commit), continue anyway, or abort.
-
-Check if branch pushed:
-!`git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null`
-
-**If not pushed:** Auto-push with `git push -u origin HEAD` and inform user.
-
-## Generate PR Title and Description
-
-Use the `/create-pr-description` command to generate the PR title and description.
-
-This command will:
-- Extract branch information and ticket identifiers
-- Generate a properly formatted PR title
-- Create a comprehensive PR description following best practices
-
-**Important:** Store the title and description output from `/create-pr-description` for use in the PR creation step.
-
-## Create PR
-
-**Before creating PR, ask the user:**
-
-"Would you like to add a reviewer to this PR?"
-- If yes: Ask for the GitHub username
-- If no: Skip the reviewer
-
-Use `gh pr create` with the title and description from `/create-pr-description`:
-
-```bash
-# Without reviewer
-gh pr create --base main --title "<TITLE_FROM_COMMAND>" --body "$(cat <<'EOF'
-<DESCRIPTION_FROM_COMMAND>
-EOF
-)"
-
-# With reviewer (if user provided username)
-gh pr create --base main --title "<TITLE_FROM_COMMAND>" --reviewer <username> --body "$(cat <<'EOF'
-<DESCRIPTION_FROM_COMMAND>
-EOF
-)"
-```
-
-**Notes:**
-- Use the exact title generated by `/create-pr-description`
-- Use the exact description generated by `/create-pr-description`
-- Use the Question tool to ask about reviewer
-
-## Output
-
-After creating:
-
-- Display PR URL as clickable link
-- Confirm PR created
-- Confirm reviewer assigned (if applicable)
-
-## Error Handling
-
-- No `gh` auth → tell user to run `gh auth login`
-- PR exists → show existing URL
-- On main/master → abort with error
-- Reviewer can't be assigned → create anyway and inform

package/commands/create-react-tests.md

@@ -1,207 +0,0 @@
----
-description: Generate/update React/TypeScript tests with Jest + RTL (90% coverage)
-agent: build
----
-
-# Generate / Update React & Hook Tests
-
-Generate or update comprehensive tests for TypeScript React components/hooks using Jest + React Testing Library.
-
-**Target:** 90% coverage minimum
-
-## Project Context
-
-**Adapt these to your project:**
-
-- **TypeScript**: Latest version (strict mode, no `any`)
-- **Jest**: Latest version
-- **Testing Library**: @testing-library/react, @testing-library/user-event
-- **Coverage**: 90% all metrics
-- **File Naming**: `*.spec.tsx` for components/hooks, `*.spec.ts` for utils
-- **Location**: `__tests__` sibling folder (or configure as needed)
-
-## Critical Rules
-
-### TypeScript
-
-- **NEVER `any`**. Use types, interfaces, `unknown`, generics
-- Use `jest.mocked(moduleFn)` for typed mocks
-- Safe checks: `Object.prototype.hasOwnProperty.call(obj, key)`
-- ESM imports only
-
-### Window & Browser APIs
-
-**Best Practice**: Abstract browser APIs with utility functions:
-
-```ts
-// utils/windowUtils.ts
-export const getLocationPathname = () => window.location.pathname;
-export const getLocationHostname = () => window.location.hostname;
-export const navigateToUrl = (url: string) => { window.location.href = url; };
-```
-
-Mock in tests:
-
-```ts
-jest.mock("utils/windowUtils", () => ({
-  getLocationPathname: jest.fn(() => "/mock/path"),
-  getLocationHostname: jest.fn(() => "localhost"),
-  navigateToUrl: jest.fn(),
-}));
-```
-
-### Routing
-
-**NEVER hardcode routes.** Import constants:
-
-```ts
-import { ROUTES } from "constants/routes";
-// or import from routing config
-```
-
-### Common Mocks
-
-```ts
-// State management (adjust to your store)
-jest.mock("store/useUserStore");
-
-// Feature flags (if applicable)
-jest.mock("constants/feature-flags", () => ({
-  FEATURE_NAME: "feature-flag-key",
-}));
-
-// React Router (if applicable)
-jest.mock("react-router-dom", () => ({
-  useNavigate: jest.fn(() => jest.fn()),
-  useParams: jest.fn(() => ({})),
-}));
-```
-
-## Test Modes
-
-### Create Mode (New File)
-
-1. Happy Path - baseline render/behavior
-2. Edge Cases - empty, null, undefined
-3. Error Handling - API rejects, exceptions
-4. Behavioral Variants - interactions, branches
-5. Performance (only if memoization)
-
-### Update Mode (Existing File)
-
-1. Remove obsolete tests
-2. Replace direct `window.*` with utility mocks
-3. Add tests for new branches
-4. Maintain ≥90% coverage
-
-## Component Test Template
-
-```ts
-import { render, screen } from '@testing-library/react';
-import userEvent from '@testing-library/user-event';
-import { ComponentName } from '../ComponentName';
-
-const PROP_VARIANTS = [
-    { name: 'default', props: { title: 'Title' } },
-    { name: 'minimal', props: { title: 'T' } },
-];
-
-const renderComponent = (override = {}) => {
-    const base = { title: 'Title', isVisible: true };
-    return render(<ComponentName {...base} {...override} />);
-};
-
-describe('ComponentName', () => {
-    beforeEach(() => jest.clearAllMocks());
-
-    describe('Happy Path', () => {
-        it('renders base state', () => {
-            renderComponent();
-            expect(screen.getByText('Title')).toBeInTheDocument();
-        });
-    });
-
-    describe('Edge Cases', () => {
-        [
-            { label: 'empty title', props: { title: '' } },
-        ].forEach(({ label, props }) => {
-            it(`handles ${label}`, () => {
-                renderComponent(props);
-                expect(screen.getByRole('main')).toBeInTheDocument();
-            });
-        });
-    });
-});
-```
-
-## Hook Test Template
-
-```ts
-import { renderHook, act } from "@testing-library/react";
-import { useCustomHook } from "../useCustomHook";
-
-describe("useCustomHook", () => {
-  it("handles default init", () => {
-    const { result } = renderHook(() => useCustomHook(undefined));
-    expect(result.current).toBeDefined();
-  });
-
-  it("updates state", () => {
-    const { result } = renderHook(() => useCustomHook(undefined));
-    act(() => {
-      result.current.setValue?.(5);
-    });
-    expect(result.current).toBeDefined();
-  });
-});
-```
-
-## Process
-
-1. Determine path: `<dir>/__tests__/<name>.spec.ts[x]`
-2. Check if exists → create or update mode
-3. Parse implementation (branches, external calls, side-effects)
-4. Generate test suites with data tables
-5. Replace direct browser API calls with abstractions
-6. Run quality gates
-
-## Quality Gates
-
-**ALL must pass:**
-
-```bash
-yarn lint                                      # No warnings
-yarn type-check                                # Zero errors
-yarn test path/to/file.spec.tsx --coverage    # ≥90%
-```
-
-## Anti-Patterns
-
-- Direct `window.location.assign(...)` without abstraction
-- Overwriting `window.location.pathname` directly
-- Hardcoded routes like `/dashboard/settings`
-- Deep nesting >3 levels
-- Using `any`
-- Mocking i18n/translation libraries (initialize properly in setup)
-
-## Naming
-
-✅ Good: `it('redirects to overview when role missing')`
-❌ Bad: `it('test redirect 1')`
-
-## Customization Notes
-
-**This template uses:**
-- **yarn** as package manager
-- React Testing Library for component tests
-- Jest as test runner
-- TypeScript strict mode
-- ESM module system
-
-**Adapt for your project:**
-- Different package manager (`npm`, `pnpm`)
-- Different test location (e.g., `src/__tests__`, `tests/`)
-- Different naming convention (e.g., `.test.tsx`)
-- Different coverage thresholds
-- Project-specific mocks and utilities
-- Alternative testing libraries (Vitest, etc.)

package/mcps/context7/.mcp.json

@@ -1,13 +0,0 @@
-{
-  "mcpServers": {
-    "context7": {
-      "type": "remote",
-      "url": "https://mcp.context7.com/mcp",
-      "headers": {
-        "CONTEXT7_API_KEY": "TOKEN_PLACEHOLDER"
-      },
-      "oauth": false,
-      "enabled": true
-    }
-  }
-}

package/mcps/expo-mcp/.mcp.json

@@ -1,13 +0,0 @@
-{
-  "mcpServers": {
-    "expo-mcp": {
-      "type": "remote",
-      "url": "https://mcp.expo.dev/mcp",
-      "headers": {
-        "Authorization": "Bearer TOKEN_PLACEHOLDER"
-      },
-      "oauth": false,
-      "enabled": true
-    }
-  }
-}

package/mcps/figma-mcp/.mcp.json

@@ -1,10 +0,0 @@
-{
-  "mcpServers": {
-    "figma": {
-      "type": "remote",
-      "url": "http://127.0.0.1:3845/mcp",
-      "oauth": false,
-      "enabled": true
-    }
-  }
-}

package/skills/github-cli/SKILL.md

@@ -1,125 +0,0 @@
----
-name: github-cli
-description: This skill should be used when the user wants to interact with GitHub repositories, issues, pull requests, releases, or any GitHub-related operations. Use the gh CLI instead of MCP tools for all GitHub operations.
----
-
-# GitHub CLI Skill
-
-This skill provides instructions for using the `gh` CLI to interact with GitHub, replacing the need for the GitHub MCP server.
-
-## Prerequisites
-
-The `gh` CLI is already authenticated. Verify with:
-
-```bash
-gh auth status
-```
-
-## Pull Requests
-
-```bash
-# List PRs
-gh pr list
-gh pr list --state=all --limit=20
-
-# View PR details
-gh pr view <number>
-gh pr view <number> --comments
-
-# Create PR
-gh pr create --title "Title" --body "Description"
-gh pr create --fill  # Auto-fill from commits
-
-# Review PR
-gh pr review <number> --approve
-gh pr review <number> --request-changes --body "Comments"
-
-# Merge PR
-gh pr merge <number> --squash
-gh pr merge <number> --merge
-
-# Check PR status
-gh pr checks <number>
-```
-
-## Issues
-
-```bash
-# List issues
-gh issue list
-gh issue list --label "bug" --state=open
-
-# View issue
-gh issue view <number>
-
-# Create issue
-gh issue create --title "Title" --body "Description"
-
-# Close issue
-gh issue close <number>
-
-# Add comment
-gh issue comment <number> --body "Comment text"
-```
-
-## Repository Operations
-
-```bash
-# Clone
-gh repo clone owner/repo
-
-# View repo info
-gh repo view owner/repo
-
-# List branches
-gh api repos/{owner}/{repo}/branches --jq '.[].name'
-
-# Get file contents
-gh api repos/{owner}/{repo}/contents/path/to/file --jq '.content' | base64 -d
-```
-
-## Search
-
-```bash
-# Search code
-gh search code "pattern" --repo=owner/repo
-
-# Search issues/PRs
-gh search issues "query" --repo=owner/repo
-gh search prs "query" --repo=owner/repo
-```
-
-## Releases
-
-```bash
-# List releases
-gh release list
-
-# View latest
-gh release view --latest
-
-# Create release
-gh release create v1.0.0 --title "v1.0.0" --notes "Notes"
-```
-
-## API Access
-
-For any operation not covered above, use the generic API:
-
-```bash
-# GET request
-gh api repos/{owner}/{repo}/endpoint
-
-# POST request
-gh api repos/{owner}/{repo}/issues -f title="Title" -f body="Body"
-
-# With JQ filtering
-gh api repos/{owner}/{repo}/pulls --jq '.[].title'
-```
-
-## Tips
-
-- Most commands accept `--json` for JSON output
-- Use `--jq` to filter JSON responses
-- From a git repo, `gh` auto-detects owner/repo
-- Use `-R owner/repo` to specify a different repository