1k-dev-commands
Standardized development scripts for building, linting, testing, and managing local servers.
Install
mkdir -p .claude/skills/1k-dev-commands && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4608" && unzip -o skill.zip -d .claude/skills/1k-dev-commands && rm skill.zipInstalls to .claude/skills/1k-dev-commands
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
OneKey development commands plus branch, commit, validation, and PR conventions.Key capabilities
- →Start desktop, web, and mobile development servers
- →Build production-ready application bundles
- →Run linting and type checks
- →Execute Jest test suites
- →Clean build artifacts and reinstall dependencies
How it works
The tool maps standard development lifecycle tasks to specific Yarn scripts that handle platform-specific bundling, linting, and testing configurations.
Inputs & outputs
When to use 1k-dev-commands
- →Start the development server
- →Build production-ready code
- →Run linting and type checks
- →Execute test suites
About this skill
OneKey Development Commands
For branch naming, commit format, rebasing, and PR conventions, read git-workflow.md.
Application Development Commands
PLATFORM-SPECIFIC DEVELOPMENT:
-
yarn app:desktop- Start desktop Electron app development with Rspack- Runtime: 30-60 seconds to start
- Common issues: Node version conflicts, missing native dependencies
- Troubleshooting: Inspect startup logs first; use clean/reinstall only when evidence points to stale build artifacts or broken dependencies
-
yarn app:web:rspack- Start web development server (port 3000)- Runtime: 15-30 seconds to start
- Common issues: Port 3000 already in use, rspack compilation errors
- Troubleshooting: Identify the process using port 3000 before stopping it; preserve unrelated sessions and check console errors
-
yarn app:ext- Start browser extension development with Rspack- Runtime: 20-40 seconds to start
- Common issues: Manifest v3 validation errors, permission issues
- Troubleshooting: Check extension manifest validity, verify content security policy
-
Mobile DevSession launcher - Default path for normal iOS/Android React Native development. Read this guide before starting the app, restoring shell/vendor resources, or attaching UI tooling.
-
Mobile dependency setup - CocoaPods, Pods installation, and missing injected assets.
-
yarn app:ios- Start iOS development through the Mobile DevSession launcher- 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 development through the Mobile DevSession launcher- Runtime: 1-2 minutes (includes Metro bundler)
- Common issues: Android SDK path, emulator setup, gradle build failures
- Prerequisites: Android Studio, SDK tools, emulator configured
-
Direct local native builds:
yarn workspace @onekeyhq/mobile iosandyarn workspace @onekeyhq/mobile android. Use them only when explicitly requested or when diagnosing the launcher. -
yarn app:web-embed- Start embeddable components development- Runtime: 15-30 seconds
- Usage: For developing standalone wallet components
-
yarn app:native-bundle- Prepare iOS/Android development vendor bundles, then start Metro. Wait forDev server ready; this does not install the app.
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: Unpacked extension in
apps/ext/build/chrome_v3/ - 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
Development Tools & Quality Assurance
Pre-commit Commands (Local Development)
Use this for fast agent pre-commit validation:
yarn agent:check --profile commit- Runs worktree auto-fixes, staged lint, type checks, and repository checks with compact output. Matching modified and untracked JS/TS files may be changed byoxlint --fixandoxfmt; inspect the worktree first and preserve unrelated user changes.
Pre-commit workflow:
yarn agent:check --profile commit && git commit -m "your message"
PR Readiness And Remote Status
-
yarn agent:check --profile pr- Local checks and auto-fixes plus remote CI/review status. Use for implementation readiness, not read-only review. -
yarn agent:check --profile ci --pr <number>- Remote CI/review status without local auto-fixes; writes local logs. -
yarn lint- Full project check for CI. For agent validation use the profiles above; use lower-level lint/type commands to diagnose a failed gate. -
Do not run
yarn eslint,npx eslint, ornode_modules/.bin/eslint. ESLint entries are legacy compatibility remnants.
Other Tools
yarn clean- Clean all build artifacts and node_modulesyarn reinstall- Full clean install (use when dependency issues occur)
Testing
- Run the relevant package's test script or a focused Jest test with
yarn jest --runTestsByPath <test-file>. Avoid the ambiguous rootyarn test. - Select tests by failure modes and acceptance criteria; passing lint/types alone does not establish runtime correctness.
- Jest configuration in
jest.config.js - Test setup in
jest-setup.js - Tests located in
@tests/directories within packages - Mobile tests use
jest-expopreset
When not to use it
- →When running outside the OneKey development environment
- →When manual build scripts are required
Prerequisites
Limitations
- →Requires specific platform environment setup
- →Platform-specific dependencies may fail if environment is incomplete
How it compares
It centralizes all project-specific build and development workflows into a single command interface, avoiding manual configuration of complex build tools.
Compared to similar skills
1k-dev-commands side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| 1k-dev-commands (this skill) | 2 | 4mo | Review | Beginner |
| turborepo | 61 | 5mo | Review | Intermediate |
| svelte-expert | 11 | 1y | No flags | Intermediate |
| perf-lighthouse | 13 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by OneKeyHQ
View all by OneKeyHQ →You might also like
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
svelte-expert
Raudbjorn
Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
zod-4
prowler-cloud
Zod 4 schema validation patterns. Trigger: When creating or updating Zod v4 schemas for validation/parsing (forms, request payloads, adapters), including v3 -> v4 migration patterns.
develop-ai-functions-example
vercel
Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures.
adk-engineer
jeremylongshore
Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.