Crafting Effective Readmes

Apply the K.I.S.S principle (Keep It Simple, Stupid) to reduce complexity, improve maintainability, and solve problems elegantly. Use when designing systems, writing code, planning solutions, creating documentation, architecting features, or making decisions where simplicity drives quality and efficiency.

Interactive guide for creating Remotion videos - from strategic concept to rendered MP4. Use when the user wants to create a video, make a Remotion project, build a product demo video, generate a launch video, make a recurring content template, create a marketing video, or says "I need a video for...", "help me make a video", "video for my product", "remotion video". Covers the full creative process: expert deliberation, scenario design, build, and review. Works alongside the official remotion-dev/skills for API-level guidance.

Create well-structured RFCs and technical proposals for software projects. Use this skill whenever the user wants to write an RFC, technical proposal, design doc, architecture doc, or system design overview. Also trigger when the user says things like "write an RFC", "I need to propose a new system", "create a technical proposal", "document the architecture", "write up the design", "I need a design doc", or "explain the system architecture in a doc". Even if they just say "RFC", "design doc", or "arch doc", use this skill. Covers both RFCs (proposing what to build) and architecture docs (documenting an existing codebase).

Documentation-first project planning that produces implementation-ready blueprints and single-shot coding agent prompts. Generates 4 interconnected docs — SPECIFICATION.md, IMPLEMENTATION.md, TASKS.md, BRANDING.md — plus a self-contained PROMPT.md for autonomous execution by any coding agent. Includes interactive tech stack selection, design pattern recommendations, and architecture decisions with trade-off analysis. Trigger when user wants to: plan a project, create specs, architect a system, break work into tasks, choose a tech stack, get design pattern advice, generate a coding agent prompt, or do documentation-first development. Phrases: "plan my project", "spec this out", "architect", "help me plan", "what stack should I use", "generate a prompt", "break this into tasks", "project docs", "I want to build X".

Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-python. Use before the final response whenever the current task changed runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size and including local-only or uncommitted work. Skip only for trivial or conversation-only tasks, repo-meta/doc-only tasks without behavior impact, or when the user explicitly says not to include the PR draft block.

Transforms analysis, data, and complex information into clear, persuasive narratives tailored to specific audiences — executives, customers, investors, or non-technical stakeholders. Provides story structures (Hero's Journey, Problem-Solution-Benefit, Situation-Complication-Resolution) and audience adaptation techniques. Use when presenting findings, explaining technical concepts to non-technical audiences, writing announcements, or when user mentions "write this for", "explain to", "present findings", "make this compelling", or "audience is".