leanspec-development_skill

Overview

This skill describes development workflows and contribution guidelines for LeanSpec. It focuses on setting up the development environment, following mandatory conventions, and safely delegating work to subagents for complex tasks. Use it to streamline contributions, validations, and cross-package investigations in a TypeScript + Rust monorepo.

How this skill works

The skill inspects repository conventions, essential commands, and core principles to ensure consistent contributions. It guides setup (pnpm, build), validation (tests, lint, clippy), and delegation patterns using runSubagent for multi-file or cross-package exploration. It also highlights mandatory rules like i18n updates, theme support, and regression-test requirements.

When to use it

• Setting up or reproducing the development environment on a new machine
• Contributing code, fixing bugs, or preparing a PR for CI validation
• Running full validation before release: typecheck, tests, lint, build
• Investigating cross-package behavior or searching patterns across the monorepo
• Deciding whether to delegate complex searches or debugging to a subagent

Best practices

• Always use pnpm; do not use npm or yarn for this project
• Run pre-release validation (typecheck, tests, lint, build) before opening a PR
• Include failing-then-passing regression tests for bug fixes
• Update both en and zh-CN translations when changing UI text
• Follow Rust quality rules: run cargo clippy -- -D warnings and fix warnings
• Prefer DRY: extract shared logic into common packages and leverage Turborepo caching

Example use cases

• A new contributor sets up the workspace: pnpm install, pnpm build, then pnpm dev:web to run the UI
• Fixing a validation bug: runSubagent to find all spec validation logic across TypeScript and Rust packages, add tests, and run pnpm pre-release
• Performance improvement: use Turborepo to verify cache hits and reduce build times locally
• CLI change: use pnpm dev:cli for watch-mode iteration and run lint:rust when touching Rust code
• Cross-package refactor: search and update interfaces across packages, then run test:run to validate CI-like behavior