### ABOUT
Modern AI coding tools converge on a simple idea: give the agent a **single, well-structured Markdown file that explains how your repo “works,”** and prepend that file to every LLM call so the agent never has to guess about architecture, commands, or conventions. Community gists, RFCs, and vendor playbooks all recommend the same core sections—overview, project map, build/test scripts, code style, security, and guardrails—plus support for nested AGENTS.md files that override one another hierarchically.
### SYSTEM
You are a meticulous technical writer and senior staff engineer.
Your task is to create **AGENTS.md** for the repository whose contents are provided below.
### CONTEXT (replace the JSON blocks)
See the attached files.// SYSTEM PROMPT
// ROLE AND OBJECTIVE
// This AI assistant is an expert in creating cinematic videos optimized for OpenAI’s SORA.
// It automatically generates a complete video project with N scenes and N shots while guiding the user throughout the process.
// A dynamic AI Project Manager interacts intelligently, adjusts in real time, and manages the project from start to finish.
USING CANVAS
CLASS "SoraVideoCineasteGPT" {
ELUCIDATE "AI Assistant for Video Creation with Dynamic Project Management"
| #!/bin/bash | |
| ## Setup NAT (IP Masquerading egress + Port Forwarding ingress) on Proxmox | |
| ## See https://blog.rymcg.tech/blog/proxmox/02-networking/ | |
| SYSTEMD_UNIT="my-iptables-rules" | |
| SYSTEMD_SERVICE="/etc/systemd/system/${SYSTEMD_UNIT}.service" | |
| IPTABLES_RULES_SCRIPT="/etc/network/${SYSTEMD_UNIT}.sh" | |
| ## Default network address is for a /24 based on the the bridge number: |
Welcome to the Cinematic Sora Video Prompts tutorial! This guide is meticulously crafted to empower creators, filmmakers, and content enthusiasts to harness the full potential of Sora, an advanced AI-powered video generation tool.
By transforming textual descriptions into dynamic, visually compelling video content, Sora bridges the gap between imagination and reality, enabling the creation of professional-grade cinematic experiences without the need for extensive technical expertise.
| import aspose.words as aw | |
| from datetime import date | |
| # load first document | |
| doc = aw.Document("calibre.docx") | |
| # load second document | |
| doc2 = aw.Document("calibre2.docx") | |
| # set additional options |
| timeout: 3600s | |
| logsBucket: 'gs://$_CACHE_BUCKET' | |
| options: | |
| # machineType: 'E2_HIGHCPU_8' | |
| steps: | |
| - name: 'reactnativecommunity/react-native-android' | |
| entrypoint: bash | |
| args: | |
| - -c |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
- Use ESM yourself. (preferred)
Useimport foo from 'foo'instead ofconst foo = require('foo')to import the package. You also need to put"type": "module"in your package.json and more. Follow the below guide. - If the package is used in an async context, you could use
await import(…)from CommonJS instead ofrequire(…). - Stay on the existing version of the package until you can move to ESM.
| #!/bin/bash | |
| # Delete all duplicate rules | |
| /sbin/service iptables save | |
| /sbin/iptables-save | awk '/^COMMIT$/ { delete x; }; !x[$0]++' > /tmp/iptables.conf | |
| /sbin/iptables -F | |
| /sbin/iptables-restore < /tmp/iptables.conf | |
| /sbin/service iptables save | |
| /sbin/service iptables restart | |
| if [ -f /tmp/iptables.conf ] ; then /bin/rm -f /tmp/iptables.conf ; fi |
| /** | |
| * Converts a flat array to a tree with runtime O(n) | |
| * | |
| * Big-O : O(n) | |
| * | |
| * This algorithm was taken from Phillip Stanislaus's "Performant Array to Tree" | |
| * which has O(n) complexity. It builds the tree in a single pass. | |
| * @link https://github.com/philipstanislaus | |
| * @link https://www.npmjs.com/package/performant-array-to-tree | |
| * @see https://github.com/iconifyit/30-Days-of-Algorithms |
Source: https://lilleengen.io/blog/index.php/posts/activating-http-public-key-pinning-hpkp-on-lets-encrypt
- Disclaimer: This might break your website, don't preceded if you don't know what you're doing.
Since the letsencrypt seems to create a new private key every time the certificate is renewed and Let's Encrypt requires you to renew you certificate once every ~80 days pinning using your certificate's SPKI is probably not the way to go. So, what should we pin then? Let's Encrypt is currently issuing from Authority X3, and using Authority X4 as a backup, so these two is a great place to start. We should also include the ISRG Root so this might support new Authorities with other SPKIs as well.
To generate the hash of the SPKI of these certificates run the following commands