Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
Shell Keyboard adds the keys a terminal actually needs — the ones iOS's default keyboard leaves out.
$1.99
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for Shell Keyboard: map the core Developer Tools workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Shell Keyboard adds the keys a terminal actually needs — the ones iOS's default keyboard leaves out. Working over SSH or in a local shell needs Ctrl, Esc, Tab, arrow keys, and function keys, none of which exist on the standard iOS keyboard. Shell Keyboard is a custom keyboard built specifically for terminal apps like Blink, Termius, Prompt, a-Shell and iSH — it sends the exact ASCII control codes and ANSI/VT escape sequences your terminal expects, the same bytes a physical keyboard would send. NEW ON IPAD: A REAL KEYBOARD Choose a 60% or 75% layout, the compact keyboards terminal users already type on. The 75% layout puts Esc, F1–F12, a number row, Caps Lock, Home, End, Page Up, Page Down and inverted-T arrow keys on one screen, and Shift types the symbol printed on each key, just like a physical keyboard. The 60% layout keeps the function keys, navigation and arrows one fn press away. iPad opens in the 75% layout; the original ShellKey layout is one tap away in Settings. WHAT'S INCLUDED • A dedicated terminal layer: Ctrl, Alt, Esc, Tab, arrow keys, Home/End/PgUp/PgDn, and the punctuation a shell prompt uses constantly • Ctrl and Alt as proper modifiers — latch one for a single keypress, or double-tap to lock it on, like a hardware keyboard • A full function-key layer: tap fn and the top row becomes F1 through F12, while every other row stays exactly where it was • Arrow keys that match the app you're in — Normal for shells, Application for vim, tmux, less and htop, or Move the Cursor for ordinary text fields • Return or Enter: long-press the Return key to switch between a carriage return and a line feed • A plain QWERTY layer and a complete symbols layer, for ordinary text — hostnames, paths, commit messages — without leaving the keyboard • Seven themes — Shell, Ember, Glacier, Dusk, Moss, Void (pure black) and High Contrast — each in light and dark, and an Appearance option to keep the keyboard light or dark everywhere • On iPad, 60% and 75% layouts (75% by default), described above • A searchable reference inside the app, listing every key alongside the exact escape sequence and hex bytes it sends • Every key emits the exact byte sequence a real terminal expects SETTINGS LIVE IN THE KEYBOARD Touch and hold the key with the small gear (or tap the gear key on the iPad's 60% and 75% layouts) for Haptic feedback, Theme, Appearance and, on iPad, Layout. They live in the keyboard itself because, without Full Access, iOS keeps a keyboard and its app apart, and Shell Keyboard never asks for Full Access. BUILT FOR PRIVACY Shell Keyboard never asks for Full Access. It cannot reach the network. It never reads, stores, or transmits anything you type — every key it sends is decided from the key you tapped, and nothing else. No analytics, no crash reporting, no account. GOOD TO KNOW In a terminal or editor running inside a web browser — code-server, Jupyter and the like — the keys that send a multi-character escape sequence don't get through: the arrow keys, F1 through F12, Home, End, Page Up, Page Down, Shift+Tab and Alt combinations. Everything that sends a single byte works there normally, including every Ctrl combination, Esc, Tab, Return and ordinary typing. Web pages listen for key press events and iOS only lets a keyboard extension insert text, so this is an iOS limitation that applies to every third-party keyboard, not something an app can work around. WHO IT'S FOR Anyone who SSHes from an iPhone or iPad — sysadmins, developers, and anyone tired of missing Ctrl+C.
Written user reviews are not shown here. Check current App Store reviews >
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: Limited symbol options compared to traditional keyboards
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Customization options are often confusing
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Poor performance on older devices
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Lack of support for different programming languages
Validate with people who use this workflow before building.
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
From the Build Kit assessment.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.