flow

Generate Helm 3+ chart structure for todo/task applications. Use for: creating Chart.yaml, values.yaml, and templates/ directory with Deployment and Service manifests. Triggers: "helm chart", "helm template", "helm values", "create helm chart", "helm install", "helm upgrade", "package as helm chart". NOT for: plain Kubernetes YAML (use kubernetes-yaml-best-practices), Kustomize, or kubectl commands. NOT for: CRDs, hooks, subcharts, or advanced Helm features unless explicitly requested.

Apply Kubernetes pod security hardening with securityContext, Pod Security Standards, and container isolation. Use for: adding runAsNonRoot, readOnlyRootFilesystem, dropping capabilities, seccomp profiles, and privilege escalation prevention. Triggers: "secure pod", "pod security", "non-root container", "security context", "k8s security", "harden deployment", "pod security standards", "restricted PSS". NOT for: NetworkPolicies, RBAC, Secrets management, or service mesh security. Use alongside kubernetes-yaml-best-practices for complete manifests.

Generate production-ready Kubernetes YAML manifests following best practices. Use when creating or reviewing: Deployments, Services, ConfigMaps, Secrets, Ingress, PersistentVolumeClaims, or any k8s resource YAML. Triggers: "kubernetes manifest", "deployment yaml", "service yaml", "write k8s resource", "create kubernetes", "k8s yaml", "pod spec", "container spec". NOT for Helm charts, Kustomize overlays, or kubectl commands.

Deploy and test applications on local Minikube Kubernetes cluster. Use for: loading local Docker images to Minikube, exposing services locally via port-forward or minikube service, debugging pods (logs, describe, exec), troubleshooting CrashLoopBackOff/ImagePullBackOff errors. Triggers: "deploy to minikube", "minikube image load", "port-forward", "minikube service", "debug pod", "why is pod crashing", "minikube dashboard", "local kubernetes testing". NOT for: minikube installation, minikube start/stop, cloud Kubernetes, Helm charts, or writing YAML manifests (use kubernetes-yaml-best-practices for YAML).

OCI & OKE specialist for the Todo app hackathon project. Provides infrastructure context, authentication patterns, and deployment guidance for Oracle Kubernetes Engine in me-dubai-1. Use when working with: OKE cluster operations, kubectl commands, oci CLI, Helm deploys to OKE, Dapr/Kafka on OKE, Ingress/LoadBalancer setup, Kubernetes secrets, cloud deployment, OCI networking, node pool management, or troubleshooting OKE auth errors. Triggers: "OKE", "oci", "kubectl", "deploy to cloud", "cluster", "OCI", "oracle kubernetes", "ingress on OKE", "secrets on OKE", "Dapr on OKE", "Kafka on OKE", "node pool", "DOKS alternative".

Dapr service invocation pattern for FastAPI Todo app. Use DaprClient.invoke_method to call other services with user_id propagated via metadata. Use when implementing service-to-service communication in FastAPI applications with user context propagation.

Dapr pub/sub pattern for FastAPI Todo app with user isolation. Use Dapr Python SDK (dapr.clients.DaprClient) to publish events to pubsub component named "kafka-pubsub" with user_id in metadata. Use when implementing event publishing to Dapr pub/sub from FastAPI endpoints with user context propagation.

Kafka consumer pattern for todo app background services. Use when implementing event consumers, background workers, or async event processing from Kafka. Triggers: kafka consumer, consume events, event listener, background worker, process events, aiokafka consumer, event handler.

Kafka producer pattern for FastAPI todo app events with user isolation. Use when implementing event publishing to Kafka from FastAPI endpoints. Triggers: kafka producer, publish event, event streaming, task events, audit events, produce to kafka, aiokafka producer.

provide fastapi jwt dependency, current_user from jwt, protected endpoint auth, fastapi jwt verification with shared secret

todo rest endpoint, /api/tasks crud, fastapi todo api route, patch /complete endpoint, todo specific rest api

place file in monorepo, frontend nextjs folder, backend fastapi, reference specs folder, monorepo structure guidance

nextjs todo component, task card tailwind, add edit todo form, todo list ui pattern, nextjs task management ui

follow spec-driven development, enforce SDD workflow, implement from spec, generate code from plan and tasks, use spec kit plus, run full SDD loop

todo task sqlmodel, task database model, sqlmodel task schema with user_id, create todo model

enforce user isolation, filter by user_id, prevent data leak in query, multi-user task filter, always add WHERE user_id

FastAPI todo advanced endpoints, filter sort recurring due_date tasks query params. Extends existing task endpoints with advanced query parameters for filtering and sorting. Use when implementing enhanced task filtering capabilities with priority, tags, due dates, and recurring tasks.

Extend todo task sqlmodel, add priority tags due_date recurring reminder fields to Task model. Always preserves existing fields (id, user_id, title, description, completed, created_at, updated_at) and maintains backward compatibility. Use when modifying Task model with new fields like priority, tags, due_date, recurrence, and reminders.