ryne2010
- 9 skills
- 0 followers
- 10 hours ago last updated
- ▌ Harness Engineering Audit · ryne2010 bundleAudit a repository for OpenAI-style harness engineering and Codex/OMX readiness. Use when reviewing AGENTS.md, Codex config, OMX workflows, MCP, hooks, rules, skills, subagents, docs authority, validation commands, repo legibility, visual product spec packs, generated artifact policy, or production readiness for AI-driven development.
- ▌ Zero To Hero · ryne2010 bundlePrepare an idea, prototype, partial app, hardware concept, or messy repository for later Codex implementation by generating canonical requirements, capability-specific documentation, a target-aware agent harness, durable plans, validation contracts, and neutral handoff artifacts. Use for web, API, CLI, mobile, desktop, AI/data, infrastructure, firmware, robotics, mechanical CAD, PCB, or composite projects. This skill never implements target product runtime code.
- ▌ Frontend Parity · ryne2010Build or repair frontend routes against approved visual targets, route capsules, component recipes, screenshot evidence, and no-scaffold gates.
- ▌ Product Usability · ryne2010Complete usable local workflows by binding actions, forms, dataflows, state transitions, local simulators, and runtime evidence.
- ▌ Local Mode Verification · ryne2010Verify that Local Mode is a locally usable product with synthetic data, local persistence, simulators, no real-world effects, and evidence artifacts.
- ▌ Lynx App Builder · ryne2010 bundleUse for Lynx.js app surfaces, ReactLynx screens, pages, dashboards, product surfaces, mobile flows, and visually driven Lynx UI from scratch or redesign. Builds from high-quality image-generated concepts, routes framework truth through official Lynx tooling, applies ReactLynx guardrails, composes UI with local-workspace Lynx UI guidance, and verifies with Lynx DevTool screenshots, $visual-ralph/$visual-verdict evidence, or explicit static/build evidence.
- ▌ Lynx UI Guidance · ryne2010 bundleUse read-only @dumbooks/lynx-ui guidance for Lynx-native UI composition, component selection, registry checks, package-import-first usage, exact export surface and examples lookup, proof gates, official-substrate metadata, guarded CLI boundaries, local-workspace/external-consumer framing, and migration planning. Applies when a Lynx app needs components, tokens, forms, overlays, patterns, themes, visual styles, base colors, or a replacement for DOM-oriented UI-kit assumptions.
- ▌ Stripe Best Practices · ryne2010 bundleOptional service-domain guidance for Stripe integrations used by Lynx.js apps. Guides API selection, Checkout Sessions, PaymentIntents, Connect, subscriptions, and migrations while keeping payment surfaces separate from Lynx UI implementation guidance.
- ▌ Supabase Postgres Best Practices · ryne2010 bundleOptional service-domain guidance for Postgres and Supabase data layers used by Lynx.js apps. Use when writing, reviewing, or optimizing queries, schema designs, indexes, RLS policies, connection behavior, or database configuration; do not use as UI implementation guidance.