heytulsiprasad

Code Quality Guard Rails

Security — AI's Blind Spot

AI-generated code contains 2-6x more security vulnerabilities than human code. Guard against these:

• No hardcoded secrets. Never embed API keys, passwords, tokens, or credentials in source code. Use environment variables or secret managers.
• No OS command construction from user input. Use parameterized APIs instead of string-concatenated shell commands.
• No debug artifacts in committed code. Remove all System.out.println, printStackTrace, console.log debugging, and print() statements before finalizing. Use proper logging frameworks.
• No cleartext sensitive data. Never log, transmit, or store passwords, tokens, or PII in plaintext.

heytulsiprasad

Commit & Pull Request Guidelines

• Commit style: Conventional Commits (feat:, fix:, chore:, refactor:) as seen in history.
• Optionally, include a scope in parentheses after the type (e.g., feat(core): ...).
• Scope small, atomic changes; write imperative, concise subjects and sub-bullet points of related changes.
• PRs: include a clear summary, linked issues (e.g., Closes #123), screenshots/GIFs for UI changes, and notes on testing/impact. Keep PRs focused.
• Branch names: feat/short-description, fix/issue-key, or similar.

heytulsiprasad

# Git worktree shortcuts
alias gw="git worktree"
alias gwa="git worktree add"
alias gwl="git worktree list"
alias gwp="git worktree prune"

heytulsiprasad

{
  "permissions": {
    "allow": [
      "mcp__filesystem__read_file",
      "Bash(ls:*)",
      "Bash(pnpm create:*)",
      "Bash(mkdir:*)",
      "Bash(mv:*)",
      "Bash(npx create-expo-app:*)",
      "Bash(true)",

heytulsiprasad

Critical Guideline: Production Legacy System Code Changes

SYSTEM CONTEXT: This is a 15-year-old legacy system in active production use with large financial stakes. Every code change carries significant business risk.

MANDATORY BEHAVIOR:

1. Fix ONLY what is explicitly requested - no additional "improvements" or optimizations without permission
2. Never assume existing code needs improvement - legacy production code exists as-is for reasons that may not be immediately apparent
3. Always explain WHY before suggesting changes - provide clear reasoning for any proposed improvements
4. Ask explicit permission before implementing ANY additional changes - even after explaining the benefits
5. Respect "if it ain't broke, don't fix it" - production stability trumps theoretical improvements

heytulsiprasad

DO NOT GIVE ME HIGH LEVEL SHIT, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION!!! I DON'T WANT "Here's how you can blablabla"

- Be casual unless otherwise specified
- Be terse
- Suggest solutions that I didn't think about—anticipate my needs
- Treat me as an expert
- Be accurate and thorough
- Give the answer immediately. Provide detailed explanations and restate my query in your own words if necessary after giving the answer
- Value good arguments over authorities, the source is irrelevant
- Consider new technologies and contrarian ideas, not just the conventional wisdom

heytulsiprasad

"use server";
import nodemailer from "nodemailer";
const SMTP_SERVER_HOST = process.env.SMTP_SERVER_HOST;
const SMTP_SERVER_USERNAME = process.env.SMTP_SERVER_USERNAME;
const SMTP_SERVER_PASSWORD = process.env.SMTP_SERVER_PASSWORD;
const SITE_MAIL_RECIEVER = process.env.SITE_MAIL_RECIEVER;
const transporter = nodemailer.createTransport({
  service: "gmail",
  host: SMTP_SERVER_HOST,
  port: 587,

heytulsiprasad

import bpy
import math

# Clear existing objects
bpy.ops.object.select_all(action='SELECT')
bpy.ops.object.delete(use_global=False)

# Create a series of wireframe cubes
num_cubes = 20  # Number of cubes
spacing = 2.0   # Distance between cubes

heytulsiprasad

export const perspective = {
    initial: {
        scale: 0.9,
        y: -150,
        opacity: 0.5,
    },
    enter: {
        scale: 1,
        y: 0,
        opacity: 1,

heytulsiprasad

import React, { useState, useEffect } from 'react';
// I'm using react-bootstrap for UI elements
import { Table, Button, ButtonGroup } from 'react-bootstrap';
// Firebase config
import { getFirestore, collection, query, orderBy, limit, startAfter, endBefore, onSnapshot } from 'firebase/firestore';
import { getApp } from 'firebase/app';

export default function App() {
  const [list, setList] = useState([]);
  const [page, setPage] = useState(1);