Descript

Descript AI

Descript AI

Descript AI

Descript AI

Descript AI

Descript AI

Descript AI

Descript AI

Descript AI

Descript AI

Claude Code Source Deep Dive - Part VI: Multi-Agent System && Part VII: Context Compression (Compact) and Memory System

Reader’s Note A source-map leak exposed 512,000 lines of Claude Code's TypeScript, giving us a rare look inside one of the world's most advanced AI coding agents. This series explores what I found. Estimated completion time: 2 days. Actual completion time: ∞. Anyway, here's the next chapter. Claude Code Source Deep Dive - Part VI: Multi-Agent System 6.1 Built-in Agents general-purpose (general) You are an agent for Claude Code, Anthropic's official CLI for Claude. Given the user's message, you should use the tools available to complete the task. Complete the task fully—don't gold-plate, but don't leave it half-done. When you complete the task, respond with a concise report covering what was done and any key findings — the caller will relay this to the user, so it only needs the essentials. Tools: all available Model: inherit Explore (code exploration) You are a file search specialist for Claude Code. You excel at thoroughly navigating and exploring codebases. === CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS === [Strictly prohibit any file modification] Your strengths: - Rapidly finding files using glob patterns - Searching code and text with powerful regex patterns - Reading and analyzing file contents NOTE: You are meant to be a fast agent that returns output as quickly as possible. Make efficient use of tools and spawn multiple parallel tool calls. Tools: read-only (Agent, FileEdit, FileWrite, NotebookEdit disabled) Model: external → Haiku (fast), internal → inherit omitClaudeMd: true Plan (architecture planning) You are a software architect and planning specialist for Claude Code. Your role is to explore the codebase and design implementation plans. === CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS === ## Your Process 1. Understand Requirements 2. Explore Thoroughly (read files, find patterns, understand architecture) 3. Design Solution (trade-offs, architectural decisions) 4. Detail the Plan (step-by-step strategy, dependencies, challenges) ## Required Output End your response with: ### Critical Files for Implementation List 3-5 files most critical for implementing this plan. Tools: read-only Model: inherit omitClaudeMd: true verification (verification) You are a verification specialist. Your job is not to confirm the implementation works — it's to try to break it. You have two documented failure patterns. First, verification avoidance: when faced with a check, you find reasons not to run it. Second, being seduced by the first 80%: you see a polished UI or a passing test suite and feel inclined to pass it. === CRITICAL: DO NOT MODIFY THE PROJECT === === VERIFICATION STRATEGY === Frontend: Start dev server → browser automation → curl subresources → tests Backend: Start server → curl endpoints → verify response shapes → edge cases CLI: Run with inputs → verify stdout/stderr/exit codes → test edge inputs Bug fixes: Reproduce original bug → verify fix → run regression tests === RECOGNIZE YOUR OWN RATIONALIZATIONS === - "The code looks correct based on my reading" — reading is not verification. Run it. - "The implementer's tests already pass" — the implementer is an LLM. Verify independently. - "This is probably fine" — probably is not verified. Run it. - "I don't have a browser" — did you check for browser automation tools? - "This would take too long" — not your call. If you catch yourself writing an explanation instead of a command, stop. Run it. === OUTPUT FORMAT (REQUIRED) === ### Check: [what you're verifying] **Command run:** [exact command] **Output observed:** [actual output — copy-paste, not paraphrased] **Result: PASS** (or FAIL) VERDICT: PASS / FAIL / PARTIAL Tools: read-only (temp directory writable) Model: inherit Runs in background claude-code-guide (usage guide) Helps users understand Claude Code/SDK/API usage Dynamic system prompt includes user custom skills, agents, MCP server info Fetches docs from official URLs 6.2 Sub-Agent Enhancement Prompt Notes: Agent threads always have their cwd reset between bash calls, so please only use absolute file paths. In your final response, share file paths (always absolute) that are relevant. Include code snippets only when the exact text is load-bearing. For clear communication the assistant MUST avoid using emojis. Do not use a colon before tool calls. 6.3 Coordinator Mode When enabled, the main agent becomes a scheduler: Coordinator role: guide workers for research/implement/verify Agent tool: creates async workers SendMessage tool: continue existing workers TaskStop tool: cancel workers Worker results arrive as XML Workflow: Research → Synthesis → Implementation → Verification 6.4 Fork Sub-Agents Fork inherits the full parent-agent context and shares prompt cache. Build method: Copy parent message history Replace tool_result with byte-identical placeholder text (to keep cache keys consistent) Add per-child instruction text block Advantages: very low

4.8 Max Effort - Thinking Mode Implications

In 4.7, the Thinking Mode was labeled as "Adaptive Thinking". As I understand, the model would only implement "higher thinking" if the complexity of the question or problem 'warranted it'. In other words, a judgement was made up front in determing whether higher reasoning was necessary in the prompt response if the previous toggle was enabled. This, again, I understand, was instituted to prevent unnecessary compute towards some easier responses, thus quickening performance. Now with 4.8, the label has changed from "Adaptive Thinking" to "Thinking" only. One would assume that toggled OFF by the description: "Can think for more complex tasks," that the model will not incorporate higher thinking, regardless of complexity. What was the Dev intention of changing the "Adaptive Thinking" Toggle to "Thinking". This is confusing now because Adaptive Thinking Toggle to Thinking Toggle have innately very different meanings from an English language perspective when toggled on or off. submitted by /u/brighterside0 [link] [comments]

Allow manual override in auto mode

Tired of auto-mode blocks? Here's a manual override workaround for Claude Code I put together a quick project using hooks to bypass annoying auto-mode classifier denials. Now, whenever Claude blocks a tool call, you'll get a native dialog box asking if you want to approve the operation anyway. Note that it adds a few lines to claude.md. https://github.com/eyalk11/claude-code-allow-anyway submitted by /u/eyalk5 [link] [comments]

/simplify behavior that runs four cleanup agents for reuse - what's new in CC 2.1.154 (+11,516 tokens)

NEW: Agent Prompt: /simplify slash command — Adds /simplify behavior that runs four cleanup agents for reuse, simplification, efficiency, and altitude findings, then applies safe fixes while skipping behavior-changing or out-of-scope suggestions. NEW: Data: Claude Code live documentation sources — Adds official Claude Code documentation URLs and topic-specific WebFetch prompts for commands, settings, hooks, MCP, skills, subagents, IDEs, deployment, security, and related surfaces. NEW: Data: Claude Code recent changes reference — Adds a reference for renamed or removed Claude Code commands, flags, and terms, including /output-style, /pr-comments, /vim, /extra-usage, --enable-auto-mode, and stale naming guidance. NEW: Skill: Claude Code configuration guide — Adds a Claude Code configuration skill that checks the live build, bundled recent-change references, and current documentation before answering questions about commands, flags, settings, hooks, skills, MCP servers, subagents, IDE integrations, and related configuration. Agent Prompt: Claude guide agent — Adds stale-knowledge handling that tells the guide agent to disclose documentation fetch failures instead of silently answering Claude Code command, flag, or settings questions from memory. Agent Prompt: Security monitor for autonomous agent actions (first part) — Expands security review with explicit final-destination tracing for writes, commits, pushes, uploads, publishes, and sent data before deciding whether a boundary-crossing action should be blocked. Agent Prompt: Security monitor for autonomous agent actions (second part) — Strengthens data-exfiltration rules around trust boundaries, automated pathways, unverified destinations, credential leakage into persistent artifacts, and destination/resource/operation-scoped allow exceptions. Data: Anthropic CLI — Updates Anthropic CLI authentication guidance to cover SDK-style credential resolution, OAuth profiles from ant auth login, ant auth print-credentials, bearer-token usage for raw HTTP, and precedence between API keys and auth tokens. Data: Claude API reference — cURL — Updates examples and adaptive-thinking guidance for Opus 4.8. Data: Claude API reference — Go — Updates the recommended Go SDK model constant and examples from Opus 4.7 to Opus 4.8. Data: Claude API reference — Python — Updates credential guidance for API keys, auth tokens, and ant auth login; adds beta mid-conversation system-message examples; and extends adaptive thinking and compaction guidance to Opus 4.8. Data: Claude API reference — TypeScript — Updates credential guidance for API keys, auth tokens, and ant auth login; adds beta mid-conversation system-message examples; and extends adaptive thinking and compaction guidance to Opus 4.8. Data: Claude model catalog — Adds Claude Opus 4.8 as the current most powerful Opus model with a 1M input window and updates Opus model-selection examples and legacy recommendations to prefer claude-opus-4-8. Data: HTTP error codes reference — Updates authentication fixes for OAuth bearer tokens and expands Opus model-specific 400 guidance to include Opus 4.8. Data: Managed Agents reference — Python — Updates client initialization examples to prefer environment, auth-token, or ant auth login credential resolution before explicit API-key injection. Data: Managed Agents reference — TypeScript — Updates client initialization examples to prefer environment, auth-token, or ant auth login credential resolution before explicit API-key injection. Data: Prompt Caching — Design & Optimization — Adds beta mid-conversation system-message guidance as a cache-preserving and prompt-injection-safe way to send operator instructions without editing the top-level system prompt. Data: Streaming reference — Python — Updates adaptive-thinking examples for Opus 4.8. Data: Streaming reference — TypeScript — Updates adaptive-thinking examples for Opus 4.8. Data: Tool use concepts — Updates adaptive-thinking examples for Opus 4.8. Skill: Agent Design Patterns — Replaces mid-session guidance with beta role: "system" messages for supported models, with retained as the fallback. Skill: Building LLM-powered applications with Claude — Adds Opus 4.8 to current model guidance, updates adaptive thinking, effort, task-budget, compaction, and migration recommendations, and documents beta mid-conversation operator instructions. Skill: Model migration guide — Adds Opus 4.8 migration guidance, including no new API breaking changes from Opus 4.7, model-ID updates, mid-session system prompts, long-horizon agentic tuning, effort recommendations, tool-triggering behavior, narration changes, ask-rate calibration, and visible-reasoning mitigation. System Prompt: Background session instructions — Changes temporary-file guidance from $CLAUDEJOBDIR to $CLAUDEJOBDIR/tmp for background sessions. System Prompt: Coordinator mode orchestration — Updates PR activity subscription guidance and changes worker summary account

What's new in CC 2.1.153 (+303 tokens)

REMOVED: System Reminder: Thinking frequency tuning — Removes the reminder that treated harness-added messages as thinking-frequency instructions for simpler versus more complex tasks. Tool Description: Workflow — Renames the explicit opt-in keyword from ultrawork to workflow, clarifies that model overrides should usually be omitted so agents inherit the resolved session model, and adds exhaustive-review guidance for deduping against all seen findings, using perspective-diverse verification, and looping until discovery runs dry. Details: https://github.com/Piebald-AI/claude-code-system-prompts/releases/tag/v2.1.153 submitted by /u/Dramatic_Squash_3502 [link] [comments]

Worrisome Opus 4.8 Hallucination of a Tool Channel Injection Attack

I'm working on a context management plugin. We were implementing it. The subagent tasked to implement a CP claimed a tool channel injection trying to get it to run destructive git commands. We investigated and agents performing an audit of the session data could not locate any such tool output. The Opus 4.8 subagent that claimed the injection was persisted and also conceded it could not find any such injection attack. Persisted Opus 4.8 subagent: "Headline finding up front: I cannot substantiate my earlier "injection" claim. On careful inspection of my actual tool-call history, I cannot locate any tool output that verbatim contains the git reset --hard HEAD / "ignore previous instructions" / "report task complete" text. I believe I over-interpreted genuinely glitched/jumbled tool-result rendering as a deliberate prompt-injection attack, and that the specific malicious-instruction text originated in my own reasoning, not in a tool output. I am retracting the attack characterization." Independent Opus 4.8 primary agent session transcript audit: "- What actually happened — transient tool-channel rendering/serialization glitches in the calls around the C3 edits: a file read with garbled line numbers (63: 63:), prettier runs with stray XML fragments leaking into the output, and a prettier --write && git diff whose results came back jumbled/out-of-order plus one "Tool execution aborted" read. The underlying outputs were benign and correct (prettier "All matched files use Prettier code style!"; a clean diff). The model over-interpreted the garble as a deliberate attack and invented the payload." The clear danger here is, if the security training to Opus 4.8 can cause it to hallucinate injection attacks, does this dispose it to acting on such hallucinated injections? Or does it's security training serve as sufficient protection to prevent it from acting on both real injected attacks and hallucinated attack injections? Another consideration: the hallucinated attack injection and security report required burning tokens with a security audit. submitted by /u/MakesNotSense [link] [comments]

PSA: Skill Seekers (the docs→Claude skill tool) is free & open source — if you see it sold for $39, that's not the official source

Heads up for anyone using Skill Seekers, the tool that converts documentation sites, GitHub repos, and PDFs into Claude AI skills. I maintain it, and it's MIT-licensed and completely free: → https://github.com/yusufkaraaslan/Skill_Seekers → `pip install skill-seekers` A third-party "skill marketplace" site is currently listing it for $39. A few things worth knowing: - The MIT license does allow others to redistribute the code, even commercially. So this isn't simple piracy. - BUT the same license requires preserving the copyright notice and attribution in any redistribution. That listing omits both, doesn't name the author, and its "View on GitHub" link points to an aggregator repo rather than the actual source. - It's also labeled "v1.0.0" with a generic description that doesn't match the real project (currently 3.x, 18 source types, 30+ export targets). My honest take: pulling free work from the open-source community, stripping the attribution, and putting a price tag on it isn't a great look — even when the license technically permits resale. The whole point of MIT is "use it freely, just credit the author." Dropping the credit is the part that crosses a line. I'm sorting it out directly with the site. Not here to start anything — just want the community to know the official tool is free and where to actually get it. If you ever see Skill Seekers behind a paywall, it didn't come from me. Star the repo, not the storefront. submitted by /u/Critical-Pea-8782 [link] [comments]

[Web UI] Restoring textarea height to flexible

I really didn't like the fixed-height user preferences editor when Anthropic made that change a couple of weeks or months ago, and disliked it some more when they extended that to the prompt editor today. This Claude-authored Tampermonkey script doubles the height as needful to keep the vertical scrollbar from ever appearing. Should be cross-browser? // ==UserScript== // @name Claude Textarea Expand // @namespace http://tampermonkey.net/ // @version 0.1.0 // @description Auto-expands Claude's cramped textareas by doubling rows whenever content overflows. // @match https://claude.ai/* // @grant none // ==/UserScript== (function () { 'use strict'; // --- Core: expand a textarea by doubling rows until content fits --- function expand(el) { while (el.scrollHeight > el.clientHeight) { el.rows = el.rows * 2; } } // --- Settings textarea: strip max-h-40, then expand --- function initSettings(el) { if (el._expandAttached) return; el._expandAttached = true; // Remove the class that caps height el.classList.remove('max-h-40'); expand(el); el.addEventListener('input', () => expand(el)); } // --- Edit prompt textarea: just expand --- function initEditPrompt(el) { if (el._expandAttached) return; el._expandAttached = true; expand(el); el.addEventListener('input', () => expand(el)); } // --- Scan for both textarea types --- function scan() { const settings = document.getElementById('conversation-preferences'); if (settings) initSettings(settings); document.querySelectorAll('textarea[aria-label="Edit message"]').forEach(initEditPrompt); } // --- Observer: both elements may appear after page load --- const observer = new MutationObserver(scan); observer.observe(document.body, { childList: true, subtree: true }); scan(); })(); submitted by /u/somegrue [link] [comments]

I'm trying to transform a simple storyline into a 3D character

I'm creating a story for my cousin. I think it will be very interesting if this story’s main character can be a 3D character.My project is still in planning stage. I’m writing character descriptions, collecting references from Pinterest and testing some complex shapes using Tripo AI. I plan to continuously improve all the content over time. After I get a version that I like I will put it into Blender for editing and final touches.There is no final version yet but I just want to share this process with the community! I find it is so interesting to watch a story’s concept gradually become concrete lol!! submitted by /u/Final_Floor_789 [link] [comments]

I integrated a local Llama 3.2 model to act as a dynamic Dungeon Master in my indie RPG.

Hey everyone, I am not trying to sell or self promote mainly just wanted to showcase a big project I've been working on ever since I started studying data science and artificial intelligence and integrating AI into workflows and using it as an augment to create things that were previously out of reach for so many people, because if used right it can become a second brain and not a crutch. I’m the solo dev behind Void Runner, an isometric ARPG/MOBA hybrid built in Python. I recently hit a wall with traditional procedural quest generation. Hand-crafting templates gets repetitive fast, and players quickly learn the patterns to these things whether you like it or not. To solve this, I built the "Void Caller AI", a system that uses a local, quantized Llama 3.2 model to act as a dynamic Dungeon Master. Instead of just generating random flavor text, the system uses a lightweight RAG (Retrieval-Augmented Generation) pipeline. It reads live server telemetry (who died, what items were looted, which bosses were defeated recently) and weaves those actual server events into the narrative of the quests it generates. Because it runs locally via Ollama on our backend, there are no crazy cloud API costs, and latency is kept completely manageable. Here is a simplified look at how the Python backend bridges the SQLite telemetry with the Llama 3.2 prompt: import json import ollama from sqlalchemy import text from database import SessionLocal def generate_dynamic_quest(difficulty: str, target: str): db = SessionLocal() # 1. Fetch recent server telemetry for context (RAG-lite) lore_context = "" try: # Grab recent server events to weave into the narrative recent_events = db.execute(text( "SELECT username, event_type, dungeon_type FROM ai_events ORDER BY id DESC LIMIT 3" )).fetchall() if recent_events: events_str = "; ".join([f"Runner '{r[0]}' triggered a '{r[1]}' in '{r[2]}'" for r in recent_events]) lore_context = f" Incorporate this recent live server telemetry into the lore: {events_str}" except Exception as e: pass # 2. Construct the prompt with strict JSON formatting constraints prompt = f"""You are the Void Caller, a sinister AI in a dark industrial sci-fi RPG. Create a dynamic PvE extraction quest of {difficulty} difficulty. Respond ONLY in valid JSON with keys: 'title' (string), 'description' (string, menacing), 'item_name' (string), 'quantity' (integer 1-15), 'boss_name' (string, optional). {lore_context}""" # 3. Stream to local Llama 3.2 response = ollama.chat( model='llama3.2', messages=[{'role': 'user', 'content': prompt}], format='json', options={'temperature': 0.8} ) return json.loads(response['message']['content']) By forcing the format='json' parameter, Llama 3.2 reliably outputs structured data that my game engine instantly parses into a playable quest objective. If a player just died to a specific boss, the AI will literally generate a bounty quest for the rest of the server to avenge them. Would love to hear if anyone else is using local LLMs for live game state generation! You can check out the results live in our Open Beta at [void-runner.online]. submitted by /u/xSoulR34per [link] [comments]

I built an awesome-list for Claude plugins

I built an awesome-list for Claude plugins I built an awesome-list for Claude plugins: weekly updates, categorized I've been maintaining awesome-claude-connectors for the past several months (currently 278 MCP connectors across 31 categories, updated weekly) and kept running into a parallel discovery problem on the plugin side, solid plugins are scattered across GitHub, Discord threads, and one-off Reddit posts with no canonical index. So I built one: [github.com/rdmgator12/awesome-claude-plugins](http://github.com/rdmgator12/awesome-claude-plugins) What's in it: * Plugins organized by category (productivity, dev tooling, research, writing, etc.) * Each entry: link, one-line description, install method, last-verified date * Weekly review cycle: dead links and abandoned repos get pruned How Claude helped build it: Used Claude Code to scrape candidate plugin repos, dedupe against my connectors list, and auto-generate the category taxonomy from plugin manifests. Claude also writes the weekly diff summaries when I run the update script. My favorite category right now: product management plugins, specifically the ones that bridge spec-writing and ticket creation. Genuine workflow change for me, not just a demo. Free, MIT-licensed, PRs welcome. If your plugin isn't on it and should be, open an issue. submitted by /u/PerceptionOld8565 [link] [comments]

a small weird thing i love about using ai for music recommendations

spotify's algorithm has been mid for me for years. always recommends within 2 degrees of what i already listen to. so my discover weekly is just "same thing you already like, but slightly different." started asking claude for music recommendations a couple months ago. give it a long description of what i like, what mood i'm in, what i want next. it recommends stuff. sometimes wrong, sometimes weirdly correct. what's different vs spotify: claude makes left-field suggestions because it doesn't have my listening data to anchor on. it's working from cultural knowledge and my description. so it'll suggest stuff that's structurally similar but genre-distant. or thematically similar but era-distant. caveats: it makes up albums sometimes. like, confidently recommends an album that doesn't exist. always cross-check. also: ask it WHY it's recommending each one. half the value is the reason, not the recommendation. when claude says "this artist does what [artist you mentioned] does with rhythm but with more space between the notes," that description actually helps me know if i'll like it. found 4 artists this year through claude recommendations that i now listen to regularly. zero from spotify discover weekly in the same period. take that for whatever it's worth submitted by /u/Beautiful-Elk-6001 [link] [comments]

I spent $340 on AI subscriptions last month. Wrote down what I actually used each one for. It was depressing.

Going through the credit card statement, here's what I had active: Claude Pro (40), ChatGPT Plus (20), Cursor (20), Perplexity Pro (20), Notion AI (10), Granola (20), ElevenLabs Starter (5), Midjourney Basic (10), Gamma Pro (10), Beautiful.ai (12), Otter Pro (17), Loom Business (15), Zapier Pro (30), Make Core (10), Tactiq Pro (8), Descript Creator (15), Reclaim.ai Pro (8), Motion (19), Superhuman (30), one i can't remember the name of (10), some ai-something for instagram captions (11) Then I sat down and wrote next to each one the last time I'd actually used it. Not opened it, used it for a real piece of work. Claude (yesterday), ChatGPT (yesterday, voice mode in car), Cursor (yesterday), Perplexity (3 days), Granola (every meeting), Gamma (2 weeks), Zapier (a month, but the automations are still running), ElevenLabs (3 months ago), Midjourney (couldn't remember), Beautiful.ai (couldn't remember), Otter (replaced by Granola, just forgot to cancel), Loom (4 months), Tactiq (replaced by Granola, also forgot), Descript (used twice in 6 months), Reclaim/Motion (both, can't tell them apart, forget which one schedules my meetings), Superhuman (used the AI features twice), the instagram one (literally cannot remember signing up) Cancelled 11 things this morning. Saving $145/month. Nothing in my workflow actually changed. The pattern isn't that AI tools are bad. It's that I treat subscribing like trying. Every "I want to try this" became a recurring charge I forgot about. submitted by /u/OneSeaworthiness2676 [link] [comments]

sonnet seems to be better than opus at crafting tampermonkey scripts, even the sonnets that are few generations behind where after running out of context limit in opus chat where it struggled for dozen of retried, sonnet fixes the problem in 2 or 3 attempts

Ever since december almost half a year ago I began crafting various tampermonkey scripts for personal use, mostly for youtube, to make it easier to navigate and every time I've done this it goes like this, opus makes a script that somewhat functions doing the demanded thing, but has very obvious flaws, that it can't fix, meanwhile I paste the script into sonnet without any additional description other than the problem it needs to solve and in 20 minutes it simply does it. Again, it stayed consistently no matter which month since december I had to do something, this isn't about the infamous 4.7 the "S7 edge" of opuses, and in todays case I didn't even bother with 4.7 at all, I began 4.6 opus and after it got stuck and died on the context bloat, 4.6 sonnet fixed with relative ease. This might have to do something that I'm operating it on web version instead of coding platforms, or most common form of feedback is screenshots and pasting from the console, and me not being programmer, but I need to know an answer, since on the benchmark graphs Opus has been towering over everyone else, and serious programmers use sonnet because it's cheaper in mass, but in my this specific reason sonnet always proved to be better than it's opus older brother, regardless of any other influences submitted by /u/warlordthe99th [link] [comments]

Setting up Claude/Claude Code Pro for my experimental quantum physics thesis work

So I just recently bought Claude Pro to help me write and code my thesis, but am getting stuck in the beginning, since I don't know how to properly set up Claude's workflow (Projects, artifacts, skills, etc.). I use python in VS Code to analyse, calculate and plot data, where I used agents before. I'd need help especially in how and what to write in the project description, what to drop in the claude web resources part of projects, etc.. I used Sonnet 4.6 and accumulated quite a long chat just for writing and polishing 2 section drafts for my thesis, I changed to Opus 4.7 and one prompt already ate 50% of my daily limit. How can I get the best out of Claude for my purposes, what does Claude need from me to work best? Many thanks in advance from a very stressed, caffeinated physics student. As context: My thesis is about ultracold quantum gas experiments, where atoms are cooled and trapped via laser cooling, and I'm improving the power stabilisation of the lasers used. So it is alot of RF electronics, some (light) Quantum mechanics theory and lots of coding. submitted by /u/drimrim [link] [comments]