keyvaluesoftwaresystems
- 89 skills
- 0 followers
- 4 hours ago last updated
- ▌ Clickhouse Io · keyvaluesoftwaresystemsClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
- ▌ Quarkus Tdd · keyvaluesoftwaresystemsTest-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.
- ▌ Vue Patterns · keyvaluesoftwaresystemsVue.js 3 Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns. Activates for Vue, Nuxt, Vite, or Pinia projects.
- ▌ Mysql Patterns · keyvaluesoftwaresystemsMySQL and MariaDB schema, query, indexing, transaction, replication, and connection-pool patterns for production backends.
- ▌ Redis Patterns · keyvaluesoftwaresystemsRedis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications.
- ▌ Golang Testing · keyvaluesoftwaresystemsGo testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
- ▌ Jpa Patterns · keyvaluesoftwaresystemsJPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
- ▌ Django Tdd · keyvaluesoftwaresystemsDjango testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
- ▌ Rust Testing · keyvaluesoftwaresystemsRust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
- ▌ Prisma Patterns · keyvaluesoftwaresystemsPrisma ORM patterns for TypeScript backends — schema design, query optimization, transactions, pagination, and critical traps like updateMany returning count not records, $transaction timeouts, migrate dev resetting the DB, @updatedAt skipped on bulk writes, and serverless connection exhaustion.
- ▌ Golang Patterns · keyvaluesoftwaresystemsIdiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
- ▌ Vite Patterns · keyvaluesoftwaresystemsVite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.
- ▌ Rust Patterns · keyvaluesoftwaresystemsIdiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
- ▌ Nuxt4 Patterns · keyvaluesoftwaresystemsNuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
- ▌ Springboot Tdd · keyvaluesoftwaresystemsTest-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
- ▌ React Testing · keyvaluesoftwaresystemsReact component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
- ▌ Postgres Patterns · keyvaluesoftwaresystemsPostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
- ▌ Nestjs Patterns · keyvaluesoftwaresystemsNestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production-grade TypeScript backends.
- ▌ Django Celery · keyvaluesoftwaresystemsDjango + Celery async task patterns — configuration, task design, beat scheduling, retries, canvas workflows, monitoring, and testing. Use when adding background jobs, scheduled tasks, or async processing to a Django app.
- ▌ Quarkus Patterns · keyvaluesoftwaresystemsQuarkus 3.x LTS architecture patterns with Camel for messaging, RESTful API design, CDI services, data access with Panache, and async processing. Use for Java Quarkus backend work with event-driven architectures.
- ▌ Quarkus Security · keyvaluesoftwaresystemsQuarkus Security best practices for authentication, authorization, JWT/OIDC, RBAC, input validation, CSRF, secrets management, and dependency security.
- ▌ Kotlin Testing · keyvaluesoftwaresystemsKotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
- ▌ Python Testing · keyvaluesoftwaresystemsPython testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
- ▌ Database Migrations · keyvaluesoftwaresystemsDatabase migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
- ▌ Kotlin Patterns · keyvaluesoftwaresystemsIdiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders.
- ▌ Django Patterns · keyvaluesoftwaresystemsDjango architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
- ▌ Django Security · keyvaluesoftwaresystemsDjango security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
- ▌ Python Patterns · keyvaluesoftwaresystemsPythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.
- ▌ Fastapi Patterns · keyvaluesoftwaresystemsFastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest.
- ▌ Pytorch Patterns · keyvaluesoftwaresystemsPyTorch deep learning patterns and best practices for building robust, efficient, and reproducible training pipelines, model architectures, and data loading.
- ▌ Springboot Patterns · keyvaluesoftwaresystemsSpring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
- ▌ Springboot Security · keyvaluesoftwaresystemsSpring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.
- ▌ Angular Developer · keyvaluesoftwaresystemsGenerates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
- ▌
- ▌
- ▌
- ▌ Kotlin Ktor Patterns · keyvaluesoftwaresystemsKtor server patterns including routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing.
- ▌
- ▌ Dart Flutter Patterns · keyvaluesoftwaresystemsProduction-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
- ▌ Kotlin Coroutines Flows · keyvaluesoftwaresystemsKotlin Coroutines and Flow patterns for Android and KMP — structured concurrency, Flow operators, StateFlow, error handling, and testing.
- ▌ Kotlin Exposed Patterns · keyvaluesoftwaresystemsJetBrains Exposed ORM patterns including DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern.
- ▌ Flutter Dart Code Review · keyvaluesoftwaresystemsLibrary-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
- ▌ Android Clean Architecture · keyvaluesoftwaresystemsClean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
- ▌ Compose Multiplatform Patterns · keyvaluesoftwaresystemsCompose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
- ▌ Market Research Analyst · keyvaluesoftwaresystems bundleMarket research and launch-decision engine for D2C founders and startups. Runs structured competitor analysis, product-market-fit analysis, or a full launch assessment that ends in a GO / NO-GO verdict. Always use this skill when a founder or user wants to research a brand, product, market, or competitor, or is deciding whether to start a product business — including any request to analyse, study, compare, validate, or understand customer sentiment, pricing, flavours/variants, market size or CAGR, funding, whitespace, go-to-market, brand ambassadors, manufacturing (own plant vs contract), unmet needs, or whether a product idea is worth building. Trigger even if they just describe a product (chocolate, protein bar, toothpaste, supplement, skincare, apparel, SaaS) and ask general questions about the market or whether to launch.
- ▌ Marketing Intelligence Agent · keyvaluesoftwaresystems bundleMarketing Intelligence Agent. Use when the user says "run daily report", "run weekly report", "show dashboard", "marketing report", or "setup". Pulls live Meta Ads data, generates insights, sends a Slack summary and optionally a WhatsApp message, and renders a performance dashboard. The "setup" command walks through full configuration and prints routine setup instructions. Requires Meta Ads MCP and Slack MCP to be connected. WhatsApp is optional.
- ▌ Netra MCP Usage · keyvaluesoftwaresystemsNetra MCP trace-debugging workflow focused on query_traces, get_trace_by_id, and get_session_details, including exact input parameters, filter schema, operators, sorting, and pagination patterns.
- ▌ Netra Best Practices · keyvaluesoftwaresystems bundleCode-first Netra best-practices playbook covering setup, instrumentation, context tracking, custom spans/metrics, integration patterns, evaluation, simulation, and troubleshooting.
- ▌ Netra Evaluation Setup · keyvaluesoftwaresystemsGenerate evaluation datasets from QA/dev specification documents. Analyzes spec sheets, discovers agent span structure from code, recommends evaluators, auto-configures variable mappings, and produces an editable plan for review. Use when the user says: NDD generate, create test suite, generate dataset from spec, create evaluation plan, generate NDD plan, or provides a QA specification document.
- ▌ Opfor MCP Run · keyvaluesoftwaresystems bundleRun red-team attacks and generate a report for an MCP server target.
- ▌ Opfor Run · keyvaluesoftwaresystems bundleRun red-team attacks and generate a report for an agent target.
- ▌
- ▌ Opfor Setup · keyvaluesoftwaresystems bundleSet up an agent or chatbot target for Opfor red-teaming.
- ▌ Maestro · keyvaluesoftwaresystemsLead agent for Maestro workflows — drives a workflow.yaml end-to-end by carrying out engine-served lead actions, dispatching workers, and asking humans. Front door for /maestro or $maestro with a feature slug and optional workflow file. Use when the user wants to run, resume, or continue an orchestrated SDLC flow for a feature.
- ▌ Plan · keyvaluesoftwaresystemsProduce a concise, decision-focused high-level design (HLD) for a feature. Ground the direction in requirements and the existing system, record only material trade-offs, and write a developer-readable hld.md. Read-only except for the HLD and open-question artifacts. Front door for /plan.
- ▌ Verify · keyvaluesoftwaresystemsRun the project's deterministic checks and produce an evidence-backed proof report plus a machine-readable proof marker. Never modifies code (writes only its proof artifacts). Front door for /verify.
- ▌ Fix Loop · keyvaluesoftwaresystemsMake ONE bounded fix attempt at failing deterministic checks — root-cause first, editing only files related to the failure — then report. Front door for /fix-loop.
- ▌ Repo Tasks · keyvaluesoftwaresystemsBuild a validated, repo-specific parallel task DAG from an approved LLD and contract.
- ▌ Hld Writing · keyvaluesoftwaresystemsWrite or narrowly repair one decision-focused HLD from an approved PRD, maintained architecture context, and confirmed technical decisions in plain, skimmable technical English.
- ▌ Lld Writing · keyvaluesoftwaresystemsWrite or narrowly repair one buildable repository LLD from an approved HLD, confirmed repo decisions, and bounded code evidence, including an implementation-complete data model and a frontend-ready API/client contract in concise, skimmable technical English.
- ▌ Prd Writing · keyvaluesoftwaresystemsWrite or repair one final PRD from fully confirmed structured context in plain, skimmable technical English. Use only after the PRD interview is complete; never invent missing product decisions.
- ▌ Repo Design · keyvaluesoftwaresystemsProduce a concise, buildable low-level design (LLD) for one repository. Ground it in that repo's code, show the implementation seam, responsibilities, critical flows, interfaces, state, and verification without repeating the HLD or padding irrelevant sections. Writes only the LLD. Front door for /repo-design.
- ▌ Repo Review · keyvaluesoftwaresystemsReview one repository's exact implementation worktree and commit against its LLD and contract.
- ▌ API Contract · keyvaluesoftwaresystemsGenerate the cross-repo API/event CONTRACT (OpenAPI) by reconciling the per-stack LLDs — the backend LLD (what it exposes) and the frontend LLD (what it consumes) — into the single boundary both build against. Also derives acceptance criteria and the affected stacks. Reads the LLDs; writes the contract; never edits app code. Front door for /api-contract.
- ▌ Backend Tasks · keyvaluesoftwaresystemsSplit an approved backend scope + contract into a small, ordered, test-first task list with a verification step per task and risk flags. Read-only planning — never edits code.
- ▌ Hld Interview · keyvaluesoftwaresystemsClarify material architecture decisions before an HLD is finalized. Generate feature-specific technical Grill questions, audit prior answers and contradictions, and collect grouped answers without drafting design prose.
- ▌ Lld Interview · keyvaluesoftwaresystemsClarify only material repository implementation decisions before one repo LLD is written. Audit existing answers, inspect the bounded implementation seam, and ask feature-specific questions in grouped native popups.
- ▌ Prd Interview · keyvaluesoftwaresystemsClarify product intent before a PRD is written. Summarize maintained project context, confirm the feature goal, generate feature-specific Grill questions, and resolve material behaviour and edge cases without scanning application code or drafting the PRD.
- ▌ QA Automation · keyvaluesoftwaresystemsAuthor critical-journey E2E / UI-automation tests from the acceptance criteria (not from the implementation), run them in a clean env, and report. Meets QA standards (risk-tiering, isolation, determinism, no weakened assertions). Edits test files only. Front door for /qa-automation.
- ▌ Backend Design · keyvaluesoftwaresystemsAuthor the backend low-level design (LLD) for a feature — read the relevant backend code to ground the design, then design how the feature slots in — component/sequence design, data model + migration plan, the API/events the backend will expose, error handling, security, observability, and test plan. Writes the LLD doc; never edits app code. Front door for /backend-design.
- ▌ Backend Review · keyvaluesoftwaresystemsReview the backend implementation — security, contract adherence, correctness, backward compatibility, rate-limiting, performance/scaling, migrations, test gaps, observability. Read-only; writes a review artifact. Front door for /backend-review.
- ▌ Frontend Tasks · keyvaluesoftwaresystemsSplit an approved frontend scope + contract into a small, ordered, test-first task list with a verification step per task and risk flags. Read-only planning — never edits code.
- ▌ Repo Implement · keyvaluesoftwaresystemsImplement every task slice in one selected repository and return a verifiable worktree handoff.
- ▌ Retrospect · keyvaluesoftwaresystemsDistill a finished Maestro run into structured, keyed lessons staged for the engine to consolidate. Front door for /retrospect.
- ▌ Frontend Design · keyvaluesoftwaresystemsAuthor the frontend low-level design (LLD) for a feature — read the relevant frontend code to ground the design, then design component/state architecture, routing, the full UI-state matrix, the API it needs to consume, accessibility, performance, i18n, and tests. Writes the LLD doc; never edits app code. Front door for /frontend-design.
- ▌ Frontend Review · keyvaluesoftwaresystemsReview the frontend implementation — UI-state completeness, accessibility, security, resilience, forms, performance, type safety, component quality, state management, responsive/i18n, test gaps. Read-only; writes a review artifact. Front door for /frontend-review.
- ▌ Detect Stack · keyvaluesoftwaresystemsScan the codebase to detect its technology stack(s), then install only the matching stack-tagged skills and agents (plus the always-installed core SDLC pack) by running the installer with a --stack filter. Front door for /detect-stack.
- ▌ Maestro Init · keyvaluesoftwaresystemsOne-shot onboarding for a repo — detect its tech stack and install the matching skills/agents (detect-stack), then build the living-docs knowledge base (build-knowledge). Run once when adopting Maestro in a codebase. Front door for /maestro-init or $maestro-init.
- ▌ Backend Implement · keyvaluesoftwaresystemsImplement an approved backend scope against the cross-repo contract, test-first, meeting the backend engineering standards (security, backward compatibility, rate limiting, idempotency, migrations, observability, performance). Edits code within the approved scope only. Front door for /backend-implement.
- ▌ Human Review Pack · keyvaluesoftwaresystemsAssemble a concise, evidence-backed PR/release review pack — what changed and why, impact, the verify proof, reviewer findings (fixed and deferred), and the exact decision needed. Read-only; writes the pack. Front door for /human-review-pack.
- ▌ React Patterns · keyvaluesoftwaresystemsReact 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
- ▌ Frontend Implement · keyvaluesoftwaresystemsImplement an approved frontend scope by consuming the cross-repo contract exactly, with all required UI states, meeting the frontend engineering standards (accessibility, performance, security, i18n, resilience). Edits code within scope only. Front door for /frontend-implement.
- ▌ Run Upgrade Repair · keyvaluesoftwaresystemsConvert legacy PRD and HLD documents into current concise structures while preserving every existing decision and adding no new product or architecture content.
- ▌ Architecture Review · keyvaluesoftwaresystemsReview the per-stack LLDs and the cross-repo contract — analyze architecture gaps, security, scaling, reliability, data model, and contract soundness. Read-only; writes a review artifact. Front door for /architecture-review.
- ▌ Build Knowledge · keyvaluesoftwaresystemsScan the codebase and build a structured living-docs knowledge base (technical + functional per domain, plus an architecture diagram), and seed cross-cutting review lessons. Front door for /build-knowledge.
- ▌ Functional Testcases · keyvaluesoftwaresystemsAuthor a FUNCTIONAL test-case catalog (human-readable, black-box) for a feature by deriving cases from the acceptance criteria, the HLD, and the cross-repo contract — one case per behavior a user or client can observe, positive + negative + edge, each traceable to the criterion/operation it verifies. Black-box QA source of truth, NOT automation code. Reads the design artifacts; writes the catalog; never edits app code. Front door for /functional-testcases.
- ▌ React Performance · keyvaluesoftwaresystemsReact and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
- ▌ Design Correction Fold · keyvaluesoftwaresystemsApply human-approved corrections to final design-document copies with minimal, validated edits and no unrelated rewriting.
- ▌ React Native Patterns · keyvaluesoftwaresystemsReact Native and Expo app patterns — Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage. Use when building or editing React Native / Expo screens, components, navigation, or data layers.