Back to results

Filtered result set

25 / 467 matches

SkillHub ClubBuild MobileFull StackFrontendTech Writer

1k-cross-platform

Cross-platform development patterns for OneKey. Use when writing platform-specific code, handling platform differences, or understanding platform extensions. Triggers on platform, native, web, desktop, extension, mobile, ios, android, electron, react native.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
2,326
Hot score
99
Updated
March 20, 2026
Overall rating
A7.8
Composite score
6.7
Best-practice grade
B84.8

Install command

npx @skill-hub/cli install onekeyhq-app-monorepo-1k-cross-platform

Repository

OneKeyHQ/app-monorepo

Skill path: .claude/skills/1k-cross-platform

Cross-platform development patterns for OneKey. Use when writing platform-specific code, handling platform differences, or understanding platform extensions. Triggers on platform, native, web, desktop, extension, mobile, ios, android, electron, react native.

Open repository

Best for

Primary workflow: Build Mobile.

Technical facets: Full Stack, Frontend, Tech Writer, Mobile.

Target audience: Frontend developers working on OneKey applications who need to write platform-specific code for React Native, web, desktop, or browser extension targets.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: OneKeyHQ.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install 1k-cross-platform into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/OneKeyHQ/app-monorepo before adding 1k-cross-platform to shared team environments
  • Use 1k-cross-platform for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: 1k-cross-platform
description: Cross-platform development patterns for OneKey. Use when writing platform-specific code, handling platform differences, or understanding platform extensions. Triggers on platform, native, web, desktop, extension, mobile, ios, android, electron, react native.
allowed-tools: Read, Grep, Glob, Write, Edit
---

# OneKey Cross-Platform Development

## Platform Extensions

Use platform extensions for platform-specific implementations:
- `.native.ts` for React Native (iOS/Android)
- `.web.ts` for web platform
- `.desktop.ts` for desktop platform
- `.ext.ts` for browser extension

## Platform Detection

Use `import platformEnv from '@onekeyhq/shared/src/platformEnv'` for platform detection:

```typescript
import platformEnv from '@onekeyhq/shared/src/platformEnv';

if (platformEnv.isNative) {
  // React Native specific code
}

if (platformEnv.isWeb) {
  // Web specific code
}

if (platformEnv.isDesktop) {
  // Desktop (Electron) specific code
}

if (platformEnv.isExtension) {
  // Browser extension specific code
}
```

## Key Principles

- UI components should work consistently across all platforms
- Keep platform-specific code in separate files with appropriate extensions
- Minimize platform-specific code by keeping common logic separate
- Test across all target platforms

## Common Patterns

### Platform-Specific File Structure
```
MyComponent/
├── index.ts          # Main entry, common logic
├── MyComponent.tsx   # Shared component
├── MyComponent.native.tsx  # React Native specific
├── MyComponent.web.tsx     # Web specific
├── MyComponent.desktop.tsx # Desktop specific
└── MyComponent.ext.tsx     # Extension specific
```

### Conditional Platform Logic
```typescript
// GOOD: Use platformEnv
import platformEnv from '@onekeyhq/shared/src/platformEnv';

function getStoragePath() {
  if (platformEnv.isNative) {
    return 'file://...';
  }
  if (platformEnv.isDesktop) {
    return '/path/to/storage';
  }
  return 'indexeddb://...';
}

// BAD: Direct platform checks
if (typeof window !== 'undefined') { } // ❌
if (process.env.REACT_APP_PLATFORM === 'web') { } // ❌
```

### Platform-Specific Imports
```typescript
// index.ts - Auto-resolves based on platform
export * from './MyComponent';

// The bundler will automatically pick:
// - MyComponent.native.ts on mobile
// - MyComponent.web.ts on web
// - MyComponent.desktop.ts on desktop
// - MyComponent.ext.ts on extension
```

## Platform Considerations

### Extension (Chrome, Firefox, Edge, Brave)
- MV3/service worker lifetimes
- Permissions and CSP
- Background script limitations
- Cross-origin restrictions

### Mobile (iOS/Android)
- WebView limitations
- Native modules
- Background/foreground states
- Deep linking

### Desktop (Electron)
- Security boundaries
- IPC communication
- nodeIntegration settings
- File system access

### Web
- CORS restrictions
- Storage limitations (localStorage, IndexedDB)
- XSS prevention
- Bundle size optimization