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

ColdFusion Coding Standards for CFC Files

Coding standards for coldfusion cfc.instructions

java
0 downloads
69 views
0

Tags

best-practices
error-handling

Related Instructions

View all →

Spring Boot 2 → 3 Migration Guide (Jakarta EE)

**/*.java

Production-safe step-by-step playbook to migrate Spring Boot 2.x to 3.x with Jakarta EE, Java 17, Spring Security 6, and Hibernate 6

java
spring-boot
spring-boot
java
+5
1
845

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
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 for CFC Files

  • 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 ##

Additional Best Practices

  • Use this scope for component properties and methods when appropriate.

  • Document all functions with purpose, parameters, and return values (use Javadoc or similar style).

  • Use access modifiers (public, private, package, remote) for functions and variables.

  • Prefer dependency injection for component collaboration.

  • Avoid business logic in setters/getters; keep them simple.

  • Validate and sanitize all input parameters in public/remote methods.

  • Use cftry/cfcatch for error handling within methods as needed.

  • Avoid hardcoding configuration or credentials in CFCs.

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

  • Group related methods logically within the component.

  • Use meaningful, descriptive names for methods and properties.

  • Avoid using cfcomponent attributes that are deprecated or unnecessary.

  • Use ternary operators where possible

  • Ensure consistent tab alignment.