Skip to content

Claude Code + Cline Configuration & Guidelines

📂 Complete Configuration Files

Claude Code Enterprise Configuration (managed-settings.json)

{
  "organizationName": "TheCreditPros",
  "permissions": {
    "bash": "allow",
    "write": "ask",
    "read": "allow",
    "git": "allow"
  },
  "models": {
    "allowed": ["claude-4-0-sonnet", "claude-3-haiku"],
    "default": "claude-4-0-sonnet"
  },
  "creditRepairCompliance": {
    "enabled": true,
    "fcraValidation": true,
    "auditLogging": "full"
  }
}

Cline Team Rules (.clinerules/thecreditpros.md)

# TheCreditPros Enterprise Development Rules

## Compliance Requirements

- Follow FCRA/FACTA regulations for credit data
- Implement PII encryption for sensitive information
- Use consumer-friendly error messaging
- Cap credit scores at 850 maximum
- Maintain audit trails for credit operations

## Code Standards

- Use TypeScript strict mode
- Maintain 80%+ test coverage
- Follow semantic commit conventions
- Implement proper error boundaries

.prettierrc (Actual Configuration)

{
  "semi": true,
  "trailingComma": "es5",
  "singleQuote": true,
  "printWidth": 80,
  "tabWidth": 2
}

eslint.config.js (Auto-Generated by AI-SDLC - Modern Flat Config)

const typescriptEslint = require('@typescript-eslint/eslint-plugin');
const typescriptParser = require('@typescript-eslint/parser');

module.exports = [
  {
    files: ['**/*.js', '**/*.jsx'],
    rules: {
      'no-console': 'warn',
      'no-unused-vars': 'warn',
      semi: ['error', 'always'],
      quotes: ['error', 'single'],
    },
  },
  {
    files: ['**/*.ts', '**/*.tsx'],
    languageOptions: {
      parser: typescriptParser,
      parserOptions: {
        ecmaVersion: 2020,
        sourceType: 'module',
        ecmaFeatures: {
          jsx: true,
        },
      },
    },
    plugins: {
      '@typescript-eslint': typescriptEslint,
    },
    rules: {
      'no-console': 'warn',
      semi: ['error', 'always'],
      quotes: ['error', 'single'],
      '@typescript-eslint/no-unused-vars': 'warn',
    },
  },
];

🔧 Git Hooks (Husky Configuration)

.husky/pre-commit (Actual File)

#!/bin/bash

# Branch naming enforcement
branch_name=$(git symbolic-ref --short HEAD)
valid_pattern="^(feature|fix|hotfix|release|chore|docs|test)\/[a-z0-9-]+$|^(main|master|develop)$"

if [[ ! $branch_name =~ $valid_pattern ]]; then
  echo "❌ Branch name '$branch_name' does not follow naming convention."
  echo "✅ Valid formats:"
  echo "   - feature/description-here"
  echo "   - fix/bug-description"
  echo "   - hotfix/critical-issue"
  exit 1
fi

# Security auditing
echo "🔍 Running security audit..."
npm audit --audit-level=high
if [ $? -ne 0 ]; then
  echo "❌ High/critical security vulnerabilities found. Please fix before committing."
  exit 1
fi

# Run lint-staged
npx lint-staged

package.json lint-staged configuration

{
  "lint-staged": {
    "*.{js,jsx,ts,tsx}": ["eslint --fix", "prettier --write"],
    "*.php": [
      "bash -c 'if [ -f ./vendor/bin/pint ] && [[ \"$0\" != *\".template.php\" ]]; then ./vendor/bin/pint \"$0\"; fi'"
    ],
    "*.{json,md,yml,yaml}": ["prettier --write"]
  }
}

✅ Best Practices with Real Examples

Credit Repair Domain-Specific Prompts:

Generate FCRA-compliant credit calculation functions with comprehensive validation
Create Laravel migration for credit_reports table following PCI-DSS requirements
Add unit tests for credit score validation with FACTA compliance checks
Refactor payment processing to meet SOC-2 audit requirements

AI Test Generation Prompts:

Generate comprehensive Vitest tests for this credit calculator with edge cases
Create Playwright E2E tests for credit report import workflow with error handling
Add FCRA compliance validation tests for consumer data handling
Generate security tests for PII data encryption in credit processing

❌ Anti-Patterns - What NOT to Do

  • ❌ "Make this code better" → ✅ "Refactor this function to reduce cyclomatic complexity and improve readability"
  • ❌ "Add tests" → ✅ "Generate Vitest unit tests with 90% coverage including edge cases for invalid credit scores"
  • ❌ "Fix the bug" → ✅ "Debug and fix the credit calculation error where scores above 850 are not being capped correctly"

🎯 Credit Repair Domain Guidelines

FCRA Compliance Prompts:

Ensure this consumer data handling complies with FCRA Section 607 requirements
Add audit logging for credit report access per FCRA Section 604
Validate credit dispute processing follows FCRA Section 611 procedures
Generate error messages that comply with FCRA consumer disclosure requirements

Security & Privacy Prompts:

Implement PII data encryption for credit information storage
Add data retention policies compliant with credit reporting regulations
Create secure API endpoints for credit score transmission
Generate privacy-compliant error handling for consumer credit data

📝 Real-World Prompt Examples

Laravel Backend Prompts:

Create a Laravel migration for credit_disputes table with FCRA-compliant audit fields, proper indexing for performance, and soft deletes for regulatory retention.

Generate a PHP service class for credit score calculations that validates input ranges (300-850), handles edge cases for thin files, and includes comprehensive unit tests with FCRA compliance scenarios.

Add FCRA Section 611 dispute processing logic to this Laravel controller with proper validation, audit logging, and consumer notification requirements.

React Frontend Prompts:

Create a React component for credit report display that masks sensitive PII data, includes proper ARIA labels for accessibility, and handles loading states with skeleton UI.

Generate TypeScript interfaces for credit bureau API responses with proper null handling, validation schemas using Zod, and comprehensive JSDoc comments.

Add form validation for credit dispute submission that enforces FCRA consumer rights, validates required fields, and provides clear error messaging.

Testing & QA Prompts:

Generate comprehensive Vitest tests for this credit calculation function including edge cases for: thin credit files, recent bankruptcies, mixed file scenarios, and FCRA accuracy requirements.

Create Playwright E2E tests for the complete credit dispute workflow: form submission, validation, backend processing, consumer notifications, and audit trail verification.

Add security tests for PII data handling in this component ensuring proper encryption, access controls, and FCRA compliance logging.

📌 Developer Checklist for AI-Assisted Development

  • [ ] ✅ Prompt is specific and includes domain context (credit repair)
  • [ ] ✅ AI output reviewed for FCRA/FACTA compliance requirements
  • [ ] ✅ All generated tests pass and provide meaningful coverage
  • [ ] ✅ Security implications reviewed for PII/credit data handling
  • [ ] ✅ Code follows established patterns in codebase
  • [ ] ✅ Performance impact considered for credit processing workflows
  • [ ] ✅ Error handling includes consumer-friendly messaging
  • [ ] ✅ Audit logging added for regulatory compliance

🚀 Advanced AI Integration

With AI-SDLC Framework:

# Generate domain-specific tests
./ai-sdlc test-gen src/credit-calculator.js

# Create E2E tests with FCRA compliance
./ai-sdlc generate-from-requirements "Test CreditReportModal with FCRA compliance"

# AI code review with compliance checking
node scripts-complex/qodo-pr-agent.js 123

This configuration integrates seamlessly with the AI-SDLC framework for comprehensive development automation.

🔗 Related Guides: