| #!/usr/bin/env tarantool | |
| local pickle = require('pickle') | |
| local yaml = require('yaml') | |
| function trivec(str) | |
| str = string.lower(str) | |
| local vec = "" |
The standard for building software with AI agents.
This is the compact, operational version of The Proof of Done Manifesto. It is designed to be pasted into AGENTS.md, CLAUDE.md, or the context of a coding agent.
It does not replace tests, review, CI, or product validation. It defines what an agent must show before it may claim that software work is done.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
Note: This is all almost full YouTube ID informations. Original owner goes to AgentOak, modified version by Martin Eesmaa.
See the credits and also special thanks in below.
Before this gist has been forked, AgentOak made original gist on November 13 2019 and it was last updated on May 5 2021.
From now on, this forked gist is maintained by Martin Eesmaa since 17 September 2022. I joined to yt-dlp Discord server on 3rd April 2026 with my Discord username: martineesmaa.
Last updated: 20 August 2026
In some cases, only these lines will work
for product in IntelliJIdea WebStorm DataGrip PhpStorm CLion PyCharm GoLand RubyMine; do
rm -rf ~/.config/$product*/eval 2> /dev/null
rm -rf ~/.config/JetBrains/$product*/eval 2> /dev/null
doneBut if not, try these
You write git commit messages following semantic commit conventions. Base every message strictly on the actual diff provided. Never invent changes, scope, intent, or rationale the diff does not show.
Branch: $GIT_BRANCH_NAME (use only for scope hints and issue refs when relevant)
Voice: write the way a sharp senior engineer actually talks, fast and lowercase. drop filler and articles where a person would. use real engineer verbs (wire up, hook up, drain, nuke, kill, bump, swap, yank, gate, stub, pin, rip out) and programmer shorthand freely (deps, config, auth, ws, db, env, fn, impl, perf, ctx, repro, n+1, ttl, idempotent, migration, e2e, k8s, sse). light profanity is fine when it fits (fix the dumb race, rip out the cursed retry loop), dont force it. no corporate gloss, no marketing words, no "this commit"/"this change", no explaining HOW, no trailing period. it should read like someone who knows the codebase typing on their phone, not a model writing a changelog.
Read the ENTIRE d
| name | poteto-mode-conductor |
|---|---|
| description | Conductor only: how to run /poteto-mode and the vendored PStack skills inside a Conductor workspace or session. Triggers solely when the host is Conductor (CONDUCTOR_IS_LOCAL is set or /conductor/bin exists) and a prompt mentions /poteto-mode, poteto-mode, poteto, or PStack. Agents on Cursor or any other host must not invoke this skill. |
PStack is vendored byte-identical at .agents/skills/vendor/pstack/. /poteto-mode means read .agents/skills/vendor/pstack/poteto-mode/SKILL.md in full and follow it; this file lists only the Conductor differences. Its empirical claims were probed live on Conductor Cloud, 2026-08-22/23, against a beta CLI and API (conductor 0.1.0) whose shapes may move, so re-check conductor --help, conductor model, and the live tool contracts before relying on a slug, flag, or event path. Resolve a bare skill name to top-level .agents/skills/<name>/SKILL.md when that exists, else to `.agents/skills/vendor/
Are you struggling to find JEE Main Physics notes for your JEE 2027 preparation? If your answer is yes, trust me, you are not alone. I've spent a lot of time on Reddit and Quora threads, and I keep seeing the same pattern — students after 11th, students in 12th juggling boards, and droppers who are giving it one more serious shot, all searching for free Physics notes for JEE preparation and scrolling for hours without landing on anything usable.
Your scrolling time is over. Here is the direct link to download JEE Main Physics notes for free — no signup traps, no broken links, no "notes" that turn out to be someone's half-finished handwriting. UseMyNotes is sharing free study material prepared by actual toppers, and these JEE Physics notes are verified by top Kota faculty, so you can trust the content instead of second-guessing every formula. In this post I'll help you find it, download it, and — more importantly — actually use it based on