跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
安全

ship-it-backend

Turn product requirements, MVP plans, frontend flows, or rough backend requests into production-minded, verified server-side vertical slices in new or existing codebases. Use for adding or completing an API endpoint, database-backed feature, service workflow, webhook or job, authorization rule, or backend integration including the contract, schema and migrations, business logic, validation, stable errors, integrity controls, focused tests, and a frontend-ready handoff. Preserve an existing repository's stack and patterns. For a new project, let the user choose the database, cache, and relevant middleware before implementation. Do not use for standalone deep security audits, performance tuning, infrastructure design, or cloud deployment.

nanfei892 · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add nanfei892/ship-it-skills --skill ship-it-backend

技能说明


name: ship-it-backend description: Turn product requirements, MVP plans, frontend flows, or rough backend requests into production-minded, verified server-side vertical slices in new or existing codebases. Use for adding or completing an API endpoint, database-backed feature, service workflow, webhook or job, authorization rule, or backend integration including the contract, schema and migrations, business logic, validation, stable errors, integrity controls, focused tests, and a frontend-ready handoff. Preserve an existing repository's stack and patterns. For a new project, let the user choose the database, cache, and relevant middleware before implementation. Do not use for standalone deep security audits, performance tuning, infrastructure design, or cloud deployment.

Ship It: Backend

Ship one backend capability end to end. Turn intent into running code and evidence, not an architecture proposal or a collection of disconnected layers.

Commit to the outcome

  • Treat product requirements, an MVP blueprint, UI flows, tickets, and existing code as inputs to one implementation.
  • Resolve ordinary ambiguity from repository conventions and the smallest coherent product behavior. State material assumptions in the handoff.
  • Ask only for required greenfield stack choices or when an answer would change an irreversible data contract, a security boundary, an external system, or the fundamental product behavior.
  • Preserve the current language, framework, database, package manager, architecture, and local conventions unless the user explicitly requests a change.
  • When no backend exists, follow the greenfield selection workflow below instead of silently choosing infrastructure.
  • Keep the slice narrow. Do not introduce speculative abstractions, services, queues, caches, or dependencies.
  • Finish implementation and proportional verification in the same task. Do not stop after scaffolding, pseudocode, or a plan unless the user asks for one.

Let the user choose a greenfield stack

When a project has no established backend, obtain the user's infrastructure choices before scaffolding or installing dependencies. Do not ask again for choices already stated in the request or fixed by the repository, hosting environment, or product constraints.

Present one compact selection prompt. Recommend an option when context supports it, explain the recommendation in one sentence, and still let the user choose. Include these choices for every relevant category:

CategoryExample options
DatabasePostgreSQL, MySQL or MariaDB, SQLite, a document database such as MongoDB, none, or a custom choice
CacheRedis or Valkey, in-process cache, none, or a custom choice
Background jobs or messagingDatabase-backed jobs, RabbitMQ, Kafka, a managed queue, none, or a custom choice
Feature-specific middlewareObject storage, search, email delivery, or another dependency only when the product requires it; none or a custom choice

If the language or framework is also undecided, include two to four compatible options in the same prompt plus a custom choice. Keep the decision understandable by describing product impact such as operational effort, local simplicity, scaling characteristics, or hosting compatibility rather than listing brand names without context.

  • Always offer Custom so the user can enter a component not listed.
  • Always offer None for optional middleware. Choosing none means do not install, configure, or scaffold that component.
  • Do not propose a queue, cache, search engine, or object store without a concrete requirement for it.
  • Flag incompatible combinations and offer compatible alternatives, but leave the final choice to the user.
  • Wait for confirmation before provisioning services, adding infrastructure dependencies, or creating framework-specific persistence code.
  • After confirmation, start with one deployable service and establish migrations and a test harness with the first slice.
  • Record the selected components and intentionally omitted middleware in the final handoff.

Inspect before designing

Read the repository before choosing an implementation:

  1. Find repository instructions, manifests, configuration, and the commands used for tests, linting, type checks, migrations, and local execution.
  2. Trace one nearby feature through its route or handler, validation, authorization, domain or service logic, persistence, errors, and tests.
  3. Inspect the current schema, migration history, transaction helpers, ID and timestamp conventions, and test fixtures.
  4. Identify shared API response shapes, pagination rules, error middleware, logging, background-job patterns, and external-client wrappers.
  5. Check the worktree and preserve unrelated user changes.

Prefer the closest working local pattern over generic framework advice. Add a new abstraction only when the requested slice cannot fit the existing structure cleanly.

Define the contract

Before editing, reduce the request to a compact delivery contract:

  • Actor and capability: who performs which action.
  • Inputs: path, query, body, headers, event payload, or job arguments.
  • Success: observable response or side effect, including status and response shape when applicable.
  • Invariants: truths that must hold regardless of entry point, such as ownership, legal state transitions, uniqueness, limits, and resource availability.
  • Failures: invalid input, unauthenticated or forbidden access, missing resources, conflicts, dependency failure, and retry behavior relevant to this capability.
  • State change: records created or modified, external effects, and transaction boundary.

Infer this contract from the product flow and existing API style. Do not create a separate specification file unless the repository already treats one as the source of truth.

Model truth and invariants

  • Put business invariants in the domain or service layer so every entry point shares the
阅读完整来源 ↗