mcpField
P
prototype-to-production

prototype-to-production

github.com/kemiljkDevelopment6158 installsUpdated 1w ago
Repository

About prototype-to-production

A skill for turning working prototypes into production-ready software through edge-case reviews, explicit state handling, accessibility, security, and reliability checks. It is intended for developers preparing an application for release.

Key features

  1. 01Prototype hardening checklist
  2. 02Edge-case and failure-path review
  3. 03Accessibility and interaction checks
  4. 04Auth and permission review
  5. 05Observability and critical-flow tests

Use cases

  1. 01Preparing a prototype for release
  2. 02Reviewing forms and network failures
  3. 03Checking large lists and empty states

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/kemiljk/skills --skill prototype-to-production

After installing, type/prototype-to-productionin Claude Code to confirm it loaded.

Details

From the project README

Prototype to Production

Prototypes prove possibility. Production earns trust. Do not confuse a working happy path with a shippable system.

Defaults

  1. Keep the prototype's learning; replace its shortcuts.
  2. Enumerate edge cases before polishing visuals.
  3. Accessibility, auth, empty states, and failure paths are release requirements.
  4. Prefer boring, clear state models over clever demos.
  5. Measure what breaks under slow networks, large data, and repeat use.

Hardening map

Prototype shortcutProduction replacement
Mock data onlyReal loading/error/empty states
Client-only auth theatreReal session/permission checks
Happy-path formsValidation, constraints, recoverable errors
Index keys / remounting tricksStable identities
Hardcoded valuesTokens and configuration
Desktop-only interactionKeyboard, touch, reduced-motion paths

Prefer / Reject

PreferReject
Explicit state machines or clear state transitionsHidden flags that only work in the demo script
Progressive enhancementSingle-path demos with no fallback
Observability and basic tests around critical flows"We'll notice if it breaks"
Deleting demo-only codeShipping scaffolding because it already exists

Review checklist

  • What happens with zero items, huge lists, and partial failure?
  • Are permissions enforced on the server, not only hidden in the UI?
  • Do forms recover from invalid input and network failure?
  • Is focus management correct for dialogs/menus?
  • Does reduced motion still complete the task?
  • Are secrets, keys, and debug hooks gone?
  • Can another engineer maintain this without the prototype narration?

Source essays

  • On vibe coding vs shipping to production
  • On the complexity of production codebases
  • Design engineering handshake writing

Comments

Markdown supported