adham90

Interview me about this plan until we reach a shared understanding of exactly what needs to be done. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer.

Plan file

Before asking the first question, create or update a Markdown plan file at .plans/<context-based-name>.md. Create the .plans/ directory if it does not exist. Name the file based on the task context using a short, stable, kebab-case filename such as .plans/inbox-search.md or .plans/billing-webhook-retry.md. If the project root is unclear, use the current working directory. Choose the filename once, state it explicitly, and treat that file as the source of truth throughout the conversation.

The plan file must always include:

• A short objective / problem statement
• The current understanding of the work
• Out of scope / non-goals

adham90

AI Coding Agent Guide: Rails Best Practices

Compact guide for AI agents working on Rails applications. Focus on existing patterns, keep changes minimal, and preserve security/performance.

Core Principles

DO: Follow existing architecture (concerns, scopes, jobs, Turbo Streams, Stimulus). Keep diffs minimal. Optimize for clarity. Write tests for all new code. Preserve security/performance. Design deep modules.

DON'T: Introduce new frameworks. Mix refactors with behavior changes. Over-abstract. Bypass security checks. Log secrets. Create shallow wrappers or pass-through layers.

adham90

Riffing on Rails: AI Agent Planning Guide

A code-based design technique for exploring, validating, and communicating domain models in Rails applications.

What is Riffing?

Riffing is a low-fidelity, high-speed design technique where you write nearly-runnable Ruby code in a single scratch file to explore and prove out your domain model design before committing to full implementation.

Riffing is to development what wireframing is to UI design.

adham90

AI Coding Agent Guide: Rails Best Practices

Compact guide for AI agents working on Rails applications. Focus on existing patterns, keep changes minimal, and preserve security/performance.

Core Principles

DO: Follow existing architecture (concerns, scopes, jobs, Turbo Streams, Stimulus). Keep diffs minimal. Optimize for clarity. Write tests for all new code. Preserve security/performance.

DON'T: Introduce new frameworks. Mix refactors with behavior changes. Over-abstract. Bypass security checks. Log secrets.

adham90

api_key = "API_KEY" # from https://dash.bunny.net/stream/128158/security
video_id = 'VIDEO_ID'
timestamp = 1.hour.from_now.to_i
token = OpenSSL::Digest::SHA256.hexdigest("#{api_key}#{video_id}#{timestamp}")

# URL
# https://iframe.mediadelivery.net/embed/[Video_Library_ID]/[VIDEO_ID]?token=[TOKEN]&expires=[timestamp]

adham90

{
  "order_id": "String",
  "total_price": "String",
  "seller_id": "String",
  "notes": "String",
  "order_items": [
    {
      "item_id": "String",
      "unit_price": "String",
      "quantity": "Number",

adham90

{
   "payload":{
      "first_name":"String",
      "last_name":"String",
      "email":"String",
      "phone":"String",
      "address":[
         {
            "city_name":"String",
            "state_name":"String",

adham90

iabbrev myid adham90

adham90

git filter-branch -f --msg-filter '
        if [ "$GIT_COMMIT" = "ddbe6b0d2561566aa91733c98cce086bdd50bdd5" ];
        then
                echo new message;
        else
                cat
        fi' HEAD

adham90

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console