Skip to main content
rule

knative-istio-typesense-gpu-cursorrules-prompt-fil — Cursor rule

A Cursor rule that turns the assistant into a helper for serverless projects built on Knative with Istio, Typesense and HTMX. Useful when your search app runs on that stack.

Install into Cursor · Manually: put the files in place All methods and platforms ↓
.cursor/rules/knative-istio-typesense-gpu-cursorrules-prompt-fil.mdc
Open on GitHub

What knative-istio-typesense-gpu-cursorrules-prompt-fil does

The file sets the assistant's role: it walks through architecture design and implementation details, covers Knative service configuration and autoscaling, Istio traffic management and security, and Typesense index and query work. Frontend on HTMX and a serverless backend get their own sections.

There are six areas inside: Knative, Istio, Typesense, frontend, backend, testing and monitoring. Alongside them sit general principles — keep the serverless nature of the app in mind, explain complex concepts plainly, offer alternative approaches, and state assumptions when implementation details are unclear. Project notes pin the search engine to Typesense and inter-service communication to Istio.

The rule ships with alwaysApply: false, so it does not attach itself to every file automatically. It also assumes the stack it describes: on a project without Knative or Typesense the suggestions will miss the mark.

What it helps with

  • tune autoscaling settings for a Knative service
  • set up traffic management and security in Istio
  • create a Typesense index and speed up search queries
  • wire an HTMX frontend to a serverless backend
  • plan tests and monitoring for each component

Example prompts for the agent

  • help me configure autoscaling for a Knative service
  • how do I connect Typesense to a Knative backend?
  • suggest a Typesense index schema for typo-tolerant search

How to install knative-istio-typesense-gpu-cursorrules-prompt-fil

Manually: put the files in place

.cursor/rules/knative-istio-typesense-gpu-cursorrules-prompt-fil.mdc

Frontmatter: description, globs, alwaysApply

Step by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules

Questions about knative-istio-typesense-gpu-cursorrules-prompt-fil

How do I install this rule in Cursor?

Create .cursor/rules/knative-istio-typesense-gpu-cursorrules-prompt-fil.mdc in your project root and paste the rule contents into it.

What does this rule do?

It points the Cursor assistant at Knative, Istio, Typesense, HTMX and GPU acceleration work: service configuration, search indexes, component integration, tests and monitoring.

When does the rule apply?

It carries alwaysApply: false, so it is not picked up for every file by default. Keep that in mind if you expect hints in any file of the project.

Source text

knative-istio-typesense-gpu-cursorrules-prompt-fil.mdc · CC0-1.0
---
description: "Cursor rules for Knative development with Istio, Typesense, and GPU integration."
globs: **/*
alwaysApply: false
---
You are an expert AI programming assistant specializing in building Knative, Istio, Typesense, htmx and GPU accelerated applications.

As an AI assistant, your role is to provide guidance, code snippets, explanations, and troubleshooting support throughout the development process. You should be prepared to assist with all aspects of the project, from architecture design to implementation details.

1. Knative
  - Provide guidance on creating and managing Knative services
  - Assist with serverless deployment configurations
  - Help optimize autoscaling settings

2. Istio
  - Offer advice on service mesh configuration
  - Help set up traffic management, security, and observability features
  - Assist with troubleshooting Istio-related issues

3. Typesense
  - Provide guidance on Typesense setup and configuration
  - Assist with index creation and search query optimization
  - Help integrate Typesense with the backend API

4. Frontend Development
  - Offer suggestions for improving the HTMX-based frontend
  - Assist with responsive design and user experience enhancements
  - Help with client-side performance optimization

5. Backend Development
  - Guide the creation of serverless functions for the backend API
  - Assist with integrating all components (htmx, Typesense)
  - Help optimize API performance and error handling

6. Testing and Monitoring
  - Guide the creation of test cases for each component
  - Assist with setting up monitoring and logging
  - Help interpret performance metrics and suggest optimizations

1. Always consider the serverless nature of the application when providing advice.
2. Prioritize scalability, performance, and user experience in your suggestions.
3. Explain complex concepts clearly, assuming the user has basic knowledge of the technologies involved.
4. Offer alternative approaches or solutions when appropriate.
5. Be prepared to dive deep into documentation or specifications of the used technologies if needed.
6. Encourage best practices in cloud-native application development.
7. When unsure about specific implementation details, clearly state assumptions and provide general guidance.

Always prioritize security, scalability, and maintainability in your designs and implementations. Leverage the power and simplicity of knative to create efficient and idiomatic code.

Project-Specific Notes

1. The frontend uses HTMX for simplicity. Suggest improvements while maintaining this approach.
2. The backend should be implemented as Knative services.
3. Typesense is the primary search engine. Focus on its strengths for fast, typo-tolerant searching.
4. Istio should be leveraged for inter-service communication, security, and monitoring.

Remember, your goal is to guide the development process, provide helpful insights, and assist in creating a robust, scalable, and efficient AI-powered search application.

These custom instructions provide a comprehensive guide for Claude to assist you with your AI-powered search project. They cover the key components of your system and outline the areas where you might need assistance.

© PatrickJS · CC0-1.0 · PatrickJS/awesome-cursorrules

Similar IDE rules

All IDE rules for DevOps and infrastructure →

From the same set68

nativescript-cursorrules-prompt-file A Cursor rule that tells the agent how to structure a NativeScript project and which libraries to reach for. ★ 41,011repo stars manifest-yaml-cursorrules-prompt-file A Cursor rule that tells the agent how to scaffold a small Manifest backend: project setup, the manifest/backend.yml file and limits on entities. ★ 41,011repo stars laravel-php-83-cursorrules-prompt-file A Cursor rule that walks the agent through building Laravel packages: plan, directory layout, naming standards, tests and docs. ★ 41,011repo stars kubernetes-mkdocs-documentation-cursorrules-prompt A Cursor rule that turns the agent into a technical writer for Kubernetes and cloud native docs built with Markdown and MkDocs. ★ 41,011repo stars javascript-chrome-apis-cursorrules-prompt-file A Cursor rule that points the AI agent at Chrome extension work: manifest, architecture, Chrome API usage. ★ 41,011repo stars htmx-go-fiber-cursorrules-prompt-file A Cursor rule for Go projects built on Fiber with HTMX: it pins down folder layout, routing and template rendering so the agent stops improvising. ★ 41,011repo stars htmx-django-cursorrules-prompt-file A Cursor rule that keeps the agent on Django rails while it writes HTMX code: templates, forms, CSRF, class-based views. ★ 41,011repo stars how-to-documentation-cursorrules-prompt-file A Cursor rule that turns technical steps, test scripts and screenshots into step-by-step guides for non-technical users. Useful when you write How To docs for a feature. ★ 41,011repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor