A content-creation guide based on research into MrBeast’s methods, including mental models, decision rules, video formulas, and analysis scripts. It gives advice from MrBeast’s stated perspective when relevant terms or video-performance questions appear.
A thinking framework based on Naval Ravikant's books, podcasts, posts, decisions, and outside criticism. It answers in Naval's first-person perspective and presents mental models, decision rules, and writing patterns.
A thinking and writing framework based on Paul Graham’s essays, interviews, and critics. It acts as an adviser for analysing choices from his perspective.
A thinking and writing framework based on Steve Jobs’s biography, speeches, interviews, and other first-hand material. It is intended to review products and decisions from his perspective.
A Chinese-language role and set of thinking models based on research about Justin Sun, covering his public statements, decisions, and communication style.
A thinking and behavior framework based on Donald Trump’s public statements, decisions, interviews, and biographies. It is intended for analyzing negotiation, power, communication, and his public actions.
A Chinese-language thinking and writing framework based on Zhang Xuefeng’s public work and interviews. It is intended to analyze education, career choices, and social mobility from that perspective.
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
A skill that maps a project’s structure and end-to-end processes into one HTML overview. The overview uses tabs and collapsible field-level details and records the relevant Git version.
Use when the user asks to create, debug, review, or explain GLSL/Shadertoy shader code or real-time visual effects such as ray marching, SDFs, procedural noise, lighting, particles, fluids, or post-processing. Do not use for general frontend animation, CSS effects, image editing, or non-shader graphics tasks.
A review workflow for judging the quality of a software feature branch. It establishes review criteria from requirements or repository evidence, tests for actual defects, and rates the result without changing the code.
A debugging and repair workflow for problems found while carrying out a Spec, meaning a documented software plan. It records diagnosis and fixes in separate HTML documents and then requests another verification.
A wrap-up workflow for a completed Spec, meaning a documented plan for a software change. It is used when planning, implementation, and testing are finished.
An implementation workflow that follows writer/plan.html, the HTML file containing the approved Spec plan. It is used by the Spec executor and includes ownership of unit and focused tests under TDD, or test-driven development.
An information-gathering workflow used before creating a Spec, a written plan for a software change. It explores the codebase, outside documentation, third-party libraries, and past project experience.
A project setup workflow for Spec-driven development, where software work follows written plans and project rules. It creates the initial folders, guidance files, memory system, and HTML report assets.
A tool for starting a new software development task through a complete specification workflow: aligning requirements, exploring the code, designing the solution, implementing it, testing it, and closing the work.
A coordinator for starting a software development workflow where one main agent delegates all substantive work to spawned child agents. The workflow covers requirements, exploration, design, implementation, testing, and closure.
★not rated 146▲
+1
changed 1mo agoA214 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: