AI SummaryA curated collection of Windsurf rules files that guide AI coding assistants in generating Helm charts following industry best practices, architecture patterns, and Kubernetes conventions. Developers using Codeium's Cascade or similar AI tools benefit by getting standardized, production-ready Helm chart scaffolding and configurations.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "vibe-rules-collection — Windsurf Rules" prompt rules to my project. Repository: https://github.com/copyleftdev/vibe-rules-collection Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
A curated collection of .windsurfrules files designed to guide AI coding assistants (like Codeium's Cascade) in generating code that adheres to various best practices, architectural patterns, language idioms, and framework conventions.
Guiding Principles
• Chart Structure: Follow the standard Helm chart directory structure (templates/, Chart.yaml, values.yaml, charts/, crds/). • Chart.yaml: Define chart metadata accurately, including apiVersion (use v2 for Helm 3+), name, version, appVersion, and description. • values.yaml: Define default configuration values clearly. Structure values logically. Add comments explaining each value. • Templates: Use Go templating ({{ }}) within Kubernetes manifest templates (templates/*.yaml). Keep templates readable and well-commented. • Variables: Access values using .Values.<path>. Use the required function for mandatory values. • Control Structures: Use template functions and control structures (if, range, with) effectively. • Named Templates (_helpers.tpl): Define reusable template snippets (helpers) in templates/_helpers.tpl to avoid repetition and improve readability (e.g., for generating names, labels). • Resource Definitions: Ensure generated Kubernetes manifests are valid and adhere to Kubernetes best practices. • Dependencies: Manage chart dependencies using the dependencies field in Chart.yaml and the charts/ directory. • Notes (NOTES.txt): Provide useful post-installation instructions or information in templates/NOTES.txt. • Linting & Testing: Use helm lint to validate chart structure and templates. Consider using helm test for basic post-deployment verification. • Secrets Management: Avoid hardcoding secrets in templates or default values.yaml. Reference external secrets or inject them at deploy time.
AI Instructions
• Chart Scaffolding: Generate the standard Helm chart directory structure and basic files (Chart.yaml, values.yaml, templates/_helpers.tpl, templates/deployment.yaml, etc.). • Chart.yaml Generation: Populate Chart.yaml with appropriate metadata, defaulting to apiVersion: v2. • values.yaml Structure: Generate a well-commented values.yaml with common configuration options (image repository/tag, replicas, service type/port). • Template Generation: Create Kubernetes manifest templates (deployment.yaml, service.yaml, etc.) using Go templating to reference .Values. Utilize common helper templates. • Helper Templates (_helpers.tpl): Generate standard helper templates (e.g., for full name, chart name, labels) in _helpers.tpl and use them in resource templates. • Value Referencing: Ensure templates correctly access values using .Values and scope functions like with. • Linting Command: Suggest running helm lint after generating or modifying charts. • NOTES.txt Stub: Provide a basic templates/NOTES.txt. • Dependency Management: Show how to define dependencies in Chart.yaml.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts