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.
Best use case
1k-dev-commands is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using 1k-dev-commands should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1k-dev-commands/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How 1k-dev-commands Compares
| Feature / Agent | 1k-dev-commands | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# OneKey Development Commands ## Application Development Commands **PLATFORM-SPECIFIC DEVELOPMENT**: - `yarn app:desktop` - Start desktop Electron app development - **Runtime**: 30-60 seconds to start - **Common issues**: Node version conflicts, missing native dependencies - **Troubleshooting**: Run `yarn clean && yarn reinstall` if startup fails - `yarn app:web` - Start web development server (port 3000) - **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 - `yarn app:ext` - Start browser extension development - **Runtime**: 20-40 seconds to start - **Common issues**: Manifest v3 validation errors, permission issues - **Troubleshooting**: Check extension manifest validity, verify content security policy - `yarn app:ios` - Start iOS mobile development - **Runtime**: 1-2 minutes (includes Metro bundler) - **Common issues**: Xcode setup, simulator issues, pod install failures - **Prerequisites**: Xcode installed, iOS simulator available - `yarn app:android` - Start Android mobile development - **Runtime**: 1-2 minutes (includes Metro bundler) - **Common issues**: Android SDK path, emulator setup, gradle build failures - **Prerequisites**: Android Studio, SDK tools, emulator configured - `yarn app:web-embed` - Start embeddable components development - **Runtime**: 15-30 seconds - **Usage**: For developing standalone wallet components ## Build Commands **PRODUCTION BUILDS** (Use for final validation): - `yarn app:desktop:build` - Build desktop app for all platforms - **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 - `yarn app:ext:build` - Build browser extension - **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 - `yarn app:web:build` - Build web application - **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 - `yarn app:native-bundle` - Bundle React Native app - **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:** - `yarn lint:staged` - Lint only staged files (fast, recommended for pre-commit) - `yarn tsc:staged` - Type check (same as tsc:only) **Pre-commit workflow:** ```bash 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:** - `yarn lint` - Comprehensive linting (TypeScript, ESLint, folder structure, i18n) - **Expected runtime**: ~1 minute - **Zero tolerance**: ALL warnings and errors MUST be fixed - **Use case**: CI pipeline and comprehensive pre-PR checks - `yarn test` - Jest test execution - **Use case**: CI pipeline and test validation ### Other Tools - `yarn clean` - Clean all build artifacts and node_modules - `yarn reinstall` - Full clean install (use when dependency issues occur) ## Testing - Jest configuration in `jest.config.js` - Test setup in `jest-setup.js` - Tests located in `@tests/` directories within packages - Mobile tests use `jest-expo` preset
Related Skills
kitt-create-slash-commands
Expert guidance for creating slash commands. Use when working with slash commands, creating custom commands, understanding command structure, or learning YAML configuration.
running-interactive-commands-with-tmux
Controls interactive CLI tools (vim, git rebase -i, REPLs) through tmux detached sessions and send-keys. Use when running tools requiring terminal interaction, programmatic editor control, or orchestrating Claude Code sessions. Triggers include "interactive command", "vim", "REPL", "tmux", or "git rebase -i".
agent-friendly-commands
Use these when you want low-noise lint/test output (good for LLM/CI logs) while staying aligned with repo policy.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
a11y-review
Controleer toegankelijkheid conform WCAG 2.1 AA. Gebruik bij het reviewen van templates, CSS of HTML, of wanneer de gebruiker vraagt om toegankelijkheid te checken.
a11y-personas
Library of accessibility personas representing people with various disabilities, impairments, and situational limitations. Use this skill when users ask about disability types, accessibility personas, user needs for specific conditions, how people with disabilities use technology, assistive technology users, or designing for accessibility. Triggers on requests about blindness, deafness, cognitive disabilities, motor impairments, low vision, screen readers, sign language, autism, ADHD, temporary disabilities, or any question about "how would a person with X use this".
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
a11y-annotation-generator
Adds accessibility annotations (ARIA labels, roles, alt text) to make web content accessible. Use when user asks to "add accessibility", "make accessible", "add aria labels", "wcag compliance", or "screen reader support".
a-share-analysis
Comprehensive China A-share stock analysis covering fundamental analysis, technical analysis, policy impact assessment, and market-specific features (T+1 trading, price limits, northbound capital flow). Use when user asks about A股分析, Chinese mainland stocks, Shanghai/Shenzhen listed stocks, or needs analysis considering China market characteristics.
_backend-mastery
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
9d-framework
9D product development framework
97-dev
Apply timeless programming wisdom from "97 Things Every Programmer Should Know" when writing, reviewing, or refactoring code. Use for design decisions, code quality checks, professional development guidance, testing strategies, and workflow optimization.