Claude-skill-registry 1k-dev-commands
Development commands for OneKey monorepo. Use when running dev servers, building apps, linting, testing, or troubleshooting build issues. Triggers on yarn, dev, build, lint, test, desktop, mobile, web, extension, ios, android, compile, bundle.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/1k-dev-commands" ~/.claude/skills/majiayu000-claude-skill-registry-1k-dev-commands && rm -rf "$T"
manifest:
skills/data/1k-dev-commands/SKILL.mdsource content
OneKey Development Commands
Application Development Commands
PLATFORM-SPECIFIC DEVELOPMENT:
-
- Start desktop Electron app developmentyarn app:desktop- Runtime: 30-60 seconds to start
- Common issues: Node version conflicts, missing native dependencies
- Troubleshooting: Run
if startup failsyarn clean && yarn reinstall
-
- Start web development server (port 3000)yarn app:web- Runtime: 15-30 seconds to start
- Common issues: Port 3000 already in use, webpack compilation errors
- Troubleshooting: Kill existing processes on port 3000, check console for specific errors
-
- Start browser extension developmentyarn app:ext- Runtime: 20-40 seconds to start
- Common issues: Manifest v3 validation errors, permission issues
- Troubleshooting: Check extension manifest validity, verify content security policy
-
- Start iOS mobile developmentyarn app:ios- Runtime: 1-2 minutes (includes Metro bundler)
- Common issues: Xcode setup, simulator issues, pod install failures
- Prerequisites: Xcode installed, iOS simulator available
-
- Start Android mobile developmentyarn app:android- Runtime: 1-2 minutes (includes Metro bundler)
- Common issues: Android SDK path, emulator setup, gradle build failures
- Prerequisites: Android Studio, SDK tools, emulator configured
-
- Start embeddable components developmentyarn app:web-embed- Runtime: 15-30 seconds
- Usage: For developing standalone wallet components
Build Commands
PRODUCTION BUILDS (Use for final validation):
-
- Build desktop app for all platformsyarn app:desktop:build- Runtime: 5-10 minutes (multi-platform build)
- Output: Platform-specific installers in
apps/desktop/dist/ - Common issues: Code signing, platform-specific dependencies
- Verification: Test installers on target platforms
-
- Build browser extensionyarn app:ext:build- Runtime: 2-3 minutes
- Output: Extension packages in
apps/ext/dist/ - Common issues: Manifest validation, content security policy violations
- Verification: Load extension in browser for testing
-
- Build web applicationyarn app:web:build- Runtime: 3-5 minutes
- Output: Static files in
apps/web/dist/ - Common issues: Bundle size limits, missing environment variables
- Verification: Serve built files and test functionality
-
- Bundle React Native appyarn app:native-bundle- Runtime: 3-5 minutes
- Output: Platform-specific bundles
- Common issues: Native module linking, Metro bundler errors
- Prerequisites: Platform development environment properly configured
Development Tools & Quality Assurance
Pre-commit Commands (Local Development)
Use these for fast pre-commit validation:
- Lint only staged files (fast, recommended for pre-commit)yarn lint:staged
- Type check (same as tsc:only)yarn tsc:staged
Pre-commit workflow:
yarn lint:staged && yarn tsc:staged && git commit -m "your message"
CI Commands (Full Project Check)
These run in CI pipeline or for comprehensive validation:
- Comprehensive linting (TypeScript, ESLint, folder structure, i18n)yarn lint- Expected runtime: ~1 minute
- Zero tolerance: ALL warnings and errors MUST be fixed
- Use case: CI pipeline and comprehensive pre-PR checks
- Jest test executionyarn test- Use case: CI pipeline and test validation
Other Tools
- Clean all build artifacts and node_modulesyarn clean
- Full clean install (use when dependency issues occur)yarn reinstall
Testing
- Jest configuration in
jest.config.js - Test setup in
jest-setup.js - Tests located in
directories within packages@tests/ - Mobile tests use
presetjest-expo