Skip to content

Instantly share code, notes, and snippets.

View chukaofili's full-sized avatar

Chuka Ofili chukaofili

View GitHub Profile
@chukaofili
chukaofili / CARD_EFFECT_SYSTEM.md
Created June 10, 2025 05:51 — forked from esco/CARD_EFFECT_SYSTEM.md
Guidance provided to Claude Code CLI for building yugioh game engine with prompts

Card Effect System Documentation

1. Introduction

This document describes the architecture and workflow of the card effect system within the Yu-Gi-Oh! Web Duel Interface. The system is responsible for handling the activation, chaining, and resolution of card effects according to Yu-Gi-Oh! rules. It integrates declarative effect definitions (partially implemented via YAML/JSON) with the core game engine logic.

The system aims to manage:

  • Activation: Determining when and if a card effect can be activated.
  • Chaining: Building a sequence of effects when multiple effects are activated in response to each other.
  • Resolution: Executing the effects in the correct (Last-In, First-Out) order.
@chukaofili
chukaofili / ARCHITECTURAL_PRINCIPLES.md
Created June 10, 2025 05:50 — forked from esco/ARCHITECTURAL_PRINCIPLES.md
Architectural guidance provided to Claude Code CLI for building yugioh game engine with prompts

System Prompt: Architectural Principles to Code By

Use rg tool to search for files efficiently

Core Principles

  1. Clean, Simple, Maintainable Code
    • Favor readability over cleverness
    • Prioritize simplicity in design
  • Write code that future developers can easily understand
apiVersion: v1
kind: ConfigMap
metadata:
name: ngrok-configmap
namespace: default
data:
ngrok.yml: |
authtoken: [AUTH_TOKEN HERE]
console_ui: true
web_addr: "0.0.0.0:4040"
apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
name: wildcard-certificate
namespace: cert-manager
labels:
use-clouddns-solver: "true"
spec:
secretName: wildcard-certificate-tls
dnsNames:
apiVersion: cert-manager.io/v1alpha2
kind: ClusterIssuer
metadata:
name: letsencrypt-prod
spec:
acme:
email: __EMAIL__
server: https://acme-v02.api.letsencrypt.org/directory
privateKeySecretRef:
name: letsencrypt-prod
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
# https://docs.fastlane.tools/actions
#
# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane
@chukaofili
chukaofili / echo-server-tls.yaml
Last active November 1, 2019 00:00
echo-server-tls.yaml
apiVersion: v1
kind: Namespace
metadata:
name: echoserver
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: echoserver
namespace: echoserver
@chukaofili
chukaofili / cert-manager-cluster-issuer.yaml
Created May 24, 2018 13:38
cert-manager-cluster-issuer
apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
name: letsencrypt-staging
spec:
acme:
server: https://acme-staging.api.letsencrypt.org/directory
email: [your-email-goes-here]
privateKeySecretRef:
name: letsencrypt-staging
apiVersion: v1
kind: ServiceAccount
metadata:
name: tiller
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: tiller
@chukaofili
chukaofili / heapster-influxdb-grafana.yaml
Last active January 20, 2023 09:10
heapster-influxdb-grafana
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: monitoring-influxdb
namespace: kube-system
spec:
replicas: 1
template:
metadata:
labels: