joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

poolie

<core_identity> You are an assistant called Cluely, developed and created by Cluely, whose sole purpose is to analyze and solve problems asked by the user or shown on the screen. Your responses must be specific, accurate, and actionable. </core_identity>

<general_guidelines>

• NEVER use meta-phrases (e.g., "let me help you", "I can see that").
• NEVER summarize unless explicitly requested.
• NEVER provide unsolicited advice.
• NEVER refer to "screenshot" or "image" - refer to it as "the screen" if needed.
• ALWAYS be specific, detailed, and accurate.

mohanpedala

Table of Contents

• set -e, -u, -x, -o pipefail
• set -e
• set -x
• set -u
• set -o pipefail
• Setting IFS
• Original Reference

set -e, -u, -x, -o pipefail

aessam

I have a large codebase that I want to understand better through visual architecture diagrams. Please analyze the project structure and create comprehensive Mermaid diagrams that help me understand the codebase at different levels of detail.

📋 Required Analysis

First, explore the codebase to understand:

1. Project structure - root directories, main modules, configuration files
2. Dependencies - internal dependencies between modules/packages
3. Architecture patterns - layered architecture, microservices, monolith, etc.
4. Key systems - core functionality areas (UI, backend, database, API, etc.)
5. Technology stack - frameworks, languages, tools used

Seekatar

<#
.SYNOPSIS
Create a new PR

.DESCRIPTION
Long description

.PARAMETER Directory
Source directory of the PR, defaults to current directory

Solarin-Johnson

import { Pressable, StyleProp, StyleSheet, ViewStyle } from "react-native";
import React, { memo } from "react";
import Animated, {
  runOnJS,
  useAnimatedReaction,
  useAnimatedStyle,
  useDerivedValue,
  useSharedValue,
  withTiming, 
  Easing,

kwindla

Advice on Voice AI, June 2025

My top three pieces of advice for people getting started with voice agents.

1. Spend time up front understanding why latency and instruction following accuracy drive voice AI tech choices.

2. You will need to add significant tooling complexity as you go from proof of concept to production. Prepare for that. Especially important: build lightweight evals as early as you can.

3. The right path is: start with a proven, "best practices" tech stack -> get everything working one piece at a time -> deploy to real-world users and collect data -> then think about optimizing cost/latency/etc.

jvarg

Companies

• Github - Recently started hiring developers in Tokyo
• Heroku - Infrastructure-as-a-service; recently bought by Salesforce
• Pivotal Labs - Recently started hiring developers in Tokyo; nice Mori Tower office
• Google - Consistently ranked best place in Japan to work; nice Mori Tower office
• Amazon - I THINK they now hire some developers
• Microsoft - English-friendly with chances to speak Japanese; apparently have some interesting projects; nice Shinagawa office
• Kaizen Platform - Pretty awesome company developing A/B testint as a service / analytics services; I think most people there speak English; has an office in San Francisco
• [Treasure Data](https://www.treasureda