More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Automated Product Engineer

    1

    Build production-ready web and native features from brief to verified PR.

    $50

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Automated Product Engineer

    Example session with this skill installed

    Use the automated-product-engineer skill to build a project delivery dashboard in this existing Next.js app. Projects should be searchable and sortable, with completion rate, open blockers, and recent activity shown for a selected date range. Reuse the design system, verify permissions and data ownership, cover loading, empty, and error states, test the behavior, capture desktop and mobile screenshots, and open a draft PR. Do not merge.

    • Read your context and instructions
    • Compiled the automated product engineer

    Shipped: project delivery dashboard

    Built the dashboard as a complete, reviewable feature rather than an isolated table.

    Product result

    • Added a date-range-aware project dashboard with search, ascending and descending sorting, pagination, and clear empty and error states.
    • Reused the existing table, input, badge, and semantic color primitives.
    • Kept delivery metrics server-owned and restricted the route and query to authorized workspace members.
    • Preserved filters in the URL so views survive refresh and can be shared.
    • Added compact tablet and mobile layouts without hiding the comparison metrics.

    Architecture

    The page owns composition and URL state. A focused query hook owns remote cache state. The route handler authenticates and validates input, then delegates to the delivery metrics service. The service owns authorization, date boundaries, aggregation, deterministic sorting, and pagination. No business rules were added to the table component.

    Verification

    GateResult
    Focused service and route testsPassed
    Component interaction testsPassed
    Typecheck and lintPassed
    Production buildPassed
    Desktop and mobile browser QAPassed
    Keyboard, refresh, retry, and overflow checksPassed

    Captured before-and-after screenshots for desktop and mobile and attached them to the draft pull request.

    Review handoff

    Opened a draft PR with the user-visible change, data and authorization boundaries, test evidence, screenshots, known assumptions, and rollback path. No merge or production deployment was performed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Automated Product Engineer turns a product brief, Figma design, Claude Design export, screenshot, or existing flow into a review-ready production feature—not a disconnected mockup.

    It inspects the repository first, asks only the decisions that materially affect behavior or architecture, and then carries the work through implementation, responsive and accessible UI, full-stack boundaries, focused tests, browser QA, demo screenshots, retrospective fix-back, and a draft pull request.

    Use it to:

    • Build or substantially redesign features in existing applications
    • Keep UI, state, APIs, services, persistence, authorization, and analytics cleanly owned
    • Reuse semantic tokens and component systems instead of adding one-off code
    • Cover loading, empty, failure, retry, permission, responsive, and accessibility states
    • Deliver evidence: tests, screenshots, risks, rollback notes, and a review-ready PR
    • Work across Next.js, Expo and React Native, native iOS, native Android, and Kotlin Multiplatform

    The workflow preserves human control over material product decisions, releases, and merges.

    See Auto in action · Install from npm · Open-source project

    Results depend on the quality and accessibility of the target repository, design sources, and local toolchain. Native release verification still requires the relevant Xcode or Android environment, signing access, and human review. The skill prepares draft pull requests but does not merge or deploy without explicit authorization.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Requires

    GitHub
    Npmjs
    Node.js 20+
    pnpm
    Git
    A SKILL.md-compatible coding agent

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Browser
    Network Access
    Environment Variables

    Allowed Hosts

    github.com
    npmjs.com

    File Scopes

    **/*

    Reads the target repository to understand its architecture and design system; writes only the requested feature, tests, documentation, and delivery artifacts. Uses the terminal for installation and validation, browser access for manual QA and screenshots, and network access for package installation and optional draft-PR delivery. Environment variables are read only when the host project requires them and must never be exposed.

    Listed24 days ago
    Updated22 days ago

    What's inside

    Frequently Asked Questions

    No. Auto prepares a review-ready draft pull request with evidence, risks, and rollback notes. A human remains the release and merge authority unless they explicitly authorize a later action.

    Yes. Auto begins by inspecting the existing repository, architecture, design system, data boundaries, tests, and active work. It adapts to established conventions instead of generating a parallel application.

    The toolkit includes workflows for Next.js and full-stack web apps, Expo and React Native, native Swift iOS, native Kotlin Android, and Kotlin Multiplatform projects.

    New in Agents & Orchestration