agentleFS
xiaochongxiaochong/hi-kid/CLAUDE.md

hi-kid

CLAUDE.md1.1k starsChanged 6 months agoMITView on GitHub

HiKid - Your AI English Pal. An Electron desktop app built with React and TypeScript, targeting children in non-English-speaking countries who want to practice English speaking and listening. The project follows the standard electron-vite three-process architecture: Path alias: @renderer maps to src/renderer/src/, configured in electron.vite.config.ts and tsconfig.web.json. Build output: Compiled artifacts go to out/ (main, preload, and renderer bundles). The preload script exposes APIs via contextBridge.exposeInMainWorld. When adding new IPC channels:

  • Installs packages

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add types to src/preload/index.d.ts

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

HiKid - Your AI English Pal. An Electron desktop app built with React and TypeScript, targeting children in non-English-speaking countries who want to practice English speaking and listening.

Tech Stack

  • Framework: Electron with electron-vite
  • Frontend: React 19 + TypeScript 5.9 + Vite 7
  • Package Manager: npm
  • Linting: ESLint 9 (flat config) with React, Hooks, and Refresh plugins
  • Formatting: Prettier (singleQuote: true, semi: false, printWidth: 100, trailingComma: none)

Common Commands

# Install dependencies
npm install

# Development with HMR
npm run dev

# Production preview
npm start

# Type checking
npm run typecheck          # Check all
npm run typecheck:node     # Main + preload only
npm run typecheck:web      # Renderer only

# Linting and formatting
npm run lint               # ESLint with cache
npm run format             # Prettier --write

# Building
npm run build              # Type-check + electron-vite build
npm run build:mac          # Build + package for macOS
npm run build:win          # Build + package for Windows
npm run build:linux        # Build + package for Linux
npm run build:unpack       # Build as unpacked directory

Architecture

The project follows the standard electron-vite three-process architecture:

  • src/main/ — Electron main process (Node.js). Entry at index.ts. Handles BrowserWindow creation, app lifecycle, and IPC listeners.
  • src/preload/ — Preload scripts using contextBridge to safely expose APIs to the renderer. index.ts exposes electronAPI (window control) and api (custom APIs). index.d.ts contains type declarations for the global window interface.
  • src/renderer/src/ — React SPA running in the renderer process. Entry at main.tsx, root component at App.tsx.

Path alias: @renderer maps to src/renderer/src/, configured in electron.vite.config.ts and tsconfig.web.json.

Build output: Compiled artifacts go to out/ (main, preload, and renderer bundles).

IPC Pattern

The preload script exposes APIs via contextBridge.exposeInMainWorld. When adding new IPC channels:

  1. Define the channel and API in src/preload/index.ts
  2. Add types to src/preload/index.d.ts
  3. Handle the IPC in src/main/index.ts
  4. Consume it in the renderer via window.api.*

Notes

  • No test framework is configured. There are no unit or e2e tests yet.
  • The project is at a very early stage (single init commit). Core AI/English-learning features are not yet implemented.
  • electron-builder.yml still contains template defaults (productName: electron-app-demo1). Update when ready for distribution.
  • The dev branch is the active development branch; main is the default branch for PRs.

Download now (ZIP)

Trending

Quiet since April.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 2 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the xiaochong/hi-kid repository that our weekly crawl found: only 2 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.