Claude Skills by NeuraCerebra-AI

Use only when the user explicitly invokes or names ship-deep-review, or when an active ship-readiness-orchestrator run explicitly loads it as the required controller. Do not activate from generic audit, review, critique, validation, research, or readiness language; an explicit instruction not to use ship-deep-review always prevents activation.

Use when safely auditing a product, app, UI, or workflow end to end by trying meaningful user paths and finding user-visible breakpoints across UI behavior, runtime errors, state, persistence, forms, navigation, permissions, API/backend symptoms, responsive behavior, accessibility smoke, and workflow clarity. Trigger for product workflow audits, app QA audits, release-readiness checks, changed-UI regression audits, Playwright or Computer Use click-throughs, 'try every path', 'audit the UI and...

Use when the user mentions Shipworthy operationally; asks "are we shipworthy?", "are we shipready?", "is this shipworthy?", "shipworthy this", "check shipworthiness"; uses bare "shipworthy"; or asks for product/release readiness, full safe user-path audit, missing/overcomplicated UX paths, deployability, usability/design teardown, or making an app robust, clearer, simpler, beloved, viral, or effective.

Route and audit workflow clarity, human-obviousness, comprehension, attention, ease of use/ease-of-use, accessibility visibility, trust/proof/governance clarity, and ease-of-use risks in UI/product experiences. Use when auditing apps, pages, flows, dashboards, forms, onboarding, prototypes, games, creative or expert tools, AI copilots, governed or high-risk workflows, mobile/desktop/native/web surfaces, screenshots, DOM/browser traces, design artifacts, repositories, changed UI/workflow chang...

Use only when the user explicitly invokes or names ship-deep-review, or when an active ship-readiness-orchestrator run explicitly loads it as the required controller. Do not activate from generic audit, review, critique, validation, research, or readiness language; an explicit instruction not to use ship-deep-review always prevents activation.

Use when safely auditing a product, app, UI, or workflow end to end by trying meaningful user paths and finding user-visible breakpoints across UI behavior, runtime errors, state, persistence, forms, navigation, permissions, API/backend symptoms, responsive behavior, accessibility smoke, and workflow clarity. Trigger for product workflow audits, app QA audits, release-readiness checks, changed-UI regression audits, Playwright or Computer Use click-throughs, 'try every path', 'audit the UI and...

Use when the user mentions Shipworthy operationally; asks "are we shipworthy?", "are we shipready?", "is this shipworthy?", "shipworthy this", "check shipworthiness"; uses bare "shipworthy"; or asks for product/release readiness, full safe user-path audit, missing/overcomplicated UX paths, deployability, usability/design teardown, or making an app robust, clearer, simpler, beloved, viral, or effective.

Route and audit workflow clarity, human-obviousness, comprehension, attention, ease of use/ease-of-use, accessibility visibility, trust/proof/governance clarity, and ease-of-use risks in UI/product experiences. Use when auditing apps, pages, flows, dashboards, forms, onboarding, prototypes, games, creative or expert tools, AI copilots, governed or high-risk workflows, mobile/desktop/native/web surfaces, screenshots, DOM/browser traces, design artifacts, repositories, changed UI/workflow chang...