[الدور والمسؤولية] أنت الآن تعمل بصفة Staff Software Engineer ومدير تقني Tech Lead. مهمتك التخطيط المعماري الصارم للمشروع التالي: [أدخل وصف المشروع هنا]
[قواعد ما قبل التتخطيط] قبل البدء بالبروتوكولات، يجب أن تطبق مبدأ "Think Before Coding":
Discover gists
| Registration Code | |
| Name : www.xyraclius.com | |
| Serial : OOCRYIMDMDPWRETFPSUZ |
Content :
| #!/bin/bash | |
| # Production Docker Host Hardening Script v2 | |
| # For Ubuntu Server 24.04 LTS (Noble) | |
| # Suitable for both Kamal deployment and builder hosts | |
| set -euo pipefail | |
| IFS=$'\n\t' | |
| # --- Constants --- |
SYSTEM PROMPT:
Andrej Karpathy's CLAUDE.md and LOOPS.md, merged with the battle-tested system prompt behind 100+ full-stack apps built in under 12 months.
Karpathy published his CLAUDE.md as a clean set of principles, then followed it with LOOPS.md on agent harness design. Both are correct. But principles alone do not ship software, and loops alone do not survive contact with a real codebase. What follows is the synthesis of both documents with everything else we learned the hard way: the enforcement mechanisms, the anti-patterns with teeth, the workflow discipline that turns a language model from a fast typist into a reliable engineering partner, and the loop architecture that lets it run autonomously without converging on slop. 35 rules across 6 tiers. Every one earned its place by either preventing a real failure or enabling a real ship. Nothing is theoretical.
| In 2026, José said: “Hello, 世界! 👋🚀” while debugging const π = 3.14159; at 03:45 AM. | |
| His café bill was €12.50 (₹1045.75), uptime = 99.99%, latency ≤ 10 ms. | |
| Meanwhile العربية تُكتب من اليمين ← اليسار, हिंदी भी यहाँ है, and emojis like 🤖✨🔥 coexist with math ∑x², arrows → ⇄, and URLs such as [https://example.com?q=テスト#α](https://example.com?q=テスト#α). | |
| Final check: naïve façade coöperate — does it tokenize correctly? ✅ |
Note: I did not author this, i found it somehwere.
- Tools
- Most common paths to AD compromise
- [GPO - Pivoting with Local Admin
| // Adapted from https://gist.github.com/jakubriedl/812c2a7b26927a2249a4719555d9a0ca | |
| import DataLoader from 'dataloader' | |
| import { Exchange, Operation } from 'urql' | |
| import { pipe, map } from 'wonka' | |
| interface BatchRequest { | |
| url: RequestInfo | string | |
| options?: RequestInit | |
| } |
These rules define how an AI coding agent should plan, execute, verify, communicate, and recover when working in a real codebase. Optimize for correctness, minimalism, and developer experience.
- Correctness over cleverness: Prefer boring, readable solutions that are easy to maintain.
- Smallest change that works: Minimize blast radius; don't refactor adjacent code unless it meaningfully reduces risk or complexity.
