Beehive-Blog-V3

Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.

Multi-dimensional code review. Use when reviewing PRs, staged changes, or any code diff. Covers scope, dependencies, testing, performance, and security. Based on htmlpage.cn Cursor Code Review methodology.

Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.

UnoCSS instant atomic CSS engine, superset of Tailwind CSS. Use when configuring UnoCSS, writing utility rules, shortcuts, or working with presets like Wind, Icons, Attributify.

Apply Beehive Blog v3 coding standards. Use when handwritten code is being designed or edited and you need the repository's layer boundaries, directory responsibilities, config rules, and comment conventions.

Apply the contract-first workflow in Beehive Blog v3. Use when a task changes `v3/api/*.api` or `v3/proto/*.proto` and the contract sequence must be handled correctly.

Guide Beehive Blog v3 implementation work while coding. Use when handwritten business code is being added or changed and you need stage-specific implementation guidance without reloading every project rule.

Apply Beehive Blog v3 error and logging standards. Use when touching `pkg/errs`, `pkg/logs`, HTTP/gRPC error mapping, or any business code that logs or matches errors.

Close out a Beehive Blog v3 development task. Use when implementation is done and you need to verify tests, review rules, docs, and final delivery checks.

Run allowed goctl generation in Beehive Blog v3. Use when contracts are already clear and you need Swagger or RPC generation boundaries.

Apply Beehive Blog v3 review-rule enforcement. Use when you need to check or explain the automated rules around `pkg/logs`, `pkg/errs`, and forbidden legacy patterns.

Route a Beehive Blog v3 task at the start of development. Use when a task is just beginning and you need to decide whether it involves contract changes, code generation, handwritten business code, configuration, testing, or documentation updates.

Apply Beehive Blog v3 testing standards. Use when planning or writing tests and you need the repository's testing layers, Testcontainers defaults, and service/repo/logic test boundaries.