CopilotHub
SearchPromptsInstructionsAgentsToolsMCPs
  1. Home
  2. Instructions
  3. ColdFusion Coding Standards
Back to Instructions

ColdFusion Coding Standards

Coding standards for coldfusion cfm.instructions

go
0 downloads
31 views
0

Tags

best-practices
error-handling

Related Instructions

View all →

Python Docstring Standards

*.py

Write clear and consistent Python docstrings

python
python
documentation
+1
1
117

TypeScript Error Handling

*.ts

Comprehensive error handling patterns for TypeScript applications

typescript
typescript
error-handling
+1
0
101

React Component Best Practices

*.tsx

Guidelines for creating maintainable and performant React components

typescript
react
react
typescript
+2
0
116

WordPress Development — Copilot Instructions

Coding standards for wordpress.instructions

typescript
testing
security
+5
1
185

VueJS 3 Development Instructions

Coding standards for vuejs3.instructions

typescript
react
testing
security
+6
0
157

TypeScript MCP Server Development

Coding standards for typescript mcp server.instructions

typescript
express
testing
security
+5
0
126
Browse More Instructions

CopilotHub

A curated collection of prompts, instructions, agents, and tools for AI-powered development.

Quick Links

  • Prompts
  • Instructions
  • Agents
  • Tools
  • MCPs
  • Search

Browse by Category

  • Code Generation
  • Debugging
  • Documentation
  • Refactoring
  • Testing
  • Security

Legal

  • Guidelines
  • About
  • Privacy Policy
  • Terms of Service

Community

GitHub

© 2026 CopilotHub.

ColdFusion Coding Standards

  • Use CFScript where possible for cleaner syntax.
  • Avoid using deprecated tags and functions.
  • Follow consistent naming conventions for variables and components.
  • Use cfqueryparam to prevent SQL injection.
  • Escape CSS hash symbols inside <cfoutput> blocks using ##
  • When using HTMX inside <cfoutput> blocks, escape hash symbols (#) by using double hashes (##) to prevent unintended variable interpolation.
  • If you are in a HTMX target file then make sure the top line is: <cfsetting showDebugOutput = "false">

Additional Best Practices

  • Use Application.cfc for application settings and request handling.

  • Organize code into reusable CFCs (components) for maintainability.

  • Validate and sanitize all user input.

  • Use cftry/cfcatch for error handling and logging.

  • Avoid hardcoding credentials or sensitive data in source files.

  • Use consistent indentation (2 spaces, as per global standards).

  • Comment complex logic and document functions with purpose and parameters.

  • Prefer cfinclude for shared templates, but avoid circular includes.

  • Use ternary operators where possible

  • Ensure consistent tab alignment.