VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:backend-development

Production backend builder

Guides production backend work across REST, GraphQL, gRPC, auth, databases, caching, microservices, OWASP security, testing, CI/CD, Docker/Kubernetes, observability, and debugging.

01

Frame backend surface

02

Select stack

03

Design API and data

04

Secure the boundary

Rule 01

Backend implementation is production work: security, data integrity, testing, and operations are part of the surface.

Rule 02

Choose boring stack defaults from the project and requirement, not novelty.

Rule 03

Public APIs need validation, documented errors, auth/rate limits, and contract tests.

Rule 04

Database work is not done without migrations, indexes, backup/restore thinking, and performance evidence.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Frame backend surface Identify whether the work is API design, auth, database, caching, microservice architecture, security, testing, deployment, or production debugging.
  2. 2 Select stack Choose language, framework, database, and API style from project context and trade-offs: Node/NestJS, Python/FastAPI, Go/Gin, Rust/Axum, PostgreSQL, MongoDB, Redis, REST, GraphQL, or gRPC.
02

Work

Agent / skill execution

  1. 3 Design API and data Define schemas, validation, error handling, database schema, indexes, connection pooling, migrations, backups, and performance tests.
  2. 4 Secure the boundary Apply OWASP mitigation, parameterized queries, OAuth 2.1 + PKCE or JWT where appropriate, security headers, rate limiting, input validation, and Argon2id passwords.
03

Verify

Gate, review, validation

  1. 5 Add performance path Use Redis caching, indexing, CDN where applicable, load balancing, query optimization, and event or queue patterns such as Kafka when they serve the requirement.
  2. 6 Test contracts Cover unit, integration, E2E, load, migration, and microservice contract tests using the 70-20-10 testing pyramid as a guide.
04

Close

Report, handoff, artifact

  1. 7 Deploy and observe Ship with Docker, CI/CD, blue-green or canary deployment, feature flags, Prometheus/Grafana monitoring, logging, health checks, and OpenTelemetry tracing.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:backend-development [framework] [task]

Arguments

[framework]

Framework or stack

Existing backend framework and version, or the stack constraints for a comparison. Omit when the project context already supplies it; the Skill does not choose a default framework.

/ak:backend-development nestjs "Add an idempotent orders webhook endpoint"
[task] Required

Backend outcome

Natural-language API, service, auth, data-access, queue, cache, or performance outcome. Include contracts, data ownership, security needs, allowed commands, migration limits, and deployment boundaries.

/ak:backend-development fastapi "Build invoice export endpoints with PostgreSQL; add focused integration tests and do not deploy"

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

API implementation Recommended 
/ak:backend-development fastapi "Build invoice export endpoints with PostgreSQL"
Use when:
Use when backend/API implementation is the main surface.
Expected:
Selects the relevant API-design, database, security, testing, and operations references before shaping the FastAPI endpoint contract and verification path.
Auth backend 
/ak:backend-development nestjs "Add OAuth and RBAC for admin routes"
Use when:
Use when building authentication or authorization systems in a backend service.
Expected:
Uses the authentication and security references to cover OAuth 2.1/JWT choices, RBAC route boundaries, rate limits, validation, and focused tests.
Database performance 
/ak:backend-development go "Optimize high-concurrency order lookup service"
Use when:
Use when backend/API work depends on query optimization, caching, concurrency, or service scaling.
Expected:
Navigates the performance, database, architecture, and debugging references to choose indexing, Redis caching, pooling, load evidence, and observability tactics.
Stack decision 
/ak:backend-development "Compare NestJS, FastAPI, and Go for a public REST API with PostgreSQL and Redis"
Use when:
Use when the backend/API surface needs a technology decision before implementation.
Expected:
Applies the technology selection guide and decision matrix to compare language, framework, database, API style, caching, security, and operational trade-offs.

Handled Scope

  • REST/GraphQL/gRPC APIs
  • Authentication and authorization
  • Database design and migrations
  • Performance and caching
  • OWASP security
  • DevOps and observability

Next